Version control system for Make.com scenarios
Built for Make.com workflow builders who need to test scenario changes safely before deploying to production..
“I would like to modify a scenario without taking it into use. A way to do this is to have different versions of a scenario and then determine which one is activ…”
The receipts — real demand
“I would like to modify a scenario without taking it into use. A way to do this is to have different versions of a scenario and then determine which one is active. Then you also have history to go back and check how the scenario has changed. If you have version control, then it would also be possible to have auto save as you are not modifying the live scenario.”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Make.com workflow builders testing scenario changes safely before production. No search volume; pain signal shows live users manually duplicating scenarios, a clear workaround for a missing feature.
Competition & the opening
Make.com itself has no versioning for scenarios; competing automation platforms (Zapier, n8n) support some form of draft/publish. The gap is full version control with diff, rollback, and branching within Make.
What's hard to build
Must hook into Make.com's proprietary API and architecture for scenario storage and execution; ensuring version diffs are human-readable and rollbacks don't break live data flows requires deep integration and thorough testing across Make's module ecosystem.
Why now
Make.com's workflow-centric user base has grown but lacks native version control, creating clear product gap that no competitor fills.
How you'd monetize
$9.99/mo add-on subscription per Make account