Skip to main content
A workflow describes how an agent should move between tasks. Use it when different stages need different instructions or resources, such as collecting a request before preparing a handoff.
Workflow authoring and structural validation are available. A saved graph does not prove that its transitions, tool calls, or handoffs execute in a live conversation. Review current availability.

​
Build a reviewable graph

Recording pending for workflow draft authoring. No playable video is available yet.

Recording pending: build and review a workflow draft. Follow the written guide below.

Start with an existing agent, an editable branch, and a written description of the task’s entry and exit conditions.
1

Define the stages

Open the agent’s Workflows page. Describe what each stage needs to know, what it may change, and what ends that stage. Keep ordinary wording and tone in the base prompt rather than repeating it at every node.
2

Choose nodes and resources

The workflow contract includes start, override_agent, tool, standalone_agent, phone_number, and end nodes. Their presence in the contract does not establish live transfer or telephony support.An override_agent node can hold additional_prompt, additional_knowledge_base, and additional_tool_ids. Review those resources with the same care as the base agent’s attachments.
3

Check transitions

Each edge names a source and target. Each node’s edge_order must include every outgoing edge exactly once. Write clear conditions so a reviewer can explain which transition is intended for each example request.
4

Save the complete snapshot

Preserve the graph under the top-level workflow field of the agent draft, alongside name, conversation_config, and platform_settings. Follow versions and drafts, then read the draft back and compare its node and edge identifiers.

​
Structural checks

A nonempty workflow must have exactly one Start node. Edges must reference existing nodes, cannot return to Start, and must follow the permitted outgoing transitions for each node type. A node cannot have multiple unconditional outgoing edges. Tool-result conditions require a tool node. Validation can identify malformed structure. It cannot establish that a natural-language condition is unambiguous or that a downstream service will succeed. Prepare examples for the normal path, missing information, tool failure, and a request outside the workflow’s purpose.

​
Frequently asked questions

No. Start with a clear prompt and add a workflow when separate stages make the task easier to review. An empty workflow is valid authoring configuration.
No. The node describes a requested handoff. Telephony provisioning and a working conversation path are separate requirements; see telephony.