Workflows evolve. You improve them. You add features. You respond to an edge case you didn't see coming. This is good — it means you're learning and adapting.

But evolution comes with risk. You change something, test it quickly, and push it live. Three hours later, something breaks. You want to undo the change. But you've already modified the scenario in Make or n8n, and the old version is gone.

Version control for no-code workflows is simple. You don't need Git (though you can use it). You just need backups with dates and version numbers.

Export and Backup

Both Make and n8n let you export your workflows as JSON files.

Make: - Open the scenario - Click the three dots menu (top right) - Select "Download scenario as a blueprint" - Save the JSON file with a descriptive name: MorningBrief_v9.0.256_2026-03.json

n8n: - Open the workflow - Click the three dots menu - Select "Download as JSON" - Save with a descriptive name: EmailTriage_v9.0.256_2026-03-15.json

Store these files somewhere safe — a folder in Google Drive, Dropbox, or a Git repository if you're comfortable with that. The naming convention should be: [workflow-name]_v[version]_[date].json

Backup cadence: - Immediately after you build something that works - Before any significant change (add an AI step, change the trigger, add a new data source) - After any significant change, as your new "current working version"

Keep at least the last 3 versions. This gives you a safety net if two changes ago you broke something and didn't notice.