Skip to main content
Integrations

Connect Make, n8n, Zapier and Other Tools

Connect VoiceAIWrapper to Make, n8n, Zapier, HubSpot and other tools with webhooks and the API, with example automations you can copy.

Written By voiceaiwrapper

Last updated 26 days ago

VoiceAIWrapper doesn't have its own app in Make, n8n or Zapier, and there's no built-in HubSpot or Calendly connection. GoHighLevel is the only CRM with a native integration. You can still connect almost any tool, using two things every automation platform supports:

  • Webhooks send data out of VoiceAIWrapper when something happens: a call ends, leads are added, or a call is about to start.
  • The API lets your tools push data in, for example to add a lead to a campaign.

This article shows which one to use for common jobs, with example automations.

Using GoHighLevel? Use the native integration instead. It adds leads from workflows and writes call results back to contacts without any webhooks. See Connect GoHighLevel and Map Sub-Accounts.

What you can connect

You want to…UseWhere to set it up
Do something after every call (log it, update a CRM, send a message)Post-call event webhookCampaign β†’ Settings β†’ Webhooks and Emails
React when leads are added, or marked invalid or validLeads event webhookCampaign β†’ Settings β†’ Webhooks and Emails
Give the agent caller details before a call, or skip the callPre-call context webhookCampaign β†’ Settings β†’ Webhooks and Emails (outbound campaigns, and inbound campaigns on Vapi, Retell AI and VAW Native)
Get every call of one VAW Native agent, campaign or notAgent Webhook URLAgent page β†’ Call Settings β†’ Webhooks
Choose which agent answers a VAW Native numberNumber's Inbound webhookVAW Native Pod β†’ Phone Numbers β†’ open the number β†’ Inbound webhook tab
Add, update or remove leads from another toolLeads APICampaign β†’ Manage leads via API

For a fuller comparison of the webhooks, see Which Webhook Should I Use?.

Before you start

  • An account with your automation tool that can receive webhooks and send HTTP requests. In Make that's a webhook trigger and the HTTP module. In n8n it's the Webhook node and the HTTP Request node. In Zapier it's Webhooks by Zapier.
  • A campaign for the campaign webhooks and the Leads API.
  • An API key if you'll send data in. See Create and Manage API Keys. The Leads API needs a plan that includes Campaigns API.

Send data out with webhooks

Every webhook works the same way: your automation tool gives you a URL, and you paste it into VoiceAIWrapper. VoiceAIWrapper then sends a request to that URL each time the event happens.

  1. In your automation tool, create a new scenario, workflow or Zap that starts with a webhook trigger. Copy the URL it gives you.
  2. In VoiceAIWrapper, open the campaign, then Settings β†’ Webhooks and Emails.
  3. Paste the URL into the webhook field you need, for example Post-call event webhook.
  4. Optional: under Custom headers, click Add header to send something like an Authorization header your tool can check. See Add Custom Headers to Webhooks.
  5. Click Save Settings.
  6. Make a test call, or add a test lead, so your tool receives a first sample. Most tools use that sample to let you pick fields in later steps.

Each campaign has its own webhook settings. If you want the same automation for several campaigns, paste the same URL into each one and use the campaign details in the data to tell them apart.

What the post-call webhook sends

The post-call event webhook forwards every event of each call in the campaign, so one call sends several requests. Each request tells you which campaign and lead the call belongs to.

  • On VAW Native, the events are call.started, call.ended and call.analyzed. Use call.analyzed when you want the summary and analysis. The campaign and lead are inside the call object, as campaign and lead.
  • On Vapi, Retell AI, ElevenLabs and Bolna, the events are your provider's own events, passed straight through. VoiceAIWrapper adds _campaign_metadata and, when the call has a lead, _lead_metadata.

In your automation, add a filter right after the trigger so only the event you need goes on. Otherwise one call runs your automation several times. See Post-Call Event Webhook.

What the leads event webhook sends

The leads event webhook fires when leads are added, when a lead is marked invalid during a call, and when a lead is marked valid again. The event field is leads.added, leads.marked_invalid or leads.marked_valid, and the leads come as a list. See Leads Event Webhook.

Pre-call webhooks need a fast reply

The Pre-call context webhook is different: VoiceAIWrapper waits for your reply before calling or answering, and uses what you send back. Your automation must reply quickly with a JSON object. On VAW Native and on inbound calls, VoiceAIWrapper waits up to 5 seconds. For outbound calls on other engines, it waits up to 30 seconds.

That rules out tools that answer a webhook straight away with their own fixed reply. Use a tool that lets you build the reply yourself, such as n8n's Respond to Webhook node or Make's webhook response module. See Pre-Call Context Webhook.

Send data in with the API

To add leads from a form, a CRM or a spreadsheet, call the Leads API from your automation:

  1. Open an outbound campaign and its Manage leads via API tab.
  2. Under Select API, choose Add Lead, and under Code Format choose cURL.
  3. Copy the code example. It already contains the campaign's address and your selected key.
  4. In your automation tool, add an HTTP request step and copy over the method, URL, the Authorization: Bearer header and the body. n8n's HTTP Request node can import the cURL command directly.
  5. Map fields from earlier steps into the body.

Send phone numbers in E.164 format, such as +14155550123, and leave out empty fields instead of sending null. Full details are in Add Leads Automatically with the API.

Leads you add to an active campaign can be called right away during its calling window. On VAW Native each call uses AI credits; on Vapi, Retell AI and ElevenLabs it uses minutes on your provider account.

Beyond leads, the API can also manage campaigns, clients and more on plans that include Platform API. See API Reference Overview and Rate Limits.

Example automations

These are starting points. Field names in your tool depend on the sample data it received.

Log every finished call in a spreadsheet

  1. Trigger: webhook (the campaign's Post-call event webhook).
  2. Filter: keep only the final event. On VAW Native, that's call.analyzed.
  3. Action: add a row to Google Sheets or Airtable with the lead's name and phone, the campaign name and the call summary. On VAW Native they're in the call object's lead and campaign; on other engines, in _lead_metadata and _campaign_metadata.

Send new form leads to a calling campaign

  1. Trigger: a new submission in your form tool (Typeform, Jotform, a Facebook lead form and so on).
  2. Action: HTTP request to the Leads API Add Lead endpoint, with the phone number formatted as E.164.
  3. Optional: use the Leads event webhook to confirm the lead was added, and alert your team if it's later marked invalid.

Update HubSpot after each call

  1. Trigger: webhook (Post-call event webhook), filtered to the final event.
  2. Action: find the HubSpot contact by the lead's phone number or email.
  3. Action: add a note with the call summary, or update a property such as last call outcome.

Personalise calls with CRM data (n8n or Make)

  1. Trigger: webhook (the campaign's Pre-call context webhook).
  2. Action: look up the lead in your CRM.
  3. Reply: respond to the webhook with the values your agent's prompt uses, such as their plan or last order. Your reply can also tell VoiceAIWrapper to call later or not at all. See Pre-Call Decisions: Call Later, Do Not Call and Reject.

Troubleshooting

Check the URL was saved in the right campaign and field, and that your scenario, workflow or Zap is turned on (many tools only listen while you're testing or after you publish). Then place a test call. Requests and responses are listed under API & Webhook Logs on plans that include them. See My Webhook Isn't Receiving Data.

The post-call event webhook sends every event of the call, not one request per call. Add a filter so only one event type continues.

Check the API key is enabled, the phone number is in E.164 format, and the body has no null values. The API & Webhook Logs page shows the exact response. See API & Webhook Logs.

No. Use webhooks and the API as shown above. GoHighLevel is the only native CRM integration.