This no-code integration is perfect for non-technical users. If you’re a developer and need more control or custom functionality, check out Custom Webhooks.
Zapier is free to get started, but more complex automations (multi-step Zaps, premium app connections, higher task volume) may require a paid Zapier plan. See Zapier’s pricing for current tiers.
You do not need to create an outbound webhook manually for Zapier. When you set up an outbound Zapier integration, an outbound webhook is created automatically and labelled Managed by Zapier in your integrations list. The Outbound button on the integrations page is only for Custom Webhooks.
Quick Setup with Zapier Copilot
Zapier Copilot can scaffold the Zap from a natural-language description — the fastest way to forward call results into any app.1. Open Zapier and prompt Copilot
In Zapier, click Create → Zap and open Copilot. Describe what should happen after each call completes. For example, for HubSpot:When I receive a “Call Finished” trigger from Atllas, find the matching contact in HubSpot by phone number and create a call engagement.Copilot will scaffold a Zap with an Atllas → Call Finished trigger and a HubSpot action.
2. Connect your Atllas account
In the trigger step, click Connect and authorize Zapier to access your Atllas data.3. Send a sample payload
Run a test call in Atllas. Once it completes, Zapier receives the result and the trigger step populates with real fields you can map. Until Zapier sees a real payload, the field picker in later steps will be empty.4. Configure the action and turn it on
In the HubSpot step, Copilot will pre-fill mappings using the call data. For a call engagement on a HubSpot contact, the typical mapping is:- Search by:
call.recipient.phoneNumber - Engagement Type: Call
- Engagement Body ←
call.summary - Call Recording URL ←
call.recording - Call Duration ←
call.duration
Manual Setup
If you prefer to build the Zap by hand:- Create a new Zap in Zapier
- Set trigger — Choose Atllas and select Call Finished
- Connect your account — Authorize Zapier to access your Atllas data
- Choose an action — Select what app to send data to (e.g. “Create Deal in HubSpot”)
- Map call data — Connect call results to your target app fields
- Test and activate your Zap
Available Data Fields
The outbound integration fires once per call (event typecall.finished) with a JSON payload identical to the Custom Webhooks outbound payload. The following fields are available to map in your Zap:
Call
| Field | Description |
|---|---|
call.id | Unique call identifier |
call.status | finished, missed, or failed |
call.duration | Call length in seconds |
call.recording | URL to the MP3 recording |
call.summary | AI-generated summary of the call |
call.tokensConsumed | Credits used for the call |
| Field | Description |
|---|---|
who | assistant or user |
what | What was said |
when | ISO timestamp |
| Field | Description |
|---|---|
call.analysis.lead_warmth | hot, warm, cold, dead, or unknown |
call.analysis.sentiment | positive, neutral, negative, or unknown |
call.analysis.justification | Explanation of the lead warmth and sentiment rating |
| Field | Description |
|---|---|
call.recipient.phoneNumber | Contact’s phone number |
call.recipient.firstName | |
call.recipient.lastName | |
call.recipient.email | |
call.recipient.address1 | |
call.recipient.city | |
call.recipient.state | |
call.recipient.zipCode | |
call.recipient.note | Custom notes passed when the call was triggered |
| Field | Description |
|---|---|
campaign.id | Source campaign ID |
campaign.name | Source campaign name |
| Field | Description |
|---|---|
type | Always call.finished |
timestamp | Unix epoch in milliseconds when the event was sent |
Popular Workflows
Update CRM with Call ResultsTrigger: Call Finished → Action: Update Contact in HubSpot/Salesforce
Map:
call.summary, call.analysis.lead_warmth, call.recording
Create Follow-up TasksTrigger: Call Finished (filtered by
call.analysis.lead_warmth = hot) → Action: Create Task in Asana/ClickUpMap:
call.recipient.firstName, call.summary
Log to SpreadsheetTrigger: Call Finished → Action: Add Row to Google Sheets
Map: All call data for reporting and analysis
Filtering Results
Use Zapier’s Filter step to route different call outcomes to different actions:- Hot leads → Create high-priority task
- Warm leads → Add to nurture sequence
- Cold / Dead leads → Update CRM status only
- Missed calls → Schedule retry
Tips
- Use filters to handle different call outcomes differently
- Set up error notifications in Zapier to catch integration issues
- Test with a few completed calls before scaling up
- Consider multi-step Zaps for complex workflows