Skip to main content
Workflows are in beta. The APIs documented here are stable to build against, but details may evolve before general availability.

​
What are Workflows?

A workflow is a graph of nodes — agent calls, WhatsApp messages, API requests, waits, retries and endings — connected by conditions. Once published, you run contacts through it: each contact becomes an execution that walks the graph, branching on call outcomes, extracted values and API responses.

​
Key Features

  • Versioned definitions — edits go to a draft; publishing freezes an immutable version, so running campaigns are never changed underneath.
  • Condition-based branching — every node routes onward through ordered cases evaluating call status, extracted fields, API responses or contact data.
  • Native retries and waits — retry nodes re-dial unreachable contacts on a schedule; time nodes pause between steps.
  • Two ways to run — a single-contact run endpoint for event-driven use, and campaigns with CSV/JSON contact uploads for batches.
  • Full observability — per-execution node-by-node history, and per-campaign reports with a node funnel keyed to your definition.
Start with the workflow guides for concepts, the definition schema and worked examples.

​
Endpoints

Batch runs live under the Workflow Campaign APIs, and per-contact progress under the Workflow Execution APIs.