Flows

A flow is one of your business processes, written down in plain English and compiled into software. The hundredth run follows the same steps in the same order as the first, calls on an agent wherever the process needs judgement rather than a rule, stops and waits wherever the process says a person decides, and leaves a record of everything it did.

Flows are early access. They work, and they are still being finished, so give a new one a few supervised runs before you rely on it for anything you cannot afford to go wrong.

How one comes to exist

It begins as a conversation. You say what you want and your agent asks the questions a new starter would ask: what sets this off, what usually happens, what to do when it does not, and where you want to be asked before anything goes out. What comes back is a description in ordinary business words that you should read and recognise as your own process. There is no form to fill in.

That description is then checked for the gaps that would trip it up, and compiled. Compiling takes a while and happens in the background.

A build is not the finish line. You test the flow on your own real cases and confirm both the decision it made and what actually happened at the other end. Every correction you give is written down beside the process, so rebuilding honours it rather than arguing the point again. Once your real cases behave, the flow can be run: on demand, on a schedule, when a message arrives on one of your channels, or on an event from an outside system you have connected.

Write your first flow walks through all of that once.

Three shapes

Most flows are a fixed sequence: the steps and branches are settled when it is compiled and every run takes the same path, which is what you want for anything you may have to account for later.

Some are a sequence the AI walks step by step, doing the thinking at each step while the order is held for it, so it cannot run ahead or skip.

The third is a conversation the AI leads over a durable backbone that delivers each message, keeps one person's replies apart from another's, and holds the thread together for as long as the exchange takes. A flow's page names its shape: State machine for the fixed sequence, Runs in its chat for the one the AI walks step by step, and Agent flow for the conversation it leads. The list shows the last two on the flow's row.

Something simpler, one instruction on a clock or an eye kept on a page, is a scheduled task or a watcher; a flow is for when there is an order to it, rules, approvals or several people. A flow can also hand heavy work to a job and carry on when the job is done.

What the Flows pages show

Flows live under Dashboard > Flows (/manage/flows), across four tabs, and the sidebar row carries a count of the runs in progress. The page carries an Early access notice at the top.

Library lists every flow, grouped by what needs you: Needs attention (the last run failed, a run is waiting for your reply, the flow cannot be read, or a trigger has an error), Running now, Ready, Not accepted yet (no accepted build, so nothing can start it) and Off (all its triggers are off). Each row says what starts the flow, or "Started by hand", and shows a bar of its recent runs, one segment per run. Status and Trigger dropdowns narrow the list. Press Run on a row to start the latest accepted build; a flow that expects details asks you for them first. Edit opens the flow in a chat to change it. The row's menu also turns its triggers on or off, and the list's ... menu has Disable all triggers, which stops every trigger at once after you confirm.

Click a flow's name for its own page (/manage/flows/flow/<workspaceId>/<flowName>). Overview says what needs you, then the last run, the next run and the build. Below that are its triggers, each with an on/off switch, a state tag (On, Draft or Off), how often it has fired and a Test fire button; the accepted build with its acceptance tests; the details a run asks for; and the latest runs. Runs lists every run of that flow, Definition shows its steps and checks, and Projects says which projects it belongs to. A flow that has not been accepted yet says so there and tells you to compile it in its editing chat first.

Runs, the second tab, is the history of every flow: live ones first, then completed or failed, searchable, with a cancel on anything still running that asks you to confirm.

Open a run and the process is drawn as a map with the current step lit up, beside what went in, what came out, and a log of every step, decision, retry and question in order. Click an event and the map moves to the step it belongs to. It updates live, so you can watch one work. Your agent can also put that map in a tab beside the chat while you talk a flow over.

Providers lists the outside sources you have connected, what each has seen lately and whether it is switched on; on this page a provider means one of those sources, not an AI provider. Configs holds the settings a flow or a source needs, such as which inbox counts as the support inbox. Providers and Configs are shared across every project. Library and Runs follow the project you have chosen.

When a run asks you

Where the process says you decide, the run pauses and the question comes to you on the channel you already use, in ordinary words. You answer in ordinary words too.

The run picks up from exactly the step it stopped at, whether you reply in ten minutes or in three days, and it can pause more than once on the way through. Until you answer it sits in the list as suspended rather than finished, so nothing is lost while it waits for you.