Set up a Zapier Integration

Use our Zapier integration to sync your event data with our tools you use: AirTable, Google Sheets, Mailchimp, and more

Our Zapier Integration allows you to trigger Zaps when different events happen on your Luma calendar or events. With 6 powerful triggers, you can automate workflows for event management, guest tracking, and ticket sales.

The Zapier Integration is only available for Luma Plus subscribers. Find out more about Luma Plus here.

Available Triggers

You can create Zaps that trigger when any of the following actions occur:

Calendar & Audience

Calendar Person Subscribed - Triggered when someone subscribes to your calendar.

Events

Event Created - Triggered when a new event is created on your calendar.
Event Updated - Triggered when event details are modified (title, date, location, etc.). Does not trigger for guest registrations.

Guests & Registrations

Guest Registered - Triggered when someone registers for an event for the first time. Perfect for welcome emails and initial confirmations.
Guest Updated - Triggered when any guest information changes, including check-in status, approval status, or profile updates.

Tickets

Ticket Registered - Triggered for each individual ticket purchase. If a guest buys 3 tickets, this triggers 3 times, allowing you to track individual ticket sales and create unique experiences per ticket.

Setting Up Zapier

Step 1 — Get Your API Key

Your API key will be specific to a calendar that you are creating events on. To find the API key:

Visit the Calendars Home and choose the calendar you are interested in
Go to Settings → Options
Find the API Keys section

Step 2 — Install Zapier App

Find the Zapier App here: https://zapier.com/apps/luma/integrations

Step 3 — Create Your Zap

Choose Luma as your trigger app
Select the trigger event that matches your workflow needs
Connect your Luma account using your API key
Configure any filters or settings for your trigger
Test the trigger to ensure it's working correctly
Set up your action steps in other apps

Debugging Your Zapier Integration

If your Zaps aren't triggering as expected, you can use our debugging tool to see what triggers have been sent to Zapier:

Go to your calendar's Settings → Options
In the API Keys section, click the "..." (three dots) button
Select "Debug Zapier"
This will show you a flow of different Zapier triggers that have fired for your calendar

What to check:

If the trigger is missing from the debug view, it won't appear in Zapier. This could mean:
- The action hasn't occurred yet (e.g., no one has registered for your event)
- There's an issue with the trigger setup
If the trigger appears in the debug view, Zapier should pick it up if configured correctly. Check your Zap configuration in Zapier if it's not working.

Note: The debug view shows "triggers" (actions that fire in your Luma calendar), not to be confused with Luma events themselves.

Changelog

Version 5.0.1 - Released September 30, 2025

Bug fix release that resolves an issue with the "Ticket Registered" trigger:

Fixed an error that could occur when testing the trigger in Zapier

Version 5.0.0 - Released August 28, 2025

This major update brings real-time webhook-based triggers to the Luma Zapier integration:

What's New:

Real-time webhooks - Triggers now fire instantly when events occur in Luma, replacing the previous polling-based system
Renamed triggers for clarity - "Calendar Member Updated" is now "Calendar Person Subscribed" to better reflect when it fires
Split guest triggers - Separated "Guest Registered" (new registrations) from "Guest Updated" (changes to existing guests) for more precise workflow control
Added Ticket Registered trigger - Track individual ticket purchases with a trigger that fires for each ticket, enabling per-ticket workflows and accurate sales tracking

Benefits of the Update:

Instant notifications - Your Zaps trigger immediately when actions happen, no more waiting for the next polling interval
Reduced API load - Webhooks eliminate constant polling, making the integration more efficient and reliable
More precise automations - Differentiate between new registrations and updates to existing guests
Better ticket tracking - Count exact ticket sales and create unique experiences per ticket (e.g., send 3 unique QR codes if someone buys 3 tickets)
Improved reliability - Direct webhook delivery ensures no missed events between polling intervals