Skip to main content
Workflows use a versioned publishing system. Each time you publish, a new immutable version is created. This section explains exactly how versioning works, how versions are incremented, and how to move between older and newer versions safely.

​
How Publishing Works

Every time you click Save & Publish, the workflow builder creates a new version.
Versions cannot be overwritten or edited after they are published.
  • Publishing always produces a new version number (v2, v3, v4…).
  • You can never modify an existing published version directly.
  • A version’s name and description are set during publishing and cannot be changed afterward.
Published versions form the permanent historical record of the workflow.

​
Version Numbers

Version numbers always increment by one, regardless of which version you publish from. For example:
  • If the latest version is v5 and you return to v3 and publish it,
  • The workflow becomes v6, containing the exact content of v3.
This ensures that:
  • Older versions remain intact.
  • The version history remains linear and predictable.

​
Viewing & Switching Between Versions

The Version Selector in the top navigation bar allows you to switch between any previously published version.
  • It shows the version you are currently viewing.
  • Opening the dropdown lists all published versions (with their names and descriptions).
  • Selecting one loads the workflow at that specific version.
Switching versions does not change which version is active — it only changes what you see in the builder.

​
Reverting to a Previous Version

Because published versions are immutable, reverting requires republishing. To revert:
  1. Open the Version Selector.
  2. Choose the version you want to return to.
  3. Click Save & Publish.
  4. (Optional) You can note that you are reverting to a specific version in the description of the new version for clarify.
This publishes a new version that is functionally identical to the older one, but with a new version number. Example:
  • You have versions v1 → v5.
  • You want to revert the workflow to how it was in v3.
  • Select v3, then publish.
  • v6 is created, containing the v3 logic.
This ensures all workflow changes remain explicitly traceable.

​
How the Active Version Is Determined

If the workflow is Active, the active version is always: The most recently saved and published version. Switching to older versions in the builder does not affect what is in production until you publish again. If the workflow is Inactive, publishing still creates a new version, but that version does not go live until the workflow is set back to Active.

​
Importing & Exporting Versions

The Ellipses Menu includes:
  • Import – Load a workflow from a JSON file.
  • Download JSON – Export the current state of the workflow as JSON.
  • Clone from Library – Create a new workflow from an existing one you own, have access to, or from any global public workflow.
These tools allow you to move versions between orgs or reuse frameworks across projects.

​
Summary

Versioning ensures workflows are traceable, recoverable, and safely managed.
The key principles are:
  • Publishing always creates a new version.
  • Published versions are immutable.
  • Reverting requires republishing an older version.
  • The active version is always the latest published version.
  • Version history is linear and preserved forever.
This system allows confident iteration while maintaining a clear audit trail of every change.