Workflow Leads
Get Lead History
View the step-by-step path of a single lead through a workflow, including every node entered, outcomes, and time spent at each step.
GET
Get lead history in a workflow
Returns the complete history of a single lead’s path through the workflow. Each entry records a node the lead entered: the
node_id, the node_type, the human-readable label, the start and end timestamps, the per-step status, and, for VOICE_CALL nodes, the call_id so you can pivot into Get Call Details to inspect the transcript. Use this endpoint for per-lead debugging, quality review, and rendering a timeline view in your dashboard.
When to use this
- Debugging a stuck lead: confirm which node the lead is waiting on 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.
call_id returned by this endpoint with Get Call Details.
Path parameters
| Parameter | Description |
|---|---|
workflowId | The workflow ID, for example wfl_m3v7zb9rk2px. |
id | The workflow-lead enrollment ID, for example wlead_p3q8zv5bk2mx. |
Response shape
Each entry in thehistory array represents one node visit, with at least:
node_id,node_type,label: the node visited.status: the per-step status (for examplecompleted,waiting,failed).started_at: when the lead entered the node.ended_at(orends_atfor waiting nodes): when the lead left the node.call_id: present forVOICE_CALLnodes; pivot into the call log via this ID.
Errors
404 Not Foundis returned when the workflow or lead does not exist, or the lead is not enrolled in the workflow.
Request
Response
Related endpoints
- List Workflow Leads: see every lead in the workflow.
- Get Call Details: full transcript for the
call_idreturned above. - Get Workflow: workflow summary alongside per-lead drill-downs.
- List Nodes: fetch node definitions referenced in the history.
Authorizations
Pass your API key as a Bearer token in the Authorization header.
Response
200 - application/json
Success.
Example:
"wflead_abc"
Example:
"wf_abc123"
Example:
[
{
"node_id": "node_abc",
"node_label": "Initial Outreach Call",
"node_type": "VOICE_CALL",
"status": "no_answer",
"call_id": "call_aaa",
"entered_at": "2024-03-01T10:00:00.000Z",
"exited_at": "2024-03-01T10:00:45.000Z"
},
{
"node_id": "node_time",
"node_label": "Wait 2 hours",
"node_type": "TIME",
"status": "completed",
"call_id": null,
"entered_at": "2024-03-01T10:00:45.000Z",
"exited_at": "2024-03-01T12:00:45.000Z"
},
{
"node_id": "node_xyz",
"node_label": "Follow-up Call",
"node_type": "VOICE_CALL",
"status": "completed",
"call_id": "call_bbb",
"entered_at": "2024-03-01T12:00:45.000Z",
"exited_at": "2024-03-01T12:03:10.000Z"
}
]
Get lead history in a workflow