Workflows
What workflows are for
Workflows (beta) chain your agents with logic, tools and actions on a canvas. What they can do, what they can't, and how a run works.
Concept2 min readUpdated 23 October 2026
A chat reply answers one message. A workflow does a whole job: read an incoming email, sort it, pull out the order number, look the order up, draft a reply, check the draft and send it. Workflows are in beta and live under Workflows in the app's sidebar.
How a workflow is built
- Blocks are the steps: a Start block, then AI blocks (Agent, Knowledge lookup, Classify, Extract, Guardrail check), tools (MCP tool call, HTTP request), actions (Send email, Slack message, Webhook), logic (Condition, Delay), data (Set value) and End. See Workflow blocks.
- Connections join one block's exit to the next block. Classify has one exit per label plus Other; Condition has True and False; Guardrail check has Pass and Fail.
- Variables carry data between blocks:
{{input.field}}for the run's input,{{steps.<id>.output}}for an earlier block's output and{{last.output}}for the block just before. See Templates and variables.
Draft, publish, run
A workflow is a draft until you publish it. Test run in the designer runs the draft with input you type and shows each block as it goes. Publish freezes the current draft as the live version; live runs only ever use that published snapshot, so you can keep editing the draft safely. There is one published snapshot at a time, not a version history.
A published workflow runs in two ways: a webhook URL with a token, or POST /v1/workflows/run with your secret API key. See Run a workflow.
What workflows don't do
- There are no scheduled (cron) triggers. Call the webhook or the API from your own scheduler instead.
- There are no workflow templates and no assistant that draws a workflow for you. You build it block by block.
- Only the latest published snapshot is kept. Earlier published versions aren't stored.
What a run costs
| Block | Credits |
|---|---|
| Agent | 1 per reply, like any chat reply |
| Classify, Extract | 1 each time they run |
| Guardrail check | 1 only when an AI-judged check (prompt injection, toxicity, off-topic or an AI rule) is selected; free otherwise |
| Knowledge lookup, Condition, Delay, Set value, Start, End | Free |
| A live run with an HTTP, Webhook, Slack or Email block | 1 credit when the run starts; test runs don't pay it |
Limits
50 blocks and 100 connections per workflow, 25 blocks executed per run, 280 seconds per run, 30 runs a minute and 5 at once per account. All of them are in Workflow limits.
Still stuck?
Email us with what you tried and any request id. A person replies.