What this does

Every time a workflow is changed, Velaro keeps the version it replaced. Earlier versions of each workflow are saved, whether the change was made in the editor, through the API or CLI, by an MCP tool, by Moshky, or by a site sync. You can download any of them as a JSON file to compare or analyze, and you can restore one if a change did not work out.

See and restore earlier versions in the editor

1. Open the workflow and choose Version History.
2. Under Saved changes, you see the saved earlier versions, newest first. Each one shows when it was replaced, who replaced it, how (Editor, Moshky, MCP, API, Restore) and how many nodes it had.
3. Choose Download to save a version as a JSON file.
4. Choose Restore, then confirm. The workflow goes back to that version right away.

Restoring never loses work. The version you are replacing is saved in the same list first, so you can undo a restore the same way. Restoring brings back the nodes, the name and the trigger. It does not turn the workflow on or off.

A workflow that mirrors a template cannot be restored until you detach it from the template.

Use the CLI

velaro workflow versions <id>
velaro workflow download <id> <version> --out version.json
velaro workflow restore <id> <version>

Use MCP tools

Ask your assistant, or call these tools directly: workflow_versions lists the saved versions, workflow_version_get returns one as JSON, and workflow_restore restores one.

Good to know

• Only changes to a workflow's nodes, name, trigger or on/off state create a version. Reordering a list or other housekeeping does not.
• Each restore is recorded in the workflow's Activity Log entry with who restored which version.
• The older drafts and autosaves in Version History still work as before; they are kept separately from these saved changes.