Launched this week

Comfrey

Launched this week

The missing oversight layer for automation teams

2 followers

The missing oversight layer for automation teams

2 followers

Visit website

Automation tools

Comfrey helps turn scattered, duplicated, messy automations into manageable infrastructure. Track workflow changes, compare versions, document logic, map ownership, and detect risky patterns across the tools your team already uses. Built for teams that rely on automation but need more visibility, safety, and control.

Free

Launch tags:YC Application

Launch Team / Built With

Maker

📌

Hey everyone 👋 I’m Elizabeth the founder of Comfrey, and today is a beta launch. Comfrey came from a problem I kept seeing in teams that rely on automation software such as Make, Zapier, HubSpot, Airtable, n8n, Adobe Fusion, and similar tools. At first, automations are a superpower. Someone builds a workflow to solve a real problem. Then another one. Then a few more. Fast forward a year and the business is running on dozens of workflows spread across different tools, built by different people, with different naming conventions, half-finished docs, duplicated logic, and no clear owner. Everything works fine — until it doesn’t. Comfrey helps teams turn scattered, messy automations into manageable infrastructure. It tracks workflow changes, compares versions, documents logic, maps ownership, and detects risky patterns across the tools your team already uses. I'm building fast so expect a more robust launch very soon, but for this beta I’ve started with Make.com. There are already a few tools live that you can play with, focused on understanding and documenting Make scenarios more clearly. The goal is simple: make automations easier to understand, safer to change, and less dependent on one person’s memory. I’m not trying to replace automation tools. I’m building the missing visibility and control layer around them. I’d love feedback from anyone who uses Make.com or other no-code and low-code automation tools at work. I’d be really interested to hear what would matter most to you first: version history, better documentation, dependency maps, alerts, linting, ownership, or something else entirely. The roadmap is being shaped by what I hear here.

Report

4d ago

Forum Threads

p/comfrey

•

3d ago

Beta Tools: Automation Changelog Generator for Make.com Scenarios

This thread is for discussion around our latest beta tool - a changelog generator for automation workflows that currently works for Make.com scenarios.
Visit here: https://beta.comfrey.io/tools/ch...
I built this tool to combat the change blindness that automation teams face when trying to understand who changed what in a scenario, and when. The tool currently displays the updates made to each available version in an easy to read format, with the option to download the log so it can easily be shared with team mates.
Please feel free to leave your honest feedback - this is an early stage tool being shaped as I type!

p/comfrey

•

3d ago

Beta Tools: Automation Linter for Make.com Scenarios

This thread is for discussion around our latest beta tool - a linter for automation workflows that currently works for Make.com scenarios.
Visit here: https://beta.comfrey.io/tools/li...
Every workflow developer has their own style when designing automations - often this is a benefit to a team as different people have bring a variety of skills. However, if you've ever had to jump in and fix a scenario that someone else built, only to find their naming structure is all over the place, they've got over a hundred modules, and their routers look like mini hedgehogs, you'll understand the need for a way to set and enforce standards across a team. This linter tool is the start of that - currently there are only a few rules in place that you can choose to run, but we're working on a more robust solution.
Please feel free to leave your honest feedback - this is an early stage tool being shaped as I type!

p/comfrey

•

3d ago

Beta Tools: Automation Knowledge Map for Make.com Scenarios

This thread is for discussion around our latest beta tool - a knowledge mapper for automation workflows that currently works for Make.com scenarios.
Visit here: https://beta.comfrey.io/tools/kn...
Knowledge about different critical workflows can easily become siloed within automation teams. This basic tool surfaces who on the team currently has the best understanding of the current scenario, and helps team discover automations that are dangerously close to becoming a knowledge gap.
Please feel free to leave your honest feedback - this is an early stage tool being shaped as I type!

View all

Forum Threads