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
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.
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.
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:
- The Leads event webhook adds each new lead to your CRM.
- The Pre-call context webhook checks the CRM before each call and passes the lead's history to the agent.
- 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
Is there a webhook for the whole organization instead of each campaign?
Is there a webhook for the whole organization instead of each campaign?
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.
Can I see which requests were sent?
Can I see which requests were sent?
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.
My webhook isn't receiving anything.
My webhook isn't receiving anything.
Related articles
Was this helpful?
More in Webhooks and API
Pre-Call Context WebhookPre-Call Decisions: Call Later, Do Not Call and RejectLeads Event WebhookAdd Custom Headers to WebhooksStill need help? Share an idea