Luma Zapier integrationAutomate Luma with Zapier.
The Luma Zapier integration gives you 7 triggers and 1 action, with no search step. All seven triggers are instant, so guests, tickets and events reach your other tools as soon as Luma reports them. Below: what each one does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Luma Zapier integration actually does
The integration links your Luma account to Zapier, so that something happening around your events sets off a step in another app without anyone copying data by hand. Luma can report new events, changed events, calendar activity, registrations and tickets, and it can add a person to one of your calendars.
Three results you can build with it. First, a guest list that fills itself: Guest Registered sends each new registration to your spreadsheet tool, one row per guest. Second, a count of every ticket sold: Ticket Registered fires once per ticket, so a guest who takes three tickets gives you three entries rather than one. Third, contacts from elsewhere pulled into a Luma calendar: Create Calendar Person adds someone by email to a calendar, with optional tags, and creates those tags if they are missing.
What Zapier does not do for Luma: it offers no search step, so a Zap cannot look up an existing guest or event before acting. The only action adds a person to a calendar; nothing creates, edits or cancels an event, and nothing registers a guest. Every change on the event side has to happen in Luma itself, by hand.
If you are weighing up tools, read the Make vs Zapier comparison before you build.
Zapier vocabulary in one minute
Seven words come back all over this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something in an app for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan is a count of those.
- Instant vs polling
- An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap go on only when the incoming data meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app so the next steps can use it. Luma has none on Zapier.
What a Luma Zap really costs
Luma is not a premium app, so it runs on the free plan. Triggers never cost a task, and since all seven Luma triggers are instant, they also fire straight away on every plan, free included.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Luma triggers7 of 7 instant, no waiting
Only a successful action is billed. If your Zap adds a row each time a guest registers, every row is one task; a step that fails costs nothing. Watch the trigger you choose: Ticket Registered fires once per ticket, so the same guest can cost several tasks. The free plan stops at two steps, one trigger and one action, and a filter makes the Zap multi-step, which needs a paid plan. The interval grid below is Zapier's general one: it does not apply to the instant triggers of Luma.
Connect Luma to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Luma account linked to Zapier once, then reused by every step that needs it.
- 02
Find Luma in the list
Type Luma in the search box of the dialog, select it from the results, then click Add connection. A new browser tab opens on the Luma side to finish the link.
- 03
Sign in and allow access
Log in to Luma in that tab and grant Zapier access to the account. You need a Luma account, plus access to any calendar or event you do not own and want the Zap to touch.
Your first Zap: a guest list that fills itself
GoalEach time someone registers for one of your Luma events and passes your condition, add a row to your spreadsheet so the guest list is always up to date.
- 01
Create the Zap
Start a new Zap, pick Luma as the app that starts it and
Guest Registeredas the trigger event, then choose the connection you added earlier. - 02
Test the trigger
Run the test. Zapier brings back the three most recent registrations of the connected account, so you map the next steps on a real guest.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, and the value to compare with. Use a text rule on text.
- 04
Add the spreadsheet action
Add your spreadsheet tool as the action, choose the step that creates a row, and map the guest details from Luma into the columns you want.
- 05
Test, then publish
Test the action and check the row. Then click Publish. With a filter this is a multi-step Zap, so it needs a paid plan; each row created costs one task.
The 7 Luma triggers
7 events start a Zap when something happens in Luma, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
Calendar Event Added
Instant triggerIn Zapier“Triggers when an event is added to a calendar”
Starts your Zap when an event lands on one of your Luma calendars. It watches the calendar rather than the event itself, which suits anyone who runs several calendars and wants each new entry to show up elsewhere.
Event Created is the separate trigger for that.Calendar Person Subscribed
Instant triggerIn Zapier“Triggers when someone subscribes a calendar”
Fires as soon as someone subscribes to a Luma calendar. This is the moment a person shows interest in a whole series of events rather than a single date, which makes it a useful signal for your contact list.
Event Created
Instant triggerIn Zapier“Triggers when a new event is created”
Kicks off a Zap the moment a new event is created in Luma. You get the event details while they are fresh, which is the right time to prepare everything that has to exist around it in other tools.
Event Updated.Event Updated
Instant triggerIn Zapier“Triggers when an event is updated”
Runs your Zap whenever an existing Luma event is changed. It is the trigger that keeps copies of an event in other tools in step with the original.
Guest Registered
Instant triggerIn Zapier“Triggers when a new guest registers for an event (fires once even if guest has multiple tickets)”
Fires when a new guest registers for an event, and only once per guest, even if that person takes several tickets. That makes it the trigger to use when you count people rather than seats.
Ticket Registered for that.Guest Updated
Instant triggerIn Zapier“Triggers when a guest's approval status changes, when they're checked in, or when they update their registration”
Reacts to three kinds of change on a guest: the approval status moves, the guest is checked in, or the guest edits their registration. One trigger therefore covers the approval stage, the door and the corrections.
Ticket Registered
Instant triggerIn Zapier“Triggers for each individual ticket when a guest registers (fires multiple times if guest buys multiple tickets)”
Fires for each individual ticket when a guest registers, so a guest who buys several tickets starts the Zap several times. It is the trigger to choose when seats, not people, are what you count.
The Luma action
Luma gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Calendar Person
ActionIn Zapier“Create a new person in a Luma calendar with optional tags. Creates tags if they don't exist.”
Adds a new person to one of your Luma calendars from data another app holds, with optional tags. If a tag you name does not exist yet, Luma creates it on the way, so you can sort people without preparing the tags first.
When a Luma Zap breaks
Zapier attaches no help article to Luma, and no limit specific to the app is documented. What breaks is what breaks on any Zap.
Four cases come back again and again, and none of them is visible while you build the Zap. They are worth knowing before you publish. When one of them hits, the Zapier troubleshooting page is the place to start.
Past registrations are never picked up
A Zap only reacts to what happens after you switch it on. Guests who registered before stay out of the Zap, and moving that backlog is a separate job.The Zap that feeds itself
A Zap that writes into the very place its own trigger watches, like adding people to the calendar it listens to, sets itself off again and again and burns tasks.A sudden flood of items
When a trigger suddenly sends a huge batch, after a bulk import for example, Zapier's flood protection can hold those items back instead of running them all.One guest, several tickets
Ticket Registered fires once per ticket, Guest Registered once per guest. Picking the wrong one gives you duplicate rows or a guest count that looks too low.
Need help automating Luma with Zapier?
A person reads every message.
