> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Author a graph of agent instructions, tools, and transitions, then review its structure in a saved draft.

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.

<Note>
  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](/agents-platform/overview#current-availability).
</Note>

## Build a reviewable graph

<Frame caption="Recording pending: build and review a workflow draft. Follow the written guide below.">
  <img src="https://mintcdn.com/threetonelabs-c2efc9c8/RV32i5440UZIaFHA/images/tutorials/recording-pending.webp?fit=max&auto=format&n=RV32i5440UZIaFHA&q=85&s=55f66d2eef49d8c92c9ac46f84bace35" alt="Recording pending for workflow draft authoring. No playable video is available yet." width="1600" height="900" className="w-full h-auto aspect-video" loading="lazy" noZoom data-path="images/tutorials/recording-pending.webp" />
</Frame>

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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](/agents-platform/deploy/versioning), then read the draft back and compare its node and edge identifiers.
  </Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="Do I need a workflow for a simple agent?" id="faq-workflows-needed">
    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.
  </Accordion>

  <Accordion title="Does a valid phone-number node enable a transfer?" id="faq-workflows-transfer">
    No. The node describes a requested handoff. Telephony provisioning and a working conversation path are separate requirements; see [telephony](/agents-platform/deploy/telephony/overview).
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.