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

# Workflows

> Choose the right Persistence workflow: a conversation flow, the agent lifecycle canvas, or an event-to-call workflow.

Persistence uses **workflow** in three related places. Pick the one that matches the job, then keep labels consistent with the dashboard.

<Columns cols={2}>
  <Card title="Conversation flow" icon="git-branch" href="/build/conversation-flow">
    Visual call script. Use it when the conversation must follow stages, branch on known conditions, or run tools in a fixed order.
  </Card>

  <Card title="Agent workflow" icon="waypoints" href="/build/agent-workflow">
    Lifecycle canvas on the agent. Use it to attach knowledge, pre-call and post-call integrations, extraction, and webhooks around the call.
  </Card>
</Columns>

<Card title="Event-to-call workflows" icon="zap" href="/deploy/workflows">
  Workspace **Workflows**. Turn CRM, HTTP, or API events into outbound calls, delays, and follow-ups without rebuilding the agent prompt.
</Card>

## When to use each

| You need to… | Open |
| - | - |
| Control what the agent says, which tool runs next, and when the call ends | **Agents** → create a **Conversation Flow** |
| Configure what happens before, during, and after every call for one agent | That agent → **Workflow** |
| Start calls from new leads, poll an API, or chain retries and follow-ups | Sidebar **Workflows** |

A Conversation Flow agent still has the **Agent** / **Workflow** switcher. The canvas is the call script. The **Workflow** view is the lifecycle around that script.

Event-to-call workflows sit beside campaigns. Use a campaign for a contact list you already have. Use **Workflows** when each call should start from an incoming event, a previous step's result, or a [Run via API](/deploy/workflows/api) request.

## Recommended path

<Steps>
  <Step title="Choose how the agent talks">
    Start with a [single-prompt agent](/build/single-prompt) unless the call must follow a fixed order. Switch to a [conversation flow](/build/conversation-flow) when stages, branches, or tool order matter.
  </Step>

  <Step title="Wire the call lifecycle">
    Open **Workflow** on the agent. Attach knowledge bases, pre-call lookups, in-call tools, extraction, webhooks, and post-call integrations.
  </Step>

  <Step title="Test, then publish">
    Preview in the browser, then run a [simulation](/test/simulation) suite before you route a number or campaign.
  </Step>

  <Step title="Start live traffic">
    Assign a [phone number](/deploy/phone-numbers) or [number pool](/deploy/number-pools), or build an event-to-call [workflow](/deploy/workflows) that dials the published agent.
  </Step>
</Steps>


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