Freeze the draft and make it the one customers run
POST/api/flows/:flow/publish
SAVING IS NOT PUBLISHING.
flows.definition is the DRAFT — what the editor reads and writes.
Publishing freezes it into an immutable version and repoints the flow at
it.
Conversations ALREADY inside the flow are pinned to the version they started on and are untouched. Before versioning, deleting a node and saving stranded every conversation sitting on it: the visitor pressed the button, nothing happened, no error, forever — and nobody was told.
It validates again even though saving did. A draft can predate a validation rule, or come back from a rollback to a version written before one existed, and publishing is the moment the graph becomes somebody else's problem.
Request
Responses
- 200
- 401
- 403
- 404
- 422
The flow, now pointing at its new version.
Not authenticated. code: account_disabled means the member's seat was deactivated in this workspace: the session is over even though the token was not revoked (clients sign out and clean up).
Authenticated but not allowed.
Resource not found (or not visible to the current tenant).
The request failed validation.