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.

​
Registration questions

Answers to an event’s registration form can fill contact, company, and campaign member fields. Each question on your Luma forms becomes a registration question in Conversion, and you choose which fields its answers fill.

​
Where questions come from

  • Luma’s built-in questions: Company, Job Title, Phone Number, LinkedIn, X (Twitter), GitHub, Instagram, Telegram, and YouTube.
  • Your own questions: added when you connect a field event to a Luma event, when the event changes, and when registrants answer them.
A question asked with the same wording on several events is one question in Conversion, so one mapping covers them all. Rewording a question on Luma creates a new, unmapped question. Three built-in questions come mapped: A default is skipped if another Luma question already fills that field.

​
Map a question to a field

Prerequisites: You are a workspace Administrator, and Luma is connected.
  1. Open workspace Settings and go to the Integrations tab.
  2. On the Luma card, open the ⋮ menu and click Manage fields.
  3. Find the question. Search by its wording if the list is long.
  4. Open the question’s ⋮ menu and click Edit fields.
  5. Click + next to Fields.
  6. Choose a Field.
  7. Choose how Existing values are handled: Fill empty values or Replace values.
  8. Click Save.
To change a mapping, open Edit fields for the question and pick a different field, or change Existing values, on its row. Changes save right away. To remove a mapping, click × on its row, then Confirm and remove.

​
How answers are written

  • A question can fill several fields, but each field takes answers from one Luma question.
  • You can map to contact fields, company fields (through the contact’s company), and campaign member fields. The contact’s email, relationship fields, and fields Conversion manages itself can’t be mapped.
  • New contact and company mappings use Fill empty values, so a registration never replaces a value someone already set. Campaign member mappings use Replace values, so the member always shows the latest answer. A blank answer never clears a value.
  • Unanswered questions are skipped. Checkbox and terms questions are recorded as true or false.
  • A mapping applies to answers Conversion receives after you save it.

​
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. Changing the event’s title on Luma updates the field event’s Title but not its name in Conversion. If the event is cancelled on Luma, Conversion archives the field event; its members are kept.

​
Troubleshooting