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, and perform actions to update your Luma calendar. With 7 powerful triggers and 1 action, you can automate workflows for event management, guest tracking, ticket sales, and audience management.

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 Event Added - Triggered when any event appears on your calendar, including events managed by the calendar, events syndicated from other calendars, and external events you've added. This gives you a complete view of everything on your calendar.
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 a guest registers and whenever guest information changes (check-in status, approval status, profile updates). Note: This fires for both new registrations and updates to existing guests.

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.

Available Actions

You can create Zaps that perform the following actions in Luma:

Audience Management

Add Person to Calendar - Add a person to your calendar community with optional tags. Perfect for syncing newsletter subscribers (e.g., from Beehiiv), CRM contacts, or leads from other platforms directly into your Luma calendar. Tags will be automatically created if they don't already exist, making it easy to segment your audience without manual tag setup.

Example Use Cases:

Sync Beehiiv newsletter subscribers to your Luma calendar with a "Newsletter Subscriber" tag
Add new CRM contacts from HubSpot or Salesforce to your calendar community
Tag leads from different sources (e.g., "LinkedIn", "Conference Attendee") for targeted event invitations
Automatically add form respondents from Typeform or Google Forms to your calendar

Setting Up Zapier

Step 1 — Create Your Zap

Go to the Luma Zapier App
Choose Luma as your trigger app or action app
Select the trigger event or action that matches your workflow needs

Step 2 — Connect Your Luma Account

When prompted to connect your Luma account:

Click "Sign in to Luma"
You'll be redirected to Luma to authorize the connection
Select the calendar you want to connect to Zapier
Click "Authorize" to grant Zapier access to your calendar
You'll be redirected back to Zapier with your account connected

Step 3 — Configure Your Zap

Configure any filters or settings for your trigger or action
Test the trigger/action to ensure it's working correctly
Set up your action steps in other apps
Turn on your Zap

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 6.0.0 - Released November 11, 2025

Simplified account connection:

Easier setup - Click "Sign in to Luma" when setting up your Zap and authorize access to your calendar. No need to copy and paste API keys.

Note: Existing Zaps will need to be reconnected. Edit your Zaps, disconnect your Luma account, and reconnect using the new flow.

Version 5.2.0 - Released October 24, 2025

Added the first Zapier action for Luma, enabling you to add people to your calendar from other apps:

Add Person to Calendar action - Automatically add subscribers, leads, or contacts to your Luma calendar from other apps like Beehiiv, HubSpot, Typeform, and more. Tags are created automatically if they don't exist, making audience segmentation effortless.
Enhanced Calendar Event Added trigger - Now includes calendar information (name, description, social links) and event hosts, giving you richer context when building workflows that respond to events being added to your calendar.
Formatted date fields - Calendar Event Added trigger now includes formatted date fields (e.g., "Mar 15, 2025, 11:00 AM PDT") for easier use in Slack messages and other notifications.

Version 5.1.0 - Released October 23, 2025

Added a new trigger to track events added to your calendar:

Calendar Event Added trigger - Fires when any event is added to a calendar, including events managed by the calendar, events syndicated from other calendars, and external events. This gives you complete visibility into everything on your calendar.

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