Before you start
- A Luma account that owns or has access to at least one event.
- A TalkValue workspace with an active Pro plan or trial. See Plans and trial.
- Workspace Admin role. Only admins can connect integrations. See Members if you need access.
Connection model
- One Luma account per workspace. To switch accounts, disconnect the current one and connect the new one.
- Admin-only. Only workspace Admins can connect, reconnect, or disconnect integrations.
- Workspace-scoped. The connection belongs to the workspace, not to the Admin who connected it.
- Read access to your events: name, start and end time, timezone, location.
- Read access to your guests: every field you collect on the Luma registration form.
- Account email: shown on the integration card so you can confirm which account is connected.
Connect
Open Settings → Integrations
Sign in at app.trytalkvalue.com, open the side panel, and navigate to Settings → Integrations. You’ll see a card for each supported provider, including Luma.
Click Connect on the Luma card
Click the Connect button on the Luma card. TalkValue opens an authorization flow that hands off to Luma.
Authorize TalkValue in Luma
Sign in to Luma if prompted, then review the requested access and approve. Luma redirects you back to TalkValue automatically.
Confirm the connection
Back in Settings → Integrations, the Luma card now shows a green Connected badge with the Luma account email and the connection date. You’re ready to import.
What syncs
When you import a Luma event into Path, TalkValue brings in:- The event itself: name, start time, end time, timezone, and location.
- Every attendee: email, name, and the fields Luma collects during registration.
- A dedicated channel for the Luma source, so attribution charts can attribute the registrations correctly.
Status states
The Luma card on Settings → Integrations is in one of three states:- Not connected. The card shows a Connect button. Click it to start the authorization flow.
- Connected. A green Connected badge appears in the top right, with the Luma account email and connection date underneath. The card has an external link to Luma and a Disconnect button.
- Reconnect required. An amber Reconnect required badge replaces the green one. The card description reads: “Authentication expired or revoked. Connect a new Luma account above, then remove this entry.” This state appears when Luma invalidates the token, for example after a password change on Luma, or when the Luma account owner revokes TalkValue access from Luma’s settings.
Reconnect
When the card shows Reconnect required, TalkValue keeps the disconnected entry visible so you can finish the cleanup deliberately. Click Connect on the connectable Luma card above the disconnected one, run through the Luma authorization again, then click Remove on the disconnected entry once the new connection is in place. Events and guests you already imported stay in your workspace through the disconnect.Disconnect
On the connected Luma card, click Disconnect. A confirmation dialog opens with the message: “This will remove the connection to your Luma account. You can reconnect at any time, but you’ll need to re-import your events.” Confirm to flip the card to the not-connected state. Already-imported events stay in your workspace; new Luma events won’t appear until you reconnect.Troubleshooting
The Luma card shows “Reconnect required”
The authorization token expired or was revoked from the Luma side. Click Connect to reauthorize TalkValue, then remove the disconnected entry. Full pattern: Reconnect.An event I expected to see is missing from the import dialog
Check that the event is owned by (or shared with) the Luma account you connected. If you have multiple Luma accounts, disconnect and reconnect with the right one.Related
- Luma field mapping. Which Luma fields land in which TalkValue fields.
- Connect Eventbrite. Same flow for Eventbrite.
- Import a CSV. The manual import path.
- Import attendees into Badge. Using the same connection to populate a check-in event.
- Recovering from disconnect. What happens to a Badge event when its integration goes into the reconnect state.
- Attribution model. How the auto-created channel feeds into your attribution analytics.
