Help Center

What is Workflow Version History?

Workflow Version History is a built-in feature that automatically tracks every saved state of your automation. It records each editor's name, the exact timestamp, and whether the version was a draft or published. This allows you to review changes, compare different iterations, and restore previous versions with confidence.

Key Benefits

Instant Rollback: Revert to any of the last 10 versions (or 30 days of history) with a single click.
Team Transparency: See exactly who made changes and when they saved them.
Flexible Recovery: Restore a previous version as a new draft or create an entirely separate workflow from it.
Intuitive Interface: Clean sidebar design with chronological version labels (v12, v13, v14...) makes navigation simple.
No Additional Cost: Included as part of the CRM's core workflow editing tools.

How Versions Are Created

Version History automatically captures new entries when:

You manually click Save
You confirm changes in the Unsaved Changes pop-up
You use the Save Version option within the workflow
The workflow status changes (e.g., Draft to Published or Published to Draft)

Note: Routine auto-saves don't create versions by themselves. Use Save Version to snapshot your current auto-saved changes into Version History.

Browsing Versions

Open Version History to view all saved entries organized by time and editor. Each version shows:

Workflow name
Version number (e.g., v12, v13)
Timestamp
Editor name
Status (Draft or Published)

You can filter versions by editor and view up to 10 versions or 30 days of history (whichever comes first).

Restoring or Creating From a Version

Click Restore next to any previous version to reopen it as a new draft. Your published workflow remains unchanged until you publish the restored draft.

Alternatively, choose Create new workflow from version to branch into a separate workflow without affecting the original.

Restoration requirements:

The workflow must be in Draft status
There must be no contacts currently enrolled in the workflow

When you restore a version, it becomes a new version entry while all prior versions remain available.

Best Practices

Name versions at important milestones (e.g., "Added new sequence," "Updated approval process")
Coordinate with team members by using Save Version before making significant changes
Use Preview to validate differences before restoring
Create new workflows from versions when exploring major changes without affecting your current build

Important Notes

Restoring creates a new draft that must be published to go live
Undo/Redo history resets after restoration
Auto-save covers canvas edits, but some configuration panel edits may require their own save
Version History retains up to 10 versions or 30 days of history