Zapier
Connect Aura to thousands of other apps using Zapier — 23 trigger events available
Zapier
Zapier lets you connect Aura to thousands of other apps without writing code. When something happens in Aura — someone books a call, you close a deal, a lead gets qualified — Zapier can automatically do something somewhere else: post to Slack, update Salesforce, send a Customer.io email, add a row to a Google Sheet.
Aura has 23 different things you can trigger off, covering the whole booking and pipeline lifecycle.
Zapier and our Partner API webhooks are different. Zapier is for no-code automations — point and click, no engineering needed. The Partner API is for developers building tighter integrations. Zapier has more trigger types (23 vs 14) because it's the consumer-grade option.
Getting it set up
Get your Aura API key
In Aura, go to Settings → API Keys → Create API Key. Copy the key it shows you. Aura only shows it once, so paste it somewhere safe immediately.
Find Aura in Zapier
On zapier.com, start a new Zap and search for Aura as your trigger app.
Connect your account
When Zapier asks, paste the API key. That's how it gets permission to listen to your events.
Pick a trigger and test it
Choose one of the 23 events below, then run a test. Zapier pulls a real example event from your account so you can see exactly what data is available to use in your next step.
All 23 triggers
We've grouped them by what's happening in the customer's journey.
Booking lifecycle
| Trigger | When it fires |
|---|---|
call.booked | Someone completes a booking through one of your links |
call.rescheduled | A scheduled call gets moved to a new time |
call.cancelled | A scheduled call gets cancelled |
call.closer_reassigned | An admin switches the host on an upcoming call |
Call lifecycle
| Trigger | When it fires |
|---|---|
call.started | Our Notetaker joins the meeting and recording begins |
call.ended | Recording finishes |
call.notetaker_joined | Notetaker successfully gets into the meeting |
call.notetaker_media_ready | The recording and transcript finish processing |
Engagement
| Trigger | When it fires |
|---|---|
call.confirmed | The guest accepts the calendar invite |
call.declined | The guest declines the calendar invite |
call.attended | The call gets marked as attended after the meeting |
Outcomes
| Trigger | When it fires |
|---|---|
call.closed | You record an outcome of "Won" |
call.lost | You record an outcome of "Lost" |
call.no_show | The lead didn't show up |
call.cash_collected | Cash collected gets recorded on a deal |
call.ai_review_complete | The AI analysis finishes for a call |
call.follow_up | A follow-up gets generated or sent for a call |
Lead events
| Trigger | When it fires |
|---|---|
lead.started | Someone starts the booking flow |
lead.interested | Someone provides contact info partway through |
lead.captured | A new lead is created |
lead.qualified | A lead passes your qualification criteria |
lead.disqualified | A lead is marked as not a fit |
lead.status_changed | A lead's pipeline status changes |
What data comes through
Every trigger ships with the full lead and call info filled in — names, emails, UTM tags, custom question answers, the works. Field names match what you see in the app.
The easiest way to see exactly what's available on a given trigger is to use Zapier's Test trigger step:
- Set up your trigger.
- Click Test trigger.
- Zapier shows you a real recent event from your Aura account.
- The fields appear in Zapier's mapping UI on the next step.
What data is available depends on the trigger. For example, cash_collected is populated on call.closed and call.cash_collected events, but not on call.booked.
Custom fields
If your booking link has custom questions, the answers come through too — they appear as custom_field_<name> on the payload. The names match the question slugs you set up.
To see the available custom fields for your team, run a test trigger after at least one real booking has filled in those questions.
Building useful Zaps
Filter at the Zap level
If you only want some events through (like "only when the booking link is this one" or "only when utm_source = google"), use Zapier's Filter step. Aura fires the trigger for every matching event of the chosen type and lets Zapier decide which to act on — simpler and more predictable than us trying to do filtering on our side.
Popular patterns
| What you want | Trigger | Action |
|---|---|---|
| Slack notification when someone books | call.booked | Slack: Send Channel Message |
| Update your CRM when a deal closes | call.closed | Salesforce/HubSpot: Update Opportunity |
| Add qualified leads to an email sequence | lead.qualified | Customer.io / HubSpot: Add to Sequence |
| Create a coaching task when AI review is ready | call.ai_review_complete | Asana / Notion: Create Task |
| Send a re-engagement email after a no-show | call.no_show | Resend / Customer.io: Send Email |
| Log every booking to a spreadsheet | call.booked | Google Sheets: Add Row |
Limits and behavior
- We send each event once per Zap. If we retry internally, we deduplicate — your Zap won't fire twice for the same event.
- Zapier handles retries on its end if your action step fails. Aura doesn't back off when Zapier returns an error — you can see what happened in Zapier's Task History.
- Order isn't guaranteed across different triggers. Within a single trigger they fire in the order things happened, but if you have separate Zaps watching different triggers, they might land out of order. If order matters, put both steps in the same Zap.
- Standard Aura rate limits apply. If you're throttled, events queue up and resume.
Troubleshooting
"No data is coming through."
- Make sure the API key in Zapier matches an active key in Aura.
- Generate a test event (e.g., book a meeting through one of your links) and re-run the test trigger.
"My custom fields aren't showing up."
- Custom field slugs only appear after at least one real response has filled them in. Submit a test booking through the relevant booking link.
"My Zap doesn't fire."
- Check Zapier's Zap History to see if delivery attempts are happening. If nothing's appearing, the trigger type might not match what you expect — try a different trigger.
"The data mapping looks wrong."
- Re-run Test trigger after a recent real event. Zapier refreshes its sample data.
What's next
- API Keys — where Zapier auth comes from
- Partner API Webhooks — the direct-integration option if you're building something custom
- Pipeline — see what lead status changes fire which events