Skip to main content

Version Lifecycle

Each workflow can have multiple versions. The version to run is selected by the {versionID} path segment when triggering.

Version States

Locking

Once a version is locked, it cannot be modified. This is perfect for production versions that need to stay rock-solid.

Visibility

Versions have three visibility levels:

Making a Version Unlisted

Setting allowed_to_share: false on a public version has no effect. Public versions are never downgraded.

Creating a New Version

Use the Create Version endpoint:
This sets v2 as the latest version.

Triggering a Specific Version

Pass the version in the trigger URL’s {versionID} path segment:
For example, trigger v1 with POST https://api.eachlabs.ai/v1/workflows/trigger/WF_ID/v1.
Last modified on August 14, 2026