Workflow Versions Guide

Overview

A version is a saved snapshot of your entire workflow — every node and its configuration, the connections between nodes, your AI agents' prompts, and the scripts those agents have generated. Each time you save a change, the platform records a new version. This gives you a complete history of how a workflow evolved: you can see what changed and who changed it, open any earlier state to inspect it, and roll back to it if you need to.

Versioning happens automatically — there is nothing to switch on. Versions are kept per workflow and are visible to everyone who can open that workflow. The platform retains a rolling history of recent versions for each workflow, so the list stays focused on the changes that matter.

Use Cases

• Checkpoint before a risky change: save your work, give the version a label, then experiment freely knowing you can return to the labelled point
• Recover an earlier state: roll a workflow back to how it looked before a change that didn't work out
• Understand what changed: review the timeline to see each save, who made it, and when
• Mark milestones: label important versions (for example, "Approved for production") so they're easy to find later
• See exactly what a run used: from the execution history, identify the precise version — including the generated scripts — that a past run executed

Where to Find Version History

1. Open the workflow
2. Click History in the top bar
3. Select the Version tab

You'll see a timeline of versions with the newest at the top. Each entry shows:

• the version's label, or "Saved <date>" if it hasn't been labelled
• a v<number> badge
• who saved it and how long ago
• a current marker on the version you're currently viewing

If you haven't saved any changes yet, you'll see: "No saved versions yet. A version is created each time you save."

What Creates a Version

A new version is created whenever you save a change to the workflow. That includes:

• adding, removing, or reconnecting nodes
• editing a node's configuration
• changing an AI agent's prompt
• editing an agent's generated script by hand
• turning an agent's Regenerate script option on or off

A few things to keep in mind:

• Saving with no changes does not create a duplicate version. If nothing has changed since the last save, the platform keeps the existing version rather than adding an identical one.
• Running a workflow does not, on its own, create a new version. If an AI agent generates or regenerates its script during a run, that script is saved back into the version the run used — so the version always reflects exactly what ran, without adding extra entries to your history.

Note — your agents' scripts are part of the version. For scripting and data-transformation agents, the generated script is saved together with the prompt. When you restore or view a version, you get both the prompt and the exact script that belonged to it. Custom agents work differently: their output is tied to each run rather than stored on the version.

Labeling a Version

Labels make important versions easy to recognise in the timeline. To add or change one:

1. Open History → Version
2. Click the ⋯ menu on the version you want to label
3. Select Edit label
4. Type a label (up to 255 characters) — for example, "Before new Send Email flow"
5. Click Save

To remove a label, clear the field and save; the version goes back to showing "Saved <date>".

Viewing a Past Version

Click any version in the timeline to open it. The workflow opens in View mode: a yellow bar appears at the top showing the version number and date, and the canvas becomes read-only so you can inspect the workflow exactly as it was without changing anything.

While in View mode you can:

• Switch to another version using the dropdown on the yellow bar
• Return to the live workflow by clicking the ✕ on the yellow bar

Viewing a version never changes your current workflow — it's a safe, read-only look at the past.

Restoring a Version

Restoring replaces your current workflow with the contents of an earlier version.

1. Open History → Version
2. Click the ⋯ menu on the version you want to restore
3. Select Restore
4. Confirm in the dialog

When you confirm, your current workflow is replaced with the selected version. Restoring is non-destructive: before the swap, your current state is saved as a new backup version, so nothing is lost. A confirmation message tells you which version you restored to and which new version holds your previous state, with a link to view that backup.

Note — restore is just another save. The restored workflow becomes your new current state and appears as the newest entry in the timeline. To undo a restore, simply restore the backup version it created (or any earlier version).

Versions and Executions

Every workflow run records the exact version it executed, so you can always trace a result back to the workflow that produced it.

1. Open History → Executions
2. Each run shows its status, duration, who ran it, and a version badge

What you see on a run	What it means
Version N	The run executed against version N. Open that version to see the exact nodes, prompts, and scripts it used
—	An older run from before version tracking was available; no version is recorded for it

Click a run to open it in read-only View mode, the same way you view a version.

Best Practices

• Label your milestones. A short label like "Approved – Q3 baseline" is far easier to find later than a list of timestamps
• Checkpoint before big edits. Save (and optionally label) before reworking a complex workflow, so there's a clean point to return to
• Use Restore instead of manual undo. To go back to an earlier state, restore that version rather than rebuilding it by hand — restore is exact and keeps a backup of your current work
• Use the run's version badge to reproduce results. When a run produced unexpected output, open the version shown on that execution to see precisely what ran, including the generated scripts

Common Questions

I saved but no new version appeared. A version is only created when something actually changed. Saving an unchanged workflow reuses the existing version instead of adding a duplicate.

Turning on "Regenerate script" added a version, but running it didn't add another — why? Turning the option on is a change, so saving it creates a version. The run then regenerates the script and saves it back into that same version, rather than creating a second one. The result is one version that holds both your change and the script the run produced.

I restored a version and my latest work seems gone. It isn't — restoring first saves your previous state as a new backup version. Open History → Version (or use the link in the confirmation message) and restore that backup to get your work back.

A run shows "—" instead of a version. That run happened before version tracking was enabled, so no version was recorded for it. Newer runs will show the version they executed.

Can other people see my versions? Yes. Versions belong to the workflow, so anyone who can open the workflow can view its version history, labels, and restore points.