Webhook
Webhook node allow you to sync the result of Voice Agent runs to your external systems, like CRM or to other workflow orchestrator like Zapier or n8n.
Creating the Webhook Payload#
The payload can contain a valid JSON, and you can reference variables while constructing that payload. You can reference below variables while constructing the payload.
{{workflow_run_id}}Unique ID of the Agent run{{workflow_id}}ID of the Agent{{workflow_name}}Name of the workflow{{campaign_id}}ID of the campaign this run belongs to (empty for ad-hoc runs){{call_time}}ISO-8601 UTC timestamp of when the call was initiated{{initial_context.*}}Initial context variables{{gathered_context.*}}Extracted variables{{cost_info.call_duration_seconds}}Call duration{{recording_url}}Call recording URL{{transcript_url}}Transcript URL
For the full list of available variables, authentication options, and receiver examples, see the Webhook Payloads developer reference.
An example of the payload is given below
{
"call_id": "{{workflow_run_id}}",
"first_name": "{{initial_context.first_name}}",
"rsvp": "{{gathered_context.rsvp}}",
"duration": "{{cost_info.call_duration_seconds}}",
"recording_url": "{{recording_url}}",
"transcript_url": "{{transcript_url}}"
}When to use a webhook node#
Use a Webhook node when call results need to be sent to your CRM, helpdesk, analytics pipeline, automation tool, or backend system after the run reaches that part of the workflow.
Payload checklist#
- Include the run identifier and any variables your external system needs to match the call to a customer or record.
- Use gathered context for values extracted during the conversation.
- Include recording or transcript URLs only when your process is allowed to receive and store them.
- Test with sample data before connecting the webhook to a production automation.
Reliability guidance#
Your receiving endpoint should validate requests, handle retries safely, and avoid treating duplicate webhook deliveries as separate customer actions.