Finally Make.com
version control for
every scenario.
Make.com's Version History disappears after 60 days, won't show you what changed, and gives you no way back when a teammate's save lands on top of yours. Comfrey is the safety net underneath.
Three ways Make goes wrong, quietly.
A teammate's save lands on top of yours. A 60-day window on version history. No audit log outside Enterprise. Put together, that's a lot of room for things to go wrong without anyone noticing — until they do.
Teams using Make.com work better with Comfrey
Version history
Every edit to every saved scenario is captured automatically. See exactly what changed, when, and by who — down to individual modules and fields.
One-click rollback
Diff any two versions side by side. Restore a previous version quickly — no rebuild, no guesswork.
Change feed
One feed showing every edit across every scenario, every workspace. Know what your team changed today without asking in Slack.
Inline documentation
Pin notes, decisions, and runbooks to the exact module they describe. Context shows up where someone actually needs it.
Knowledge map
See who understands each scenario. Get warnings when critical automations are understood by only one person.
Scenario linting
Catch broken modules, missing error handlers, hardcoded keys, and abandoned copies — before they cause outages.
How it compares to what you're doing now.
Most teams cobble together version control out of saved blueprints, naming conventions, and hope. Here's what each option actually gives you.
| Capability | Make.com built-in | Manual blueprint exports | Comfrey |
|---|---|---|---|
| History beyond 60 days | — | If you remember | ✓ |
| One-click rollback | Partial | — | ✓ |
| Plain-language diff | — | — | ✓ |
| Two-maker conflict warning | — | — | Coming |
| Change log on non-Enterprise plans | — | — | ✓ |
| Dependency map | Make Grid (paid, public beta) | — | ✓ cross-platform |
| Cross-platform | — | — | ✓ |
| Setup time | n/a | Hours, ongoing | Minutes |
Make's Version History retains saved scenario versions for up to 60 days. Audit Logs are Enterprise-only and stored for 12 months. Make Grid is in public beta on all paid plans.
Three steps. Then you're covered.
Connect Make
Authorize your Make account. Comfrey reads your scenarios — it never modifies them. Read-only by default.
First snapshot runs
Comfrey captures the current state of every scenario. Your full history starts building from here — automatically.
Sleep easy
Every saved change is versioned and diffable. If anything breaks, you know what changed — and you can roll it back.
“I need to know what changed before I start debugging.”
“Three people edit the same scenario. We need a changelog.”
“When I hand off a workflow, the new owner has no context.”
Built for the people actually running automations.
Comfrey is not another dev tool ported to no-code. It's built from the ground up for ops leads, RevOps teams, and automation specialists — the people who actually build and maintain Make scenarios every day. No CLI. No Git. No YAML. Just the visibility and control you've been missing.
Where this fits in the bigger picture.
Version control is the foundation. Once you have history, diffs, and rollback, everything else becomes possible — linting, knowledge maps, documentation, team coordination. Comfrey is building the full ops layer for automation, starting with the part that hurts most.
Frequently asked questions
Does Comfrey modify my Make scenarios?
No. Comfrey connects with read-only access. It takes snapshots of your scenario state but never writes, edits, or executes anything in your Make account.
How is this different from exporting blueprints?
Blueprint exports are a manual, one-time snapshot. Comfrey captures every change automatically, diffs versions side by side, and lets you restore with one click. It's the difference between a backup and version control.
What if I use Make and other tools?
Comfrey is building support for multiple platforms. Make is first, with n8n, Zapier, and others on the roadmap. One dashboard for your whole automation estate.
Does my team need to be technical?
Not at all. There's no CLI, no Git, no config files. If you can use Make, you can use Comfrey. It's designed for the people who actually build and maintain automations.
Is my data secure?
Yes. Comfrey stores scenario metadata and structure — not your execution data or customer records. All data is encrypted in transit and at rest. See our security page for full details.
What does it cost?
Comfrey is in early access. Pricing will be published closer to general availability. Early-access users will get a significant discount.