Draft
Where edits land. Safe to iterate on — production runs are unaffected
Published
The stable version that API-triggered and scheduled executions run by default
Which version does an execution run?
An execution runs exactly one version of the agent, and edits made in a draft do not apply until published.Running a draft from the UI
When running from the platform, the run modal has a version selector in the top right. Use it to run any version — including unpublished drafts — which is the recommended way to test changes before publishing.Running a specific version via API
agentExecutePost accepts an optional version field in the request body. Pass a version number to run that exact version — published or not — for example to smoke-test a draft programmatically before publishing it. When omitted, the latest published version is used.
Publishing
Publishing promotes a version to be the default used by API, schedule, and integration triggers (schedules pinned to a specific version keep it):- In the Builder, click Publish once you’re happy with the draft.
- Programmatically, use the
workflowPublishMCP tool or the corresponding API endpoint.

