Skip to main content
POST
Trigger an Outbound Agent Run by API Trigger Node
Outbound calling is temporarily disabled. Use the browser tester or incoming calls to test your agent. The reference below does not enable outbound calling.
Requires a Labs OAuth user access token with super_user and at least Editor access to the selected workspace. API keys are not accepted for this endpoint. See authentication. Use this endpoint when you want to start an agent run through an API Trigger node. The uuid comes from the API Trigger node in your agent. Add the node to your workflow and copy its auto-generated trigger_path. Use workflow_run_id from the response to later retrieve run details, recordings, and transcripts. Pass initial_context to inject runtime data as template variables into the agent’s prompt. See Using initial context. Pass telephony_configuration_id to route the call through a specific telephony configuration instead of your organization’s default. The id is shown on each row in Phone numbers.
This route expects an API Trigger node UUID (trigger_path). Do not pass a workflow UUID here. If you want to execute by Agent UUID, use Trigger an outbound agent run by Agent UUID instead.
Your telephony provider must be configured before outbound calls will connect. See Telephony for setup instructions.

Authorizations

Authorization
string
header
required

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

Path Parameters

uuid
string
required

Body

application/json
phone_number
string
required
initial_context
Initial Context · object | null
telephony_configuration_id
integer | null

Response

Successful Response

status
string
required
workflow_run_id
integer
required
workflow_run_name
string
required