Workflows
Build your first workflow
Create a workflow, add and connect blocks, set their inputs, test the draft and publish it. About ten minutes.
Guide2 min readUpdated 23 October 2026
This guide builds a small support-triage workflow: it takes a customer email, classifies it, and sends billing questions to an agent and everything else to Slack. The same steps work for any workflow.
Before you start
- At least one agent with a model key. AI blocks (Agent, Knowledge lookup, Classify, Extract, Guardrail check, MCP tool call) all act through one of your agents. See Create an agent.
- Credits for the AI blocks you test: Agent, Classify and Extract cost 1 credit each time they run.
- A Slack incoming webhook URL if you want the Slack block.
Steps
- 1
Create the workflow
Open Workflows in the sidebar and create a new workflow. Give it a name. The designer opens with a Start block on the canvas.
- 2
Define the inputs on Start
Select the Start block and add its Inputs, for example
emailandmessage. Each input is text; required inputs can't be empty when a run starts. Later blocks read them as{{input.email}}and{{input.message}}. - 3
Add blocks from the palette
Open Blocks, search or browse the groups (AI, Tools, Actions, Logic, Data) and drag a block onto the canvas, or click it to add it. Add a Classify block, a Condition, an Agent block and a Slack message.
- 4
Connect them
Drag from a block's exit to the next block. Classify has one exit per label plus Other, so connect the
billingexit to the Agent block and the others to Slack. Select a connection to remove it. - 5
Fill in each block's settings
Select a block to open its settings. Classify: pick an agent (its model does the sorting), set Text to classify to
{{input.message}}and add labels with a description each. Agent: pick the agent and set Message to the text it should answer. Slack: paste the Incoming webhook URL and write the message. A block with problems shows Issues with this block. - 6
Test the draft
Click Test run, fill in the inputs and run it. The run panel shows each block's status, input, output, tokens and time as it goes. Fix what's wrong and test again; test runs don't pay the outbound run credit, but their Agent and AI blocks cost the same as live.
- 7
Publish
Click Publish. The current draft becomes the live version. The webhook trigger and the API only ever run the published snapshot; keep editing and publish again when the draft is ready.
You're done when
The workflow shows as published, a test run finishes with status succeeded, and Runs lists it with its duration and tokens.
If something goes wrong
Publish is refused
The designer checks the whole graph before publishing: every block needs its required settings, connections must lead somewhere, and the workflow must stay within 50 blocks and 100 connections. Open the issues indicator in the designer toolbar (Things to check before running) and fix each item.
A Classify or Agent block fails with a credits error
AI blocks spend credits. Top up in Billing, then run again. See Running out of credits.
My changes don't show up in webhook runs
Live runs use the published snapshot. The designer shows when the draft has unpublished changes; publish again to make them live.
Still stuck?
Email us with what you tried and any request id. A person replies.