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.

Getting it set up

---

All 23 triggers

We've grouped them by what's happening in the customer's journey.

Booking lifecycle

Call lifecycle

Engagement

Outcomes

Lead events

How lead.interested and lead.qualified are decided

Aura checks each booking-page visit once, five minutes after the visitor first enters a name plus an email or phone. It sends at most one of these events for that visit:

• Someone who books within five minutes never triggers lead.qualified. To act on every lead who made it past your questions, trigger on both lead.qualified and call.booked.
• The check runs once per visit, not once per person. The same person on a new visit or another scheduler can trigger it again.
• qualified_at in the payload is when the check ran, not when the visitor answered.
• lead.qualified is not related to the "Qualified booking" event on a booking link's Tracking step. That one is a Meta ad event sent after a call outcome.

---

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:

1. Set up your trigger.
2. Click Test trigger.
3. Zapier shows you a real recent event from your Aura account.
4. 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 scheduler 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.

Consent

Payloads with the lead's details also say what the person agreed to on your booking form. Aura sends the phone number either way, so check consent before a Zap texts or emails anyone.

• consent lists each consent box and what the person chose. consent_summary gives the same choices as text.
• consent_by_type gives one answer for each kind of message: Booking texts (sms_booking), Marketing texts (sms_marketing), Marketing emails (email_marketing) and Data use (data_processing). Each answer is yes, no or not_asked.

To act only on people who agreed, add a Filter step that checks the answer's state is yes. For example, check the sms_marketing state before a Zap sends an offer by text. Treat not_asked like a no.

Answers by type need your consent boxes to have a type. See Privacy & consent. Every field is described in the payload reference. Zapier and the webhooks use the same fields.

---

Building useful Zaps

Filter at the Zap level

If you only want some events through (like "only when the scheduler 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

---

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 scheduler.

"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