Skip to main content
Luma connects with an API key. Once connected, everything in Field Event Platform Sync applies; this page covers the connection and where Luma behaves differently.

​
Connect Luma

Prerequisites: You are a workspace Administrator, and you have an API key from Luma. Luma issues keys per calendar or, on higher tiers, per organization. Either works; see Luma’s own documentation for how to create one.
  1. Open workspace Settings and go to the Integrations tab.
  2. Find Luma and click Connect.
  3. Paste your API key and click Connect.
Conversion validates the key against Luma before saving it and works out whether it’s a calendar or organization key. Once connected, the card shows the calendar it covers, or the number of calendars for an organization key. Use Update connection to rotate the key, or Disconnect to remove the integration; connected field events keep their members but stop syncing. At connect time Conversion also registers a webhook with Luma, which is what makes registrations arrive in real time. Disconnecting removes it.
A calendar key only sees that calendar’s events. If an event is missing from the picker, check which calendar it belongs to.

​
Registration and attendance

Luma notifies Conversion as guests register, change status, or check in, so members update within moments. A full reconciliation also runs every six hours to catch anything a notification missed.

​
Event details

Luma fills in the title, times, registration link, format (in-person or virtual, based on the location type), approval requirement, venue and address, host as organizer, capacity, and spots remaining. Luma doesn’t report an event lifecycle status, so Conversion reads it off the clock. Changes to the event on Luma arrive in real time. If the event is cancelled on Luma, Conversion archives the field event; its members are kept.

​
Troubleshooting