Ticketing integration
AgendaForge + Luma
Sell tickets on Luma's checkout while guests, orders, and check-ins sync live into your AgendaForge event CRM.
The AgendaForge Luma integration turns the two-tool setup most Luma conferences already run — Luma as the registration front door, something else for the program — into one wired stack. You connect one Luma calendar with its API key, bind your AgendaForge event to an event on that calendar, and every guest and order syncs in: a one-time backfill first, then live signed webhooks as people register, get approved, or are refunded. Each Luma guest becomes a real contact and event member in your CRM — with tags, notes, activity, segments, and email — sitting next to your speakers, sponsors, and sessions instead of in a separate guest list. The sync runs both ways where Luma's API allows it: you can approve, decline, or waitlist guests and send invites from inside AgendaForge, and ticket types you create or edit in AgendaForge push straight to Luma. Money, deliberately, stays on Luma: buyers pay on Luma's hosted checkout and funds settle to your own Stripe — AgendaForge never touches the payment.
Capabilities
What the Luma integration does.
- Syncs every Luma guest and order into AgendaForge — a full backfill on connect, then live updates via Luma's signed webhooks — so registrants become contacts and event members you can segment, tag, note, and email.
- Lets you manage guests from inside AgendaForge: approve, decline, waitlist, or set pending, and invite new guests by email — each action writes back to Luma, which stays the source of truth.
- Pushes ticket types both ways: create or edit a ticket type in AgendaForge (name, price, capacity, hidden, approval-required, sale window) and it's written to Luma; Luma-side types sync in on every re-sync.
- Mirrors check-ins: guests you check in on Luma show as checked in on AgendaForge's check-in screen after a re-sync (Luma's check-in API is read-only, so scanning happens on Luma).
- Keeps money entirely on Luma: buyers pay on Luma's hosted, Luma-branded checkout and funds settle to your own Stripe account. AgendaForge never processes the payment and takes no fee on Luma sales.
- Supports switching a single event between the Luma rail and AgendaForge's early-access native Stripe ticketing — past orders and tickets are kept as CRM history either way. The Stripe rail remains feature-gated pending end-to-end production validation with a launch partner.
Triggers
What fires, and what happens.
guest.registered
The new registration is fetched in full from Luma, minted as an order with its ticket line items, and the guest becomes a contact + event member in your CRM.
guest.updated
Approval-status changes (accepted, pending, declined) and refunds made on Luma re-derive the synced order and ticket state, so the CRM never drifts from Luma.
ticket.registered
Per-ticket line items — label, price, quantity, and the linked ticket type — sync onto the guest's order.
guest checked in on Luma
The checked-in timestamp mirrors into AgendaForge's check-in view on the next sync, giving you one attendance picture across the event.
guest approved / declined / invited in AgendaForge
The action is written back to Luma via its guest API — approve, decline, waitlist, set pending, or send an email invite — with Luma remaining the authoritative record.
ticket type created or edited in AgendaForge
The ticket type is pushed to Luma with full field parity: name, price, currency, free/paid/donation, capacity, hidden, approval requirement, and sale window.
Setup
Connect it in minutes.
-
Connect Luma with an API key
In your event's Registrations → Providers tab, paste the API key for the Luma calendar that owns the event (Settings → API). Requires an active Luma Plus subscription — AgendaForge validates the key, then stores it encrypted (AES-256-GCM). Luma keys are calendar-scoped, and AgendaForge currently connects one Luma calendar per organization.
-
Bind your Luma event
Pick the Luma event to link from the dropdown. AgendaForge runs a full guest backfill immediately and shows live tiles for attendees synced, accepted, pending, declined, and orders.
-
Manage guests from AgendaForge
Approve, decline, or waitlist synced guests, invite new ones by email, and re-sync on demand. Ticket types you edit in AgendaForge push to Luma. Checkout, standalone refund management, and check-in scanning stay on Luma; declining an accepted guest can optionally ask Luma to refund them.
Good to know
This integration requires two paid tiers to exist at all: your Luma calendar must be on Luma Plus (Luma gates its API and webhooks to Plus), and the AgendaForge event must be on the Pro plan. Luma API keys are scoped to one calendar, and AgendaForge currently connects one Luma calendar per organization. Money never flows through AgendaForge — checkout and standalone refund or cancellation management stay on Luma, although declining an accepted guest can ask Luma to refund them. Check-in is a read-only mirror because Luma's check-in API can't be written to. We also don't push sessions, speakers, or agenda content into Luma — the program layer lives in AgendaForge, and each event runs on one ticketing rail at a time.
Questions
Luma, answered.
Q.01 Do I need a paid Luma plan to use this integration?
Q.02 Does AgendaForge process payments for Luma events?
Q.03 What syncs into AgendaForge, and what writes back to Luma?
Q.04 Can I check guests in from AgendaForge for a Luma event?
Q.05 Can I switch between Luma and AgendaForge's native ticketing?
Q.06 Does AgendaForge push my agenda or speakers into Luma?
Integration reviewed July 2026. See the API reference for webhook and Zapier details.
More integrations
Run your event with Luma wired in.
Invite-only while we onboard early partners. Tell us about your event and we'll bring you in — white-glove, no training course required.