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.
Quick Setup with Zapier Copilot
Zapier Copilot can scaffold the entire Zap from a natural-language prompt — the fastest way to get this wired up.1. Create the Zapier Webhook in Atllas
Before opening Zapier, set up the connection point on the Atllas side:- Go to the Integrations tab in Atllas
- Click Inbound and select Zapier Webhook
- The webhook appears on your integrations page
2. Configure the campaign
Every webhook-triggered call uses the campaign attached to the webhook, so set it up before going live:- On the webhook you just created, click Phone Call Settings
- Configure the script, voice, voicemail, follow-ups, and any other call behaviour
- Save
3. Open Zapier and prompt Copilot
In Zapier, click Create → Zap and open Copilot. Describe what you want. For example, for HubSpot:When a new contact is added into HubSpot, send out a call using Atllas.Copilot will scaffold a two-step Zap: a HubSpot New Contact trigger and an Atllas → Invoke Call action.
4. Connect your accounts
Copilot will prompt you to connect:- HubSpot — sign in and grant access
- Atllas — authorize Zapier and select the Zapier Webhook you created in step 1
5. Map your data
In the Atllas action step, map the contact fields:- Phone Number ←
phone - First Name ←
firstname - Last Name ←
lastname - Email ←
email
6. Test and turn on
Click Test step to send a real test call. Once it works, toggle the Zap on. From this point on, every new HubSpot contact will trigger an AI call.Manual Setup
If you’d rather build the Zap by hand:1. Create the Zapier Webhook in Atllas
- Go to the Integrations tab in Atllas
- Click Inbound and select Zapier Webhook
- The webhook appears on your integrations page
2. Configure the campaign
- On the webhook you just created, click Phone Call Settings
- Configure the script, voice, voicemail, follow-ups, and any other call behaviour
- Save
3. Build the Zap
- Create a new Zap in Zapier
- Choose a trigger from any app (e.g. “New Lead in HubSpot”)
- Add Atllas action — Select Invoke Call
- Connect your Atllas account — Authorize Zapier to access your Atllas data and select the Zapier Webhook you created
- Map your data — Connect lead information to call fields
- Test and activate your Zap
Fields
When configuring the Atllas Invoke Call action in Zapier, the following fields are available:| Zapier Field | Required | Description |
|---|---|---|
| Phone Number | Yes | Recipient’s phone number — include country code (e.g. +15555555555) |
| Campaign | Yes | Which AI Calling campaign to use for the call |
| First Name | No | Used for personalization during the call |
| Last Name | No | |
| No | Used for email follow-ups | |
| Company Name | No | Adds context to the AI’s conversation |
| Job Title | No | |
| Address Line 1 | No | |
| City | No | |
| State | No | |
| Zip Code | No | |
| Country | No | |
| Notes | No | Any additional context for this specific contact |
The campaign is selected when you create the Zapier Webhook in Atllas, not per-call. There is no
campaign_id field in the payload.Customising the Phone Call
Every call triggered by the integration uses the campaign attached to the Zapier Webhook. The webhook owns every call setting — voice, call script, voicemail message, follow-ups, call forwarding, keypad navigation, language, background ambiance, and so on. To change call behaviour:- Go to the Integrations tab in Atllas and find your Zapier Webhook
- Click Phone Call Settings on the webhook
- Edit any setting — voice, script, follow-ups, voicemail, etc.
- Save
Tips
- Test your Zap with a non-production phone number first
- Make sure your campaign prompt is configured before connecting
- Monitor your first few calls to verify data is mapping correctly
- Check your Atllas calling credits before enabling high-volume automation

