The repair shop wants its automation to ask Camille for a pickup time before it tells her the bike is ready. Its agent changes the draft and saves it as a version, then an administrator publishes it. An automation has one draft, the versions saved from it, and at most one published version, much like code and its commits.
Draft. Members and their agents edit it freely. Nothing in the draft reaches a contact.
Version. A snapshot of the draft that never changes, with a message saying what changed. Its author saves it as major (3 after 2.1) when it changes the graph's shape or a trigger, and as minor (2.2) otherwise.
Published version. The version whose triggers are active. Only administrators of the workspace publish, because publishing starts messaging contacts.
Restore. Copies a version into the draft, without losing the draft's changes or touching the published version.
Publishing refuses a version that would fail a run, naming the trigger or step of each problem: a value read before any step writes it, an undeclared attribute, a condition comparing values of different kinds, or an AI model or reasoning effort Heythere does not offer. getAutomation lists them for the draft as draftProblems.
A run stays on the version it started with. If Camille is already answering when the shop publishes, she finishes on the previous version, so publishing never breaks a conversation under way.
In the API
Every operation is a REST endpoint and, unless marked REST only, an MCP tool of the same name. The OpenAPI document describes their parameters, payloads, and errors.
- POST
createAutomationVersionVersion an automation's draft
/api/organizations/{organizationId}/workspaces/{workspaceId}/automations/{automationId}/versions - GET
listAutomationVersionsList automation versions
/api/organizations/{organizationId}/workspaces/{workspaceId}/automations/{automationId}/versions - GET
getAutomationVersionGet an automation version
/api/organizations/{organizationId}/workspaces/{workspaceId}/automations/{automationId}/versions/{automationVersionId} - PUT
publishAutomationVersionPublish an automation version
/api/organizations/{organizationId}/workspaces/{workspaceId}/automations/{automationId}/published-version - POST
restoreAutomationVersionRestore an automation version
/api/organizations/{organizationId}/workspaces/{workspaceId}/automations/{automationId}/versions/{automationVersionId}/restore