Overview

Workflows let you build structured, step-by-step logic for your agent. Unlike playbooks, which let the model reason freely toward a goal, workflows follow a defined path - every step executes in order, exactly as you designed it.

Workflow canvas with connected playbooks and conditions
Connect steps and playbooks to define the path through a workflow.

Workflows aren’t purely scripted. You can embed playbooks, operators, set steps, and crews anywhere in the flow, giving you deterministic control with AI reasoning baked in wherever you need it.

How a workflow runs

A workflow executes the steps and branches you connect.

A workflow executes the steps and branches you connect. A condition selects a configured path; a listen step can wait for input; a tool step can call an external service. AI-capable steps, including playbooks, let part of the process reason dynamically without replacing the surrounding workflow structure.

For example, a returns workflow can collect an order ID, check eligibility, and follow separate eligible and ineligible branches. A playbook within that workflow could clarify the customer’s reason for returning an item, then exit into the next connected step.

Named variables let you pass captured values into later conditions, messages, and tool inputs. Configure those assignments explicitly instead of assuming every tool response becomes a variable. Read about stored values and context.

How agents work explains when to choose a workflow, a playbook, or both.

Creating workflows

From the Agent tab, click + in the right editor.

1

Add or create a workflow

From the Agent tab, click + in the right editor. Select an existing workflow or create a new one.

Plus button beside the Workflows heading
Add a workflow from the agent’s Workflows list.

You can also create workflows from within a workflow using the workflow step, or from the workflow CMS tab.

2

Name your workflow and add a trigger

Give your workflow a clear name and trigger. The trigger should cover both what the workflow does and when the agent should route into it - this is what the top-level agent and other playbooks read when deciding whether to call it.

Create workflow dialog with name and trigger fields
Give the workflow a name and a trigger that explains when to use it.
3

Design your workflow

On creation, you’ll be taken to the canvas to start building. Workflows added from the agent tab are automatically attached to your agent. Click × in the top right to return to the agent tab at any time.

4

Run your workflow

Press ‘Run’ in the top right, or use the shortcut  Shift + R  then initiate the workflow. When initiated from on the canvas, your workflow will run in isolation. When initiated from the agent tab, workflow can be called and will run with all previous state.

5

Iterate

When running a workflow in Voiceflow, you can see the full logs in real-time, along with canvas follow along. This makes it super easy to de-bug and improve your workflows quickly.

Steps

Steps are the building blocks of workflows, organized into four categories:

Actions

Actions let you keep your canvas clean without losing any functionality.

Workflow node with its Actions menu open
Open a workflow’s Actions menu to edit or manage the workflow.

To add an action, click any port and then click on empty canvas space to expose the step menu. This is also the fastest way to add steps without dragging from the sidebar.

Nesting workflows

Workflows can call other workflows using the workflow step.

Workflows can call other workflows using the workflow step. This lets you break complex processes into smaller, reusable pieces - build once, use across multiple workflows. For example, an identity verification workflow can be called from your returns flow, your account management flow, and your payment flow without duplicating the logic in each one.

Workflow step with a Select a workflow control
Call another workflow from a workflow step.

Workflows only run if they’re added to the agent, or referenced directly inside a workflow. If a workflow exists in your project but isn’t connected to either, the agent will never use it.

Entry conditions and required variables

Entry conditions and required variables can only be applied when a workflow is routed to directly by the agent.

Entry conditions and required variables can only be applied when a workflow is routed to directly by the agent. They’re not available when the workflow is called via a workflow step inside another workflow.

Entry conditions and required variables control when the agent can route into a workflow. Until they’re met, the workflow stays unavailable, so the agent won’t hand off to it no matter what the customer says. This gives you precise, rule-based control over when each workflow becomes reachable.

Entry conditions

Entry conditions are deterministic checks that must evaluate to true before the workflow can be routed to. If the checks don’t pass, the workflow stays unavailable for routing. For example, you could gate a support ticket escalation workflow so only users whose {account_type} variable is set to enterprise are able to escalate tickets to their account manager.

Workflow entry condition settings
Control when the agent can enter a workflow. Photo:

Required variables

You can also require that specific variables have a value before the agent can route in. Until every required variable is filled, the workflow stays unavailable. For example, require {order_id} before the agent can hand off to a returns workflow, so it never starts without the information it needs.

Workflow required variables menu
Specify the variables a workflow needs before it starts. Photo:

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.