Save and publish
Save a flow, manage its versions, link it to an agent, make it autonomous and export it.
A flow goes through three states: the draft you edit in the editor, the versions saved on the platform, and the version run by an agent. This page explains how to move from one to the other without surprises.
Auto-save and saving
The editor has two levels of saving:
| Level | Trigger | Effect |
|---|---|---|
| auto-saved | Automatic, on every change | Your changes are kept in your browser. Nothing is published yet. |
| Save | Click on the top bar button | The flow is sent to the platform and a new version is created. |
The Save button shows Saving…, then Saved. If something goes wrong, it switches to Failed and the reason is shown next to the button.
Important
Until you click Save, your changes only exist in your browser: your agents and colleagues do not see them. A flow that has never been saved cannot be linked to an agent.
Version conflict
If the flow has been changed elsewhere in the meantime (by a colleague, in another tab), saving is refused with the message "Version conflict: this flow has been modified elsewhere. Reload before saving." Reload the page, reapply your changes, then save again.
Check before saving
Before saving, review the canvas:
- no block carries the No next step badge;
- the Entry badge is on the right block;
- every conditional branch has a target and an otherwise fallback;
- the Email, SMS and Datastore blocks show no missing-tool warning.
Version history
Each save creates a new version. The version button in the top bar (for example v12) opens the Version history: each version is listed with its author and date, and the current version is marked current. This button appears as soon as the flow has been saved once.
View an older version
- Click the version button.
- Click a version in the list.
- The canvas shows that version as a preview, read-only. A banner shows "Preview of v8" with its author and date.
- Use the banner arrows to move to the older or newer version.
- Click Exit preview to go back to your current edit.
During the preview, the library, write actions and shortcuts are disabled, and auto-save is suspended: your current edit is left untouched.
Restore a version
From the preview, click Restore this version. The chosen version becomes the new current version (for example v13 if you were on v12). Restoring deletes nothing: the history stays intact.
Link a flow to an agent
A flow runs through an agent: the agent provides the model, the voice and the phone number.
- Open the agent from the Agents page.
- Go to the Linked flow section: "Links a journey to the agent and pins the version to run."
- Click the Linked flow selector and choose the flow. Only saved flows are offered, with their current version.
- Choose the Version (see below).
- Save the agent.
The Open in the flow editor link goes straight to the linked flow. The cross in the selector Detaches the flow from the agent.
Followed version or pinned version
| Choice | Behavior |
|---|---|
| Latest — follows the flow's changes | The agent loads the latest saved version on every conversation. A change to the flow applies without touching the agent. |
| v1, v2… | The agent runs exactly this version. After a change to the flow, pin the new version (or switch to Latest). |
Choosing a flow pins its current version by default.
Tip
In production, pin a version: you can then edit and save the flow for your tests without changing the behavior of the live agent. Switch to the new version once it has been tested.
Linking a flow also attaches to the agent the tools this flow calls. See Flow tools added automatically.
Orphan reference
If the linked flow no longer exists (deleted, or never saved), the section shows "Orphan reference": the agent cannot run it. Click Detach, then choose an existing flow.
Make a flow autonomous
An autonomous flow runs without a user on the other end. This is required for a scheduled automation to launch it, for example to update a database every night or to send reminders.
- In the top bar, click Make autonomous.
- The flow is saved immediately and checked.
- If the check succeeds, the button becomes Autonomous. Otherwise, the reason for the refusal is shown and the flow goes back to non-autonomous.
From its entry, an autonomous flow must only contain blocks that do not wait for a reply: Datastore, MCP tool, HTTP request, Message without waiting for a reply, Human validation and Hang up. Click Autonomous to remove this status.
See Automations.
Import and export
| Action | Effect |
|---|---|
| Export JSON | Copies the flow document to the clipboard, as it is saved on the platform. The button shows Copied. |
| Import | Opens a .json file and creates a new flow from its content, opened right away in the editor. The original flow is not changed. |
An exported JSON re-imports identically: it is a simple way to copy a flow from one workspace to another, or to keep a backup. If the file cannot be read, the message "Import not possible." (or the precise reason) is shown for a few seconds.
Note
An imported flow is a new draft: click Save to publish it.
Delete a flow
Deletion is done from the Flows page (see Managing your flows). A flow linked to an agent cannot be deleted: detach it from each agent concerned first.
Learn more
Create an agent
Create an agent from scratch or from a template, then set its model, prompt, capabilities, knowledge, flow and webhooks.
Test an agent
Talk to an agent in writing or by voice, inject test variables and turn on the diagnostic log before going live.
Automations
Run an agent without inbound interaction, on a schedule or when an external system asks, and track its run history.
Tools
Create tools, test them, use them in a flow and link them to an agent.