Enroll Contact (Create Run)
Changed onManually enroll a contact into a workflow, starting a new run immediately. The workflow must be enabled (status: live) — an unenabled workflow returns 422. The contact must belong to the same workspace.
Some step types are skipped at enrollment rather than executed — notably page (show_page_step) and internal sequence/plumbing steps, which only make sense inside a funnel. This list is non-exhaustive; standalone automations run the action and split steps documented under Workflows::Step.
Request
- Base URLhttps://myworkspace.myclickfunnels.com/api/v2
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Integer id or obfuscated public_id of the workflow.
Request body
Example request
{
"run": {
"contact_id": "CtAbcd",
"skip_communication": false
}
}Response
Created
Example response
{
"id": 501,
"public_id": "RnXxYz",
"workflow_id": 101,
"contact_id": 9001,
"contact": {
"id": 9001,
"public_id": "CtAbcd",
"email_address": "jane.doe@example.com",
"first_name": "Jane",
"last_name": "Doe",
"phone_number": null
},
"current_step_id": null,
"event_id": null,
"type": null,
"status": "completed",
"skip_communication": false,
"completed_at": "2025-06-02T10:30:00.000Z",
"paused_at": null,
"created_at": "2025-06-01T09:00:00.000Z",
"updated_at": "2025-06-02T10:30:00.000Z"
}Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info