Skip to Content
DocsIntegrationsZapier / Make / n8n

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:

  1. 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.
  2. Workflow webhook action — Add a Webhook action to a specific workflow for more targeted forwarding with conditions and filters.
  3. 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:

  1. Create a new Zap
  2. Choose Webhooks by Zapier as the trigger
  3. Select Catch Hook
  4. Copy the webhook URL provided

Make:

  1. Create a new Scenario
  2. Add a Webhooks → Custom Webhook module as the trigger
  3. Click Add to create a new webhook
  4. Copy the webhook URL provided

n8n:

  1. Create a new Workflow
  2. Add a Webhook trigger node
  3. Set the HTTP Method to POST
  4. Copy the Production URL (available after saving and activating the workflow)

Step 2: Add the URL to BuildVoiceAI

  1. Go to Settings → API & Webhooks
  2. Paste the webhook URL from your automation platform
  3. 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:

  1. Verify your automation platform receives the data
  2. See all available fields and map them to your actions
  3. 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 call
  • from_number / to_number — caller and recipient phone numbers
  • duration_seconds — how long the call lasted
  • sentiment — positive, neutral, or negative
  • summary — AI-generated call summary
  • transcript — full conversation transcript
  • recording_url — link to the call recording
  • provider — 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

  1. Go to Settings → API & Webhooks
  2. Generate an API key if you haven’t already
  3. Use the API trigger endpoint with your key

Platform Setup

Zapier:

  1. Add a Webhooks by Zapier action (not trigger)
  2. Choose POST
  3. Enter https://app.buildvoiceai.com/api/trigger-call
  4. Add header: Authorization: Bearer your_api_key
  5. Set the payload type to JSON
  6. Map the phone field to the contact’s phone number

Make:

  1. Add an HTTP → Make a request module
  2. Set the URL to https://app.buildvoiceai.com/api/trigger-call
  3. Set the method to POST
  4. Add header: Authorization: Bearer your_api_key
  5. Set the body type to JSON
  6. Add the phone field with the contact’s number

n8n:

  1. Add an HTTP Request node
  2. Set the method to POST
  3. Enter https://app.buildvoiceai.com/api/trigger-call
  4. Add header: Authorization: Bearer your_api_key
  5. Set the body content type to JSON
  6. Add the phone field

Webhook Security

BuildVoiceAI signs every webhook with HMAC-SHA256 when a signing secret is configured. Each request includes:

HeaderDescription
X-Prosody-SignatureHMAC-SHA256 hex digest of the payload
X-Prosody-TimestampUnix 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:

AttemptDelay
1st attemptImmediate
2nd attempt1 second after failure
3rd attempt2 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

  1. Trigger: call_ended webhook from BuildVoiceAI
  2. Filter: duration_seconds > 30 and status = completed
  3. Action: Search for contact by from_number in Salesforce/Pipedrive/Close
  4. Action: Create or update contact with call summary as a note
  5. Use case: Automatically logging qualified calls to CRMs that BuildVoiceAI does not natively integrate with

Real-Time Slack Alerts

  1. Trigger: call_ended webhook
  2. Filter: sentiment = positive and duration_seconds > 60
  3. Action: Send Slack message to #new-leads with caller number, summary, and sentiment
  4. Use case: Immediate team notification for hot leads

Google Sheets Call Log

  1. Trigger: call_ended webhook
  2. Action: Append row to Google Sheets with date, caller, agent, duration, sentiment, summary
  3. Use case: Simple call reporting for clients who prefer spreadsheets

Appointment Follow-Up

  1. Trigger: call_ended webhook
  2. Filter: summary contains appointment-related keywords
  3. Action: Create Google Calendar event
  4. Action: Send confirmation SMS via Twilio
  5. Use case: Automated booking flow for calls where appointments are discussed

Negative Sentiment Escalation

  1. Trigger: call_ended webhook
  2. Filter: sentiment = negative
  3. Action: Send email to account manager with transcript link
  4. Action: Create task in Asana/Monday.com
  5. Use case: Ensuring unhappy callers get prompt human follow-up

CRM Lead → Outbound Call

  1. Trigger: New contact created in your CRM (via CRM’s native Zapier/Make integration)
  2. Filter: Contact has a phone number and is tagged “New Lead”
  3. Action: POST to BuildVoiceAI API to trigger an outbound qualification call
  4. Use case: Automatically qualifying inbound leads with an AI agent

Choosing Your Platform

PlatformBest ForCost
ZapierSimplest setup, non-technical usersFree tier available, paid plans per task
MakeVisual workflow builder, complex branching logicMore cost-effective at high volumes
n8nFull control, self-hosted option, no per-execution costsFree (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.

Last updated on