Branches and parallel paths
Conditions, switches, merges, waits and loops. One trigger can reach the live web, your databases and your files at the same time, and a single agent step reads all of it before deciding what follows.
Workflows
A run you can repeat.
Turn one good agent run into a graph: branches, parallel paths, a wait, a loop and a human decision where it matters. Every step can be inspected, tested on its own and replayed - and the whole thing runs on a schedule, a webhook or an incoming message.
23 stepsOne palette
4 triggersYou, a schedule, a webhook, a message
1 graphBranches and parallel paths
What you getA graph that follows
A graph that follows
the shape of the work.
A workflow is not a list of steps run in the order you typed them. A trigger fans out, the paths run side by side, and a merge brings them back together before the next decision.
A human where it matters
A human step stops the run and waits for you. Approve it from the page and the run continues with your answer; refuse it and nothing downstream happens.
Test one step, not the whole thing
Any step runs on its own, with the inputs you give it, before the workflow is published. When a run stops on a failure you see that step's inputs and its error, and you retry it from there.
An assistant on the canvas
A chat sits beside the editor and builds the workflow with you: it selects a node, changes the draft, runs it and reads the result back. Every change it makes is yours to undo.
The editorThe graph you draw
The graph you draw
is the graph that runs.
No export, no second representation of the same thing. Here a switch opens three cases and a default into four model steps; they come back together at an approval that waits for a person, and what comes out is written to a file. The assistant, the run history and a single-step test are in the same bar.
The paletteTwenty-three steps,
Twenty-three steps,
four ways to start.
A workflow is built from the services already on your account. Nothing here is a connector to buy, and nothing has to be wired before it can be used.
CountSteps
Triggers4Manual, schedule, webhook, incoming mail
Intelligence3A model, an agent, a generated medium
Tools4Search, fetch, convert, any HTTP call
Data5Query, write, save a file, memory, index a document
Services5Send and read mail, create and deploy a host, DNS records
Control6Condition, switch, merge, human, wait, loop
A step is billed for what it uses - a model turn, a search, a conversion - on the same balance as the agent.See full pricing
Questions
Workflows, in detail.
What can start a workflow?
Four things: you, a schedule, a webhook, or a message arriving in one of your mailboxes. The same graph runs the same way whichever one starts it.
What happens when a step fails?
The run stops there and keeps everything the earlier steps produced. From the run panel you see that step's inputs and its error, fix the cause and retry the step - the run continues from there.
Can the agent build one for me?
Yes. It has a workflow tool and can list, read, create, update, run and delete them. Creating or changing a workflow asks your permission, even in Auto mode.
Do workflows cost more than doing the work by hand?
No. The same steps cost the same credits as the agent doing them in a conversation. What a workflow adds is that it runs without you.