Theme

Quick Guide (<20min)

Versioning

Median read time: 02 min 14 sec
Version control is just as important for workflows as it is for code. With doFlo, you can easily track, manage, and roll back workflow changes using simple JSON exports.

Why Version Your Workflows?

  • ✅ Keep a history of every change you make
  • ✅ Experiment safely without breaking production workflows
  • ✅ Roll back instantly if something doesn’t work out
  • ✅ Collaborate with your team using Git

How Versioning Works in doFlo

Instead of creating multiple workflow copies inside the app, doFlo gives you full control through exported JSON files. These files capture the complete structure and logic of your workflow.

Step 1. Export Your Workflow

  • Open your workflow in doFlo
  • Select Export as JSON
  • Save the file locally and commit it to your Git repository
Tip: Use meaningful commit messages (e.g. “Added Slack notification step”) so you can easily track changes later.

Step 2. Track in Git

Push your JSON file to GitHub, GitLab, or any Git-based version control system. From here, you can:
  • Compare diffs between versions
  • Collaborate with your team via pull requests
  • Revert to a previous version if needed

Step 3. Import a Version Back to doFlo

Need to restore or roll back?
  • Download the JSON file from your repo
  • Go to Import Workflow in doFlo
  • Upload the file—your workflow will be instantly reconstructed
Import and export buttons can be found here:

Best Practices

  • Keep one repo per project or client for tidy organization
  • Tag major releases (e.g. v1.0, v2.0) for quick rollbacks
  • Regularly export production workflows as backups

✨ That’s it! With doFlo’s export/import system, workflow versioning is as reliable as code versioning - giving you the freedom to build, iterate, and recover without stress.
Previous
Migrate from n8n or Make