Versioning & Drafts
Edit flows safely with draft mode and version history.
How Versioning Works
Every time you save a flow, Notumation increments the version number (v1, v2, v3, and so on). The version history is stored permanently, so you always have a record of previous configurations.
Active flows have two distinct states: the published version (currently running) and the draft (your work-in-progress edits). This separation ensures that your live automation keeps running reliably while you make changes.
Editing an Active Flow
When you open an active flow and start editing, your changes are saved as a draft automatically. The key points:
- The published version continues running and handling trigger events as normal
- Your edits are saved in real time as a draft — you will not lose work if you close the page
- Other workspace members see the published version when viewing the flow
- A “Draft” badge appears next to the flow name to indicate unpublished changes
You can safely experiment with step order, conditions, and new actions without affecting the live automation.
Publishing Changes
When your draft is ready, click the Publish button in the flow editor toolbar. This replaces the published version with your draft:
- The new version becomes active immediately
- The next trigger event will use the updated flow
- The previous version is preserved in the version history
Before publishing, consider running a dry test to verify your changes work as expected.
Discarding a Draft
If you decide your changes are not needed, click Discard Draft in the flow editor toolbar. This throws away all unpublished edits and reverts the editor to the currently published version. The live flow is not affected since it was already running the published version.
Version History
Click the Versions tab in the flow editor to see a list of all previous versions. Each entry shows:
- Version number (e.g., v3)
- Save date and time
- A summary of what changed (if you added a description)
You cannot directly restore a previous version, but you can view any old version and manually recreate its configuration. This prevents accidental rollbacks on active flows.
Duplicating a Flow
Click the Duplicate button on any flow (active or inactive) to create a copy. The duplicate:
- Gets a new name with “Copy of” prefix
- Starts in an inactive state — it will not trigger until you activate it
- Has its own independent version history starting at v1
- Contains all the steps, conditions, and configuration from the original
Use duplication to create variations of a flow (e.g., one per database) or to experiment without touching the original.
Exporting a Flow
Click the Export button to download the flow configuration as a JSON file. The export includes:
- All steps, triggers, conditions, and configuration
- Template variable references (as
{{var.NAME}}, not the actual values) - Version metadata
Exports are useful for backups, sharing flow templates with teammates, or moving flows between workspaces. Import a JSON file by clicking Import Flow on the dashboard.