Workflows

A workflow is a graph of blocks joined by arrows. Set an assistant's prompt to a workflow (on the Assistant tab, instead of free-form instructions) and every call to that assistant runs it:

• The conversation follows the blocks from the start block, one step at a time. A workflow can be as small as one conversation block holding your usual instructions.
• Trigger blocks start chains of server-side steps when the call is answered or after it ends, such as a CRM lookup or a Slack alert.

#How a workflow call runs

1. The call starts at the start block, which is always a conversation block.
2. In a conversation block the assistant talks, following that block's instruction, until one of the conditions on its outgoing arrows is true, for example "the caller wants to book".
3. Server-side blocks (tool, code, HTTP, app, set, condition, switch, AI, text, email) run one after another without waiting for the caller, up to 12 in a row.
4. The call ends at an end block, or when a transfer block puts the caller through.

#Variables in workflows

Conversation blocks can list variables to collect, such as order_number or preferred_day. Code, HTTP, app and AI blocks save their results as variables too. Any later block can use them as {{name}}, alongside the built-in variables.

#Global steps

Give a conversation block a global condition, such as "the caller asks for a person", and it can be reached from every other conversation step. You don't need to draw the same arrow from every block.

#Checks before saving

The editor warns about problems as you build: a block with no way out, blocks that nothing reaches, or a missing start. Anything that would strand a caller blocks saving until it is fixed. A workflow can have up to 200 blocks.

#Draft with AI

Describe what you want in the editor's AI box, for example "after each call, add a row to my sheet and alert Slack if it's urgent". It drafts the blocks and arrows for you to check and adjust.

Workflows are included in Pro.