Zapier, Make & n8n
BuildVoiceAI integrates with automation platforms through real-time webhooks. Every time a call starts or ends, structured call data is automatically forwarded to your configured webhook URL — no workflow action required.
How It Works
BuildVoiceAI connects to automation platforms in two ways:
- Automatic webhook forwarding — Configure a webhook URL in Settings, and every call event (
call_started,call_ended) is forwarded in real-time. No workflow setup needed. - Workflow webhook action — Add a Webhook action to a specific workflow for more targeted forwarding with conditions and filters.
- Incoming triggers — Your automation platform triggers outbound calls by sending requests to BuildVoiceAI’s API.
The automatic webhook forwarding is the recommended approach for Zapier, Make, and n8n. It sends all call events to your automation platform without requiring individual workflow actions.
Receiving Call Data (Automatic Webhook Forwarding)
Step 1: Create a Webhook Trigger in Your Platform
Zapier:
- Create a new Zap
- Choose Webhooks by Zapier as the trigger
- Select Catch Hook
- Copy the webhook URL provided
Make:
- Create a new Scenario
- Add a Webhooks → Custom Webhook module as the trigger
- Click Add to create a new webhook
- Copy the webhook URL provided
n8n:
- Create a new Workflow
- Add a Webhook trigger node
- Set the HTTP Method to
POST - Copy the Production URL (available after saving and activating the workflow)
Step 2: Add the URL to BuildVoiceAI
- Go to Settings → API & Webhooks
- Paste the webhook URL from your automation platform
- Click Save
That’s it — all call events for your agency will now be forwarded to your automation platform automatically.
For client-specific routing, configure the webhook URL on the Client Detail → API & Webhooks section instead. Client-level URLs override the agency default, so different clients can route events to different automation platforms.
Step 3: Test the Connection
Click the Send Test Webhook button in Settings. This sends a sample call_ended payload so you can:
- Verify your automation platform receives the data
- See all available fields and map them to your actions
- Confirm the connection works before any real calls happen
The test payload includes "test": true so your automation can filter out test events.
Step 4: Build Your Automation
In your automation platform, add actions that process the incoming call data. The webhook payload includes everything you need:
agent_name— which agent handled the callfrom_number/to_number— caller and recipient phone numbersduration_seconds— how long the call lastedsentiment— positive, neutral, or negativesummary— AI-generated call summarytranscript— full conversation transcriptrecording_url— link to the call recordingprovider— which voice provider handled the call (retell, vapi, bland, or elevenlabs)
See the Webhook Events reference for the complete payload format.
Triggering Calls from Your Automation Platform
To have your automation platform initiate outbound calls, send an HTTP POST request to the BuildVoiceAI API.
Getting Your API Credentials
- Go to Settings → API & Webhooks
- Generate an API key if you haven’t already
- Use the API trigger endpoint with your key
Platform Setup
Zapier:
- Add a Webhooks by Zapier action (not trigger)
- Choose POST
- Enter
https://app.buildvoiceai.com/api/trigger-call - Add header:
Authorization: Bearer your_api_key - Set the payload type to JSON
- Map the
phonefield to the contact’s phone number
Make:
- Add an HTTP → Make a request module
- Set the URL to
https://app.buildvoiceai.com/api/trigger-call - Set the method to
POST - Add header:
Authorization: Bearer your_api_key - Set the body type to JSON
- Add the
phonefield with the contact’s number
n8n:
- Add an HTTP Request node
- Set the method to
POST - Enter
https://app.buildvoiceai.com/api/trigger-call - Add header:
Authorization: Bearer your_api_key - Set the body content type to JSON
- Add the
phonefield
Webhook Security
BuildVoiceAI signs every webhook with HMAC-SHA256 when a signing secret is configured. Each request includes:
| Header | Description |
|---|---|
X-Prosody-Signature | HMAC-SHA256 hex digest of the payload |
X-Prosody-Timestamp | Unix timestamp when the request was signed |
Your signing secret is auto-generated when you save your webhook configuration. Find it in Settings → API & Webhooks (click the eye icon to reveal).
For verification details and code examples, see the Webhook Events reference.
Reliability
Webhook deliveries include automatic retries with exponential backoff:
| Attempt | Delay |
|---|---|
| 1st attempt | Immediate |
| 2nd attempt | 1 second after failure |
| 3rd attempt | 2 seconds after failure |
Only server errors (5xx) and rate limits (429) are retried. Client errors (4xx) fail immediately.
All delivery attempts are logged in the Delivery Log (Settings → API & Webhooks → Recent Deliveries) so you can debug issues.
Example Automation Recipes
Lead Capture to CRM
- Trigger:
call_endedwebhook from BuildVoiceAI - Filter:
duration_seconds > 30andstatus = completed - Action: Search for contact by
from_numberin Salesforce/Pipedrive/Close - Action: Create or update contact with call
summaryas a note - Use case: Automatically logging qualified calls to CRMs that BuildVoiceAI does not natively integrate with
Real-Time Slack Alerts
- Trigger:
call_endedwebhook - Filter:
sentiment = positiveandduration_seconds > 60 - Action: Send Slack message to #new-leads with caller number, summary, and sentiment
- Use case: Immediate team notification for hot leads
Google Sheets Call Log
- Trigger:
call_endedwebhook - Action: Append row to Google Sheets with date, caller, agent, duration, sentiment, summary
- Use case: Simple call reporting for clients who prefer spreadsheets
Appointment Follow-Up
- Trigger:
call_endedwebhook - Filter:
summarycontains appointment-related keywords - Action: Create Google Calendar event
- Action: Send confirmation SMS via Twilio
- Use case: Automated booking flow for calls where appointments are discussed
Negative Sentiment Escalation
- Trigger:
call_endedwebhook - Filter:
sentiment = negative - Action: Send email to account manager with transcript link
- Action: Create task in Asana/Monday.com
- Use case: Ensuring unhappy callers get prompt human follow-up
CRM Lead → Outbound Call
- Trigger: New contact created in your CRM (via CRM’s native Zapier/Make integration)
- Filter: Contact has a phone number and is tagged “New Lead”
- Action: POST to BuildVoiceAI API to trigger an outbound qualification call
- Use case: Automatically qualifying inbound leads with an AI agent
Choosing Your Platform
| Platform | Best For | Cost |
|---|---|---|
| Zapier | Simplest setup, non-technical users | Free tier available, paid plans per task |
| Make | Visual workflow builder, complex branching logic | More cost-effective at high volumes |
| n8n | Full control, self-hosted option, no per-execution costs | Free (self-hosted) or cloud plans |
All three work equally well with BuildVoiceAI webhooks. Choose based on your existing stack and technical comfort level.
When setting up your first automation, start with a simple recipe (like appending to a Google Sheet) to verify the data is flowing correctly. Use the Send Test Webhook button to populate sample data before building complex workflows.