Skip to main content
POST
Activate a workflow and start execution for all leads
Legacy endpoint - deprecated. Unversioned endpoints are scheduled for removal on July 31, 2026. Use Update Workflow Status with action: "activate" for new /v1 integrations. This endpoint remains available for existing integrations until then.
Activates a workflow that is currently in draft status. Once active, the workflow begins processing every enrolled lead through the configured sequence on the next scheduling tick. Calls and other node actions start firing immediately, so the workflow must be fully configured, nodes, edges, agent assignments, dynamic variables, before you call this endpoint. The status returned in the response transitions from draft to active.

When to use this

  • Going live: you have finished building the workflow in the dashboard or via API and are ready to start dialling enrolled leads.
  • Reactivation after edits: you took a workflow back to draft to apply structural changes and you want to put it back into production.
If the workflow is currently paused, use Resume Workflow instead, that endpoint is the correct verb for paused → active. Use this endpoint only for draft → active.

Pre-flight checklist

Before activating, confirm:
  • Every non-terminal node has at least one outgoing edge (List Edges).
  • Every VOICE_CALL node has an assigned agent and outbound phone number.
  • The prompt for each agent references only variable keys returned by Get Variable Keys.
  • Concurrency settings match your Concurrency and limits policy.
Activation is the moment outbound calls start firing, so the cost of a mis-configured workflow at this point is real.

Path parameters

Errors

  • 404 Not Found is returned when the workflow does not exist.
  • 409 Conflict is returned when the workflow is not in draft status (use Resume Workflow for paused workflows).
  • 400 Bad Request is returned when the workflow’s graph fails pre-activation validation (for example a node missing required configuration).

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-organization-id
string
required

RSA encrypted organization ID (base64 format)

Example:

"BASE64_ENCRYPTED_ORG_ID_HERE"

Path Parameters

id
string
required

Response

Workflow activated successfully