Workflow overview

A Flow is one agent workflow drawn on a canvas. It is made of small blocks. Blocks can be wired to each other, and each one can be edited and kept as a version.

​

When to create a new Flow

We recommend one Flow per purpose. If you are building an agent that answers customer inquiries and an agent that compiles a weekly competitor digest, create a Flow for each. If the inquiry agent needs refund handling and shipment tracking, add blocks to the inquiry Flow.

​

The four block types

Blocks are units of execution. Add them from the toolbar at the top of the canvas. The dashed lines between blocks are wires: they spell out the execution order and the path data flows along.

​

How a run flows

1. A Trigger fires (an API call, an incoming webhook, a schedule).
2. The Flow enters the first Agent block. It reasons, pulls context from Memory and Knowledge, and can call Tools.
3. Once the Agent produces its answer, the Action blocks wired after it run one after another.
4. The entire run is recorded as a trace you can inspect later.

​

Draft and Published

A Flow has two states.

• Draft is the working copy you are editing now. It does not affect real users until you publish.
• Published is the version real users are on. It does not change until you publish again.

Edits never touch production. Changes only take effect when you publish them yourself. See Publishing versions.

​

Learn more