Events
Read each event’s date in its own time zone, location, capacity, spots remaining, approval and waitlist settings.
Luma connector · Event reports
Bring Luma events, guests and attendance into your reports and AI assistants: capacity and spots left, each guest’s status, ticket and UTM source, and check-in rates per event.
Updated November 2026
| Event name | Going | Checked in |
|---|---|---|
| Sunrise 10K group run | 186 | 142 |
| Trail shoe fitting night | 64 | 51 |
| Marathon training Q&A | 240 | 118 |
One Luma calendar is the data source. Reports cover events that started in your report dates and every upcoming event.
Read each event’s date in its own time zone, location, capacity, spots remaining, approval and waitlist settings.
See each guest’s status, registration, invite and check-in times, ticket, company, job title and UTM source.
Compare guests, going, checked in, waitlist, declined and check-in rate per event.
Add up ticket amounts per paid event, in each ticket’s currency.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Events your Luma calendar manages that started in the report dates, plus every upcoming event, with dates, location, capacity and registration settings.
Every guest registered or invited to those events, with approval status, registration and check-in times, tickets, amount paid and where they came from.
One row per event with guests going, checked in, waitlisted, pending, invited and declined, the check-in rate and ticket sales.
50 report fields across 3 datasets.
Search the available fields. Hover or tap a field to see what it means.
No fields match. Try another search or choose All.
Use Datapipe’s MCP access as your Luma reporting tool. Ask about registrations, check-ins and sources.
Example
Which UTM sources brought the most guests who actually checked in last quarter?
Count last quarter’s guests by UTM source, then count those with a check-in time, and rank sources by checked-in guests and check-in rate.
A Luma API key for the calendar, from the calendar’s API keys page. Luma offers API keys with Luma Plus.
Read-only. Datapipe never changes events or guests. Up to 20,000 rows per report.
Create your free account, then choose Luma in Data sources.
Paste the API key for your Luma calendar.
Choose events, guests or attendance and a destination: a sheet, Data Studio, ChatGPT or Claude.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Events with capacity and settings, guests with status, ticket and UTM details, and attendance per event.
Each key covers one calendar. Add Luma again for each calendar.
No. It only reads events and guests.
Luma offers API keys with Luma Plus.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
One for each Luma account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Start free, add Luma and bring events and guests into the tools you already use.