Flow Versioning

Flows support draft/published workflow and version history. Only published flows execute when triggered. Edits create drafts that must be published to go live.

Flow Statuses

Publishing

When you publish a flow, the current steps are snapshotted into the version history and the flow's version number increments. The flow status changes to published.

POST /connect/v1/flows/:id/publish

// Response
{
  "id": "...",
  "version": 3,
  "status": "published",
  "published_at": "2026-04-16T12:00:00Z"
}

Version History

Every publish creates a version record. You can view the full history and revert to any previous version.

GET /connect/v1/flows/:id/versions

// Response
[
  { "version": 3, "published_at": "2026-04-16T12:00:00Z" },
  { "version": 2, "published_at": "2026-04-15T09:30:00Z" },
  { "version": 1, "published_at": "2026-04-14T15:00:00Z" }
]

Reverting

Revert replaces the current flow steps with the snapshot from a previous version. This creates a new version (so you never lose history).

POST /connect/v1/flows/:id/revert/2

// Restores steps from version 2
// Creates version 4 (new publish)
// Flow status becomes "published"

Admin UI

In the flow detail page, you'll see:

• A Draft or Published badge next to the flow name with the version number
• A Publish button (when draft) or Publish New Version button (when published)
• A Version History panel listing all published versions with "Revert" buttons