Skip to main content
Deploying saves the current canvas into the version history and points your external API triggers at the new snapshot.

​
How to deploy

Use the deploy button at the top right of the canvas. On a Flow that has never been deployed, it is the [Deploy] button; on a deployed Flow, it is the [Update to ver.N] button (N is the next number). Clicking it opens a confirmation popover:
  • Changes in this deploy a per-block summary of what differs from the last deploy. Your last checkpoint before shipping.
  • Release note (optional) appears in the version list’s note column. Left empty, a default note is attached.
  • View version history jumps to the Versions page.
Click the [Update] button (or [Deploy] button) and you’re done. New runs use the new version immediately; in-flight runs finish on the version they started with.

​
[Deploy] button states

  • With an empty canvas, the button is disabled.
  • Right after a deploy, with no new Draft changes, it switches to Deployed and can’t be clicked: there are no no-op deploys.
  • Edit the Draft and it becomes the [Update to ver.N] button again. That button doubles as the “unpublished changes” indicator.

​
Reading the change list

Changes in this deploy in the confirmation popover and Changes since the previous deploy in the version detail share one format. Each entry carries a prefix:
  • + added a new block appeared.
  • ~ modified the changed field is named alongside: prompt, model, settings, runtime, and so on.
  • - removed a block or variable was dropped.
A modified entry reads like ~ Agent Review Summarizer followed by the field that changed. Two special cases:
  • A Flow’s first deploy shows as Initial deploy, with the whole configuration listed as additions.
  • Autosave snapshots compare against the previous autosave instead.
To eyeball two canvases, open each version’s Preview side by side.

​
Writing good release notes

Notes appear verbatim in the version list. Write for the person who will someday pick a rollback target. Good note:
“Tighten refund escalation. Add rule: escalate when user mentions chargeback. Resolves cluster #142.”
Poor note:
“Fixes.”
Referencing the cluster ID or improvement ID a deploy addresses makes later tracing fast. To publish from the CLI, see flows in the CLI.