Skip to main content
Webhooks and API

Which Webhook Should I Use?

Compare every webhook in VoiceAIWrapper: what triggers it, where you set it, which engines support it, and which one fits your automation.

Written By voiceaiwrapper

Last updated 26 days ago

Webhooks let VoiceAIWrapper send data to your own tools, such as Make, n8n, Zapier, GoHighLevel or your own server, the moment something happens. There are several, and each one fires at a different moment. This article helps you pick the right one.

The short answer

If you want to…Use
Get call results, transcripts and recordings after each campaign callPost-call event webhook on the campaign
Look up a lead in your CRM right before the agent calls, and pass details to the agentPre-call context webhook on an outbound campaign
Skip a lead, or call it later, based on your own rulesPre-call context webhook with a decision. See Pre-Call Decisions: Call Later, Do Not Call and Reject.
Look up a caller before the agent answers, or turn the caller awayPre-call context webhook on an inbound campaign
Know when leads are added to a campaign or become invalidLeads event webhook on the campaign
Get an email summary after each inbound callCall Summary Email on an inbound campaign (an email, not a webhook)
Get every call of one VAW Native agent, inside or outside campaignsThe agent's Webhook URL
Choose which VAW Native agent answers a number, caller by callerThe number's Inbound webhook
Get your clients' form submissionsThe form's Configure Webhook

Campaign webhooks

These live on each campaign, in the Settings tab β†’ Webhooks and Emails. You can also fill them in at the Webhooks & email step when you create an outbound or inbound phone campaign. They work on every engine unless the table says otherwise.

WebhookWhen it firesEnginesWhat it's for
Post-call event webhookDuring and after each campaign call, once for every call eventAllCall results, transcripts and analysis, with the lead and campaign attached. See Post-Call Event Webhook.
Pre-call context webhook (outbound campaigns)Right before the agent calls each leadAllAdd details to the agent's prompt, or decide to call now, later or not at all. See Pre-Call Context Webhook.
Pre-call context webhook (inbound campaigns)Before the agent answers each callerVAW Native, Vapi, Retell AIAdd details about the caller, or turn the caller away. See Pre-Call Context Webhook.
Leads event webhookWhen leads are added, marked invalid because a call couldn't be started, or marked valid againAllKeep a CRM or sheet in step with the campaign's leads. See Leads Event Webhook.
Call Summary Email (inbound campaigns)After each inbound callAllAn email to your team. It needs SendGrid connected and the Inbound Call Summary template active. See Call Summary Emails.

The post-call and pre-call webhooks can carry Custom headers, for example an Authorization header your endpoint checks. On VAW Native, only the pre-call webhook sends them; its post-call requests are signed instead. See Add Custom Headers to Webhooks.

VAW Native webhooks

VAW Native, the built-in voice engine, has two more webhooks that work outside campaigns. Both are signed with your Pod's Webhook signing secret, so your server can check that the request really came from VoiceAIWrapper.

WebhookWhere you set itWhen it firesWhat it's for
Agent Webhook URLThe agent's Call Settings tab β†’ WebhooksEvery call and chat of that agent: call.started, call.ended, call.analyzed, and chat.started, chat.ended, chat.analyzedOne place for everything an agent does, campaign or not. See VAW Native Agent Webhooks: Events and Delivery.
Phone number Inbound webhookPhone Numbers β†’ open a number β†’ Inbound webhook tabBefore the agent answers a call on that numberReturn caller details, send the call to another agent, or reject it. See Route Inbound Calls with the Phone Number Webhook.

On VAW Native, a number that belongs to an inbound campaign follows the campaign while the campaign is scheduled, active or paused. The campaign's agent answers and the campaign's pre-call context webhook is asked. The number's own Inbound webhook isn't asked for those calls.

Other webhooks

  • Client form webhook. Each client form can send its submissions to a URL. Open the form and click Configure Webhook. Leave the URL empty to turn it off. See Build Client Forms.

Using more than one

You can combine them. A common setup for an outbound campaign:

  1. The Leads event webhook adds each new lead to your CRM.
  2. The Pre-call context webhook checks the CRM before each call and passes the lead's history to the agent.
  3. The Post-call event webhook writes the call result back to the CRM.

On VAW Native, if a campaign's Post-call event webhook and its agent's Webhook URL are both set, each receives the call events. If they're the same URL, it receives each event once.

Frequently asked questions

No. Campaign webhooks are set per campaign, and VAW Native agent webhooks per agent. Use the same URL on each campaign if you want everything in one place. The _campaign_metadata or campaign object in each request tells you which campaign it came from.

On VAW Native, each call's Webhooks tab shows every delivery and its response. On plans that include API & webhook logs, the API & Webhook Logs page lists webhook requests too. See API & Webhook Logs.