Skip to main content
Webhooks and API

Post-Call Event Webhook

Send every call event from a campaign to your own URL, with the lead and campaign attached, and see what each engine sends.

Written By voiceaiwrapper

Last updated 26 days ago

The post-call event webhook sends what happens on each campaign call to your own URL: call status, transcript, recording, analysis and cost, depending on the engine. Each request also says which campaign and which lead the call belongs to, so your CRM or automation can update the right record without looking anything up.

It takes a minute to set up. You need one URL that accepts POST requests with a JSON body, such as a Make, n8n or Zapier webhook trigger, or your own server.

Before you start

  • A campaign of any type: outbound phone, inbound phone or inbound widget.
  • The campaign in Draft or Paused. Settings are locked while a campaign is Active or Scheduled. Pause an active campaign, or move a scheduled one back to Draft, then come back.
  • A URL that accepts POST requests. On VAW Native it must start with https://.

Add the webhook to a campaign

  1. Open the campaign and go to the Settings tab.
  2. Open Webhooks and Emails.
  3. Paste your URL into Post-call event webhook.
  4. Optional: open Custom headers under the field and click Add header to send a header with every request, for example Authorization. See Add Custom Headers to Webhooks.
  5. Click Save Settings.

You can also fill it in at the Webhooks & email step when you create an outbound or inbound phone campaign.

A paused outbound campaign β†’ Settings tab β†’ Webhooks and Emails panel. The Post-call event webhook field holds a sample URL (https://hooks.example.com/calls) with its help text, the Custom headers row under it is expanded with one header (Authorization and a blurred value), and the Pre-call context webhook, Leads event webhook fields and the Save Settings button are visible below.

If your agent sent its events to your own tool before you synced it with VoiceAIWrapper, paste that old URL here. You'll keep receiving the same events, now with the campaign and lead attached. See Sync Webhooks So VoiceAIWrapper Can Track Calls.

If you see "Looks like you are trying to add our webhook URL. This can create an infinite loop. Please use a different URL.", you pasted a VoiceAIWrapper address. Use your own endpoint instead.

What each engine sends

The webhook receives one request per event, so a single call usually produces several requests. Which events you get depends on the campaign's engine.

EngineEvents you receiveFormat
VAW Nativecall.started, call.ended and call.analyzed for calls. For chats in an inbound widget campaign: chat.started, chat.ended and chat.analyzed.VAW Native's own format, signed. The call object includes campaign and lead; the chat object includes campaign.
VapiEvery server message Vapi sends about the call, such as status updates and the end-of-call report, including web widget calls.Vapi's own message, with _campaign_metadata and _lead_metadata added.
Retell AIEvery event Retell sends about the call, such as call_started, call_ended and call_analyzed. For chats in a widget campaign, Retell's chat events.Retell's own event, with _campaign_metadata and _lead_metadata added.
ElevenLabsThe post-call transcription event (post_call_transcription) once the conversation ends.ElevenLabs' own event, with _campaign_metadata and _lead_metadata added.
Bolna, Ultravox (legacy Pods)Every call event the engine sends.The engine's own event, with _campaign_metadata and _lead_metadata added.

For the exact fields of each engine's own events, see that engine's documentation. VAW Native events are described in VAW Native Agent Webhooks: Events and Delivery.

What VoiceAIWrapper adds (Vapi, Retell AI, ElevenLabs, Bolna, Ultravox)

The engine's event is passed through unchanged. VoiceAIWrapper adds two objects at the top level, unless the event already has a key with the same name:

{
  "_campaign_metadata": {
    "campaign_id": "Vm9pY2VDYW1wYWlnblR5cGU6MTIzNDU2Nw==",
    "campaign_name": "Spring renewals",
    "type": "OUTBOUND",
    "status": "ACTIVE",
    "tenant_id": "VGVuYW50VHlwZTox",
    "voice_provider_id": "VGVuYW50Vm9pY2VQcm92aWRlclR5cGU6MQ==",
    "assigned_client": { "id": "Q2xpZW50VHlwZTo0Mg==", "name": "Acme Dental" },
    "asset_group_id": null
  },
  "_lead_metadata": {
    "id": "Vm9pY2VDYW1wYWlnbkxlYWRUeXBlOjEyMzQ1Njc4",
    "first_name": "John",
    "last_name": "Doe",
    "email": "john@example.com",
    "phone_number": "+14155550182",
    "custom_fields": { "plan": "Gold" },
    "attempts_made": 1,
    "invalid_reason": null,
    "answered": true,
    "answer_type": null,
    "answered_at": "2026-10-15T14:03:10+00:00"
  }
}
  • _campaign_metadata is on every event. assigned_client names the client account the campaign is assigned to, or is null. tenant_id identifies your organization and voice_provider_id the Pod.
  • _lead_metadata is added when the call has a lead: outbound calls and inbound phone calls (an inbound caller who isn't a lead yet is added to the campaign as one). Web widget calls and chats have no lead, so they arrive without it.

VAW Native campaigns

On VAW Native the webhook receives the same events, in the same format, as an agent's own Webhook URL. The campaign and lead are inside the call object:

"campaign": { "id": "Vm9pY2VDYW1wYWlnblR5cGU6MzEy", "name": "Spring renewals", "type": "OUTBOUND" },
"lead": {
  "id": "Vm9pY2VDYW1wYWlnbkxlYWRUeXBlOjQ4MjE=",
  "first_name": "Sam",
  "last_name": "Lee",
  "email": "sam@example.com",
  "phone_number": "+15555550100",
  "custom_fields": { "plan": "Silver" }
}

Chat events from a widget campaign carry a chat object instead, with campaign but no lead.

If the agent also has a Webhook URL, both URLs receive every event. If both are the same URL, it receives each event once.

How requests are delivered

Vapi, Retell AI, ElevenLabs, Bolna, UltravoxVAW Native
RequestPOST with a JSON bodyPOST with a JSON body, signed in Standard Webhooks format
HeadersContent-Type, an x-tenant-id header that identifies your organization, and your custom headersContent-Type, User-Agent, webhook-id, webhook-timestamp and webhook-signature. Custom headers aren't sent on this webhook.
Wait timeUp to 30 secondsUp to 10 seconds for a 2xx response. Redirects aren't followed.
RetriesAfter a timeout or a connection error, up to 3 more tries, a minute apart. An error status from your endpoint isn't retried.4 attempts over about 15 minutes. Timeouts, connection errors and statuses 408, 429, 500, 502, 503 and 504 are retried.

On VAW Native, check the signature with your Pod's Webhook signing secret instead of a custom header. See Verify Webhook Signatures. Each call's Webhooks tab shows every delivery, its response, and a Resend button.

Answer quickly with a 2xx status and do the heavy work afterwards. Your endpoint will receive several events per call, and some arrive close together.

Troubleshooting

Check that:

  • The URL is saved in Post-call event webhook on the campaign that placed the call. Calls placed outside a campaign (test calls, one-off calls) don't use campaign webhooks.
  • On Vapi, Retell AI and ElevenLabs, the campaign's agent and phone number are synced, so the engine sends its events to VoiceAIWrapper. See Sync Webhooks So VoiceAIWrapper Can Track Calls.
  • On VAW Native, the URL starts with https:// and points to a public address. Open a call's Webhooks tab to see what happened.

For more checks, see My Webhook Isn't Receiving Data.

That's expected for calls without a lead: web widget calls and chats.

Each event is a separate request. Use the event type (for example call.analyzed on VAW Native or call_analyzed on Retell AI) to act only on the one you need, usually the last one, which carries the analysis.

On Vapi, Retell AI, ElevenLabs, Bolna and Ultravox, add it under Custom headers. On VAW Native, verify the request signature instead. See Add Custom Headers to Webhooks.