Skip to main content
GET
Get Lead Execution History
Read only Returns the history of a single lead’s path through the workflow, oldest transition first. Entries whose destination node has since been deleted are left out. Each history entry records one move between nodes: from_node (null for the first entry, or when that node has been deleted) and to_node (each with id, label, node_type and config), the transition_reason, transitioned_at, and metadata. When the lead left a VOICE_CALL node, metadata carries the matching call_id and call_status so you can pivot into Get Call Details to inspect the transcript. IDs inside the history (entry, node and call_id) are raw, without a prefix; Get Call Details accepts a raw call ID. The response also contains:
  • lead: the lead’s id (lead_...), phone_number, dynamic_variables (an array of key and value pairs) and notes.
  • execution: the lead’s current execution (id, current_node_id, status and entry_time), or null if the lead has not started. A lead stopped because its number is on the workspace’s DNC list has status dnc_blocked, and its last history entry has transition_reason Stopped: number is on the DNC list.
  • all_nodes and all_edges: every node and edge in the workflow, so you can draw the full graph around the lead’s path.
Use this endpoint for per-lead debugging, quality review, and rendering a timeline view in your dashboard. A removed lead’s history stays readable.

When to use this

  • Debugging a stuck lead: confirm which node the lead is waiting on (execution.current_node_id) and how long it has been there.
  • Quality review: produce a per-lead timeline for compliance or operations reviewers.
  • Drill-down from a dashboard: pivot from a workflow lead row into the full path the lead took.
  • Reporting on path coverage: sample lead histories to confirm conditional branches are being followed as expected.
For aggregate lead progress across the workflow, use List Workflow Leads. For the call record of a specific voice-call step, use the call_id returned by this endpoint with Get Call Details.

Path parameters

Errors

  • 404 Not Found is returned when the workflow or lead does not exist, or the lead is not enrolled in the workflow.

Authorizations

Authorization
string
header
required

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

Path Parameters

workflowId
string
required

Workflow ID

Example:

"workflow_abc123"

id
string
required

Lead ID

Example:

"lead_abc123"

Response

Lead execution history returned successfully.

success
enum<boolean>
required
Available options:
true
error
enum<boolean>
required
Available options:
false
statusCode
integer
required
Example:

200

message
string
required
Example:

"Success"

data
object
required
timestamp
string<date-time>
required