Skip to main content

The Workflow Builder

The builder is where you draw a phone conversation as a state machine — a top-down tree of nodes, each one a phase of the call. You drag nodes from a palette onto a canvas, connect them with labelled edges, edit them in a right-hand inspector, and publish when it’s ready.
Voice Workflows are in alpha. Open them in Agent Studio → the left sidebar → Workflow.

Opening the builder

In Agent Studio, open the Workflow item in the left sidebar (it carries an Alpha badge). The builder renders inline in the studio, so you can switch between it and the rest of the agent’s configuration without leaving the page.
Workflow appears in Developer Mode. If you don’t see it in the sidebar, turn on Developer Mode in the studio.
If you’re new to the feature, start with the Voice Workflows overview to understand what a workflow is and how it differs from a normal single-prompt agent.

The canvas

The center of the builder is the canvas — the tree of your conversation.
  • Add nodes by dragging them from the node palette on the left. The palette is grouped by family: Conversational (nodes that speak and own a caller turn), Internal (nodes that run instantly with no caller turn), and Terminal (the End Call node). See Node Types for every node.
  • Connect nodes top-down. Every node has an input handle on top and an output handle on the bottom. Drag from one node’s bottom output to the next node’s top input to create an edge. Workflows flow downward.
  • Every edge shows its condition as a label on the canvas, so you can read the routing at a glance — an unconditional “else”, a natural-language Prompt condition, or a deterministic Equation. You author these in the Inspector and the details live on the Transitions page.

Mark the Start node

One node is the Start node — where the call begins. Select a node and mark it as the Start node so the engine knows which phase opens the conversation. The opening node is the one that greets the caller (its First Message, if set).

Layout tools

Two tools keep a growing tree readable:

Auto-arrange

Lays the whole graph out as a clean top-down tree — handy after you’ve been dragging nodes around or right after loading a template. Loading a template auto-lays-out for you.

Fullscreen

Expands the canvas to fill the screen for large flows. Press Esc to exit.

The right sidebar

A collapsible sidebar on the right holds four tabs.
Edits whatever you’ve selected. Select a node to edit its fields (prompt, First Message, the variables it extracts and requires, model/voice overrides, and so on — see Node Types). Select an edge to open the edge condition editor and choose how that transition fires — Unconditional, Prompt, or Equation. Conditions are explained on the Transitions page.
The sidebar is collapsible — collapse it to give the canvas more room while you’re laying out the tree, then reopen it to edit a node or edge.

The toolbar

ButtonWhat it does
TemplatesStart from a prebuilt flow — Lead Qualification, Appointment Booking, Support Triage, or Blank. Loading one auto-arranges into a top-down tree. See Templates.
ValidateRuns the engine validator and fills the Issues tab with errors and warnings.
SavePersists a draft. A draft does not run on live calls — only the published version does.
PublishMakes the agent run this workflow on real calls (switches the agent into workflow mode). See Publishing.
Test callLaunches a web call so you can talk to the workflow in your browser. Publish first so the agent actually runs the workflow.
ClearEmpties the canvas.
Enabled / DisabledWhen Disabled, calls ignore the workflow and fall back to the normal agent — without unpublishing.
Save keeps a draft; only the published version runs on calls. Save while you iterate, then Publish when the flow is ready — and remember Test call talks to the published workflow, so publish before you test. More on the draft-vs-live model is on the Publishing & Going Live page.

Build your first flow

1

Open the builder

In Agent Studio, open Workflow in the left sidebar (Developer Mode). Either start from a Template or build on a blank canvas.
2

Drag in your nodes

From the left palette, drag in the nodes you need — a Conversation node to greet, Collector nodes to capture details, Condition nodes to branch, and an End Call node to finish. They’re grouped Conversational / Internal / Terminal. See Node Types.
3

Connect them top-down

Drag from each node’s bottom output to the next node’s top input. The flow reads downward, and every edge shows its condition as a label.
4

Mark the Start node

Select your opening node and mark it as the Start node — that’s where the call begins (and where the First Message greets the caller).
5

Declare variables & set conditions

Open the Variables tab to declare the typed variables you collect, then select each edge and use the Inspector’s condition editor to set how it fires. See Transitions.
6

Tidy & validate

Click Auto-arrange to lay the tree out cleanly, then Validate and resolve any errors in the Issues tab (warnings won’t block you).
7

Save, publish, test

Save the draft as you go. When it’s ready, Publish to run it on real calls, then use Test call to talk to it in your browser. See Publishing & Going Live.

Where to go next

Node Types

Every node — Conversation, Collector, Condition, Set Variable, API Request, Transfer, End Call, and Global.

Transitions, Variables & the Director

How edges, conditions, typed variables, and the Director route each turn.

API Request Node

Call an external API mid-call and branch on the response.

Publishing & Going Live

Validate, publish, enable/disable, and put the workflow on real calls.