Zapier, Make & n8n
BuildVoiceAI works with popular automation platforms through webhooks. By combining BuildVoiceAI’s post-call workflow actions with Zapier, Make, or n8n, you can route call data to virtually any application.
How It Works
The connection uses two mechanisms:
- Outgoing data — A BuildVoiceAI workflow sends call data to your automation platform via a Webhook action
- Incoming triggers — Your automation platform triggers outbound calls by sending requests to BuildVoiceAI’s trigger-call webhook
Sending Call Data to Your Automation Platform
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 webhook URL (available after saving and activating the workflow)
Step 2: Add a Webhook Action in BuildVoiceAI
- In BuildVoiceAI, go to Workflows and create or edit a post-call workflow
- Add a Webhook action
- Paste the webhook URL from your automation platform
- Save the workflow
Step 3: Test the Connection
- Make a test call with the agent assigned to this workflow
- After the call completes, the workflow will fire and send data to your automation platform
- In your automation platform, verify the webhook received the payload
The webhook payload includes all call data: agent name, duration, phone number, sentiment, summary, transcript, and any metadata.
Triggering Calls from Your Automation Platform
To have your automation platform initiate outbound calls through BuildVoiceAI, send an HTTP POST request to your BuildVoiceAI webhook URL.
Getting Your Webhook URL
For GoHighLevel or HubSpot integrations, use the webhook URL shown on the respective integration page.
For API access (Agency plan), use the API trigger endpoint with your API key.
Platform Setup
Zapier:
- Add a Webhooks by Zapier action (not trigger)
- Choose POST
- Enter the BuildVoiceAI webhook URL
- 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 the BuildVoiceAI webhook URL
- Set the method to
POST - 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 the BuildVoiceAI webhook URL
- Set the body content type to JSON
- Add the
phonefield
Example Automation Recipes
Call Ends → Create Notion Page
- Trigger: BuildVoiceAI webhook fires after call completes
- Action: Create a page in a Notion database with the call summary, sentiment, and caller details
- Use case: Building a searchable knowledge base of customer conversations
Negative Sentiment → Send Alert Email
- Trigger: BuildVoiceAI webhook fires after call completes
- Filter: Check if the
sentimentfield equals “negative” - Action: Send an email via Gmail or SendGrid to the account manager
- Use case: Escalating unhappy callers to a human representative
Call Completes → Update Google Sheet
- Trigger: BuildVoiceAI webhook fires after call completes
- Action: Append a row to a Google Sheet with call date, caller phone, agent, duration, sentiment, and summary
- Use case: Maintaining a call log spreadsheet for reporting or client review
New Lead in CRM → Trigger Qualification Call
- Trigger: New contact created in your CRM (via the CRM’s native Zapier/Make integration)
- Filter: Contact has a phone number and is tagged as “New Lead”
- Action: Send a POST request to BuildVoiceAI’s webhook to trigger an outbound qualification call
- Use case: Automatically qualifying inbound leads with an AI agent
Call Ends → Create Follow-Up Task
- Trigger: BuildVoiceAI webhook fires after call completes
- Filter: Sentiment is “positive” and summary contains interest indicators
- Action: Create a task in Asana, Trello, or Monday.com assigned to a sales rep
- Use case: Ensuring hot leads get prompt human follow-up
Payload Reference
The webhook payload sent by BuildVoiceAI contains the following fields:
| Field | Type | Description |
|---|---|---|
call_id | string | Unique identifier for the call |
agent_id | string | UUID of the agent that handled the call |
agent_name | string | Display name of the agent |
direction | string | inbound or outbound |
phone_number | string | Caller’s phone number (E.164 format) |
duration_seconds | number | Call length in seconds |
started_at | string | ISO 8601 timestamp |
ended_at | string | ISO 8601 timestamp |
sentiment | string | positive, neutral, or negative |
summary | string | AI-generated call summary |
transcript | array | Array of transcript entries with role, content, and timestamp |
When setting up your first automation, start with a simple recipe (like appending to a Google Sheet) to verify the data is flowing correctly before building more complex workflows.