---
title: "Set up a Zapier Integration"
subtitle: "Use our Zapier integration to sync your event data with our tools you use: AirTable, Google Sheets, Mailchimp, and more"
slug: "set-up-a-zapier-integration"
url: "https://help.luma.com/p/set-up-a-zapier-integration"
tags: ["Integrations"]
---

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](https://luma.com/pricing).

## Which events trigger Zaps?

Most Zapier triggers — like guest registration, event updates, and ticket purchases — only fire for events that your calendar **manages**. Your calendar manages an event if it was created on your calendar, transferred to it, or if your calendar was granted manage access to the event. If you simply add someone else’s event to your calendar via a link (without manage access), it appears on your calendar page but your triggers won’t fire for it.

The exception is **Calendar Event Added**, which fires whenever any event is added to your calendar, including linked events from other hosts.

If you’re co-hosting an event with another organizer and want triggers like guest registration to work on your Zaps, the event needs to be created on your calendar or transferred to it. Learn more about [how calendars manage events](/p/managing-events-with-calendars) and [calendar overview](/p/luma-calendar-overview).

## 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. This includes re-registrations after a guest cancels and registers again.
- **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**

1. Go to the [Luma Zapier App](https://zapier.com/apps/luma/integrations)
2. Choose Luma as your trigger app or action app
3. Select the trigger event or action that matches your workflow needs

**Step 2 — Connect Your Luma Account**

When prompted to connect your Luma account:

1. Click **”Sign in to Luma”**
2. You’ll be redirected to Luma to authorize the connection
3. Select the calendar you want to connect to Zapier
4. Click **”Authorize”** to grant Zapier access to your calendar
5. You’ll be redirected back to Zapier with your account connected

**Step 3 — Configure Your Zap**

1. Configure any filters or settings for your trigger or action
2. Test the trigger/action to ensure it’s working correctly
3. Set up your action steps in other apps
4. 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:

1. Go to your calendar’s **Settings → Developer**
2. In the **API Keys** section, click the **”...”** (three dots) button
3. Select **”Debug Zapier”**
4. 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.3** - _Released April 13, 2026_

No user-facing changes.

**Version 6.0.2** - _Released March 4, 2026_

Fix connection expiring and add logging.

**Version 6.0.1** - _Released March 3, 2026_

Fixed an issue where some users’ Luma connections in Zapier would expire and require re-authentication.

**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