A workflow is a node-based orchestration that defines step-by-step execution for each record (row) in a workflow campaign cohort. Workflows are used when execution requires multiple steps, such as:
  • Calling an agent, waiting, then calling another agent
  • Calling external APIs and routing based on responses
  • Conditional routing across multiple paths
  • Controlled retries and failure handling per step

​
Core Concepts

​
Nodes

A workflow is composed of nodes connected by directed edges. Each node performs a single action (e.g., telephony call, wait, API call, conditional routing).
A workflow must have exactly one Start node, which is the main entry point for the execution flow. Start nodes cannot be deleted.

​
Workflow Variables

Workflow variables are the data fields used to control routing and execution. Values typically come from:

Campaign cohort CSV

Mapped to workflow variables at campaign setup time.

Node outputs

Mapped to workflow variables during execution (e.g., API response mapping, agent call output mapping).

​
System Variables

System variables provide runtime context, such as the current date and time. 
system_variables.current_datetime

​
Versions (Draft vs Committed)

Workflows support a draft/commit model for safe iteration:
  • Node-level changes can be saved during editing
  • Workflow-level validation is performed on commit
  • Campaigns execute against committed workflow versions by default
  • Production campaigns should always run on committed versions for stability