Luma Attendee Profile Exporter

Export enriched attendee data from events you manage on Luma. The actor uses the official Luma API to turn guest registrations into a clean follow-up table with contact details, social profile links, company, job title, registration answers, and a practical follow-up segment.

Luma's native exports are useful when you only need names and emails. This actor is for event organizers, community teams, founder-network operators, and sponsors who need the extra profile context guests submitted in registration forms.

Requirements

You need:

• a Luma API key for a calendar or organization that can manage the event
• the Luma event ID
• permission to export and process the attendee data for that event

Luma currently lists API access as a paid-plan feature. If your Luma account cannot create or use API keys, this actor cannot access private attendee fields on your behalf. It does not scrape Luma pages, automate login, or bypass Luma account permissions.

Why Use It

Use this actor when you want to:

• prioritize post-event outreach by profile completeness
• find attendees with LinkedIn, X/Twitter, Instagram, GitHub, Telegram, or YouTube links
• identify founders, executives, community operators, marketers, and other high-value attendee segments
• preserve custom registration answers in a structured dataset
• append event attendee rows into a larger Apify workflow using datasetId or runId
• export several guest statuses in one run, such as approved attendees plus waitlist or pending approval guests

What You Get

Each attendee row can include:

• attendee name, email, guest status, registration time, invite time, and check-in time
• company and job title when collected by the event form
• social profile links when guests provided them
• long-text registration answers normalized into bioOrDescription
• all registration answers preserved in registrationAnswers
• ticket type names when available in the guest record
• followUpSegment, such as Founder or executive, Community or marketing, or Social follow-up
• profileCompletenessScore so richer profiles can be prioritized first

How To Use

1. Create or copy a Luma API key from an account with access to the target event.
2. Copy the Luma event ID.
3. Choose the guest statuses to export.
4. Run the actor and download the default dataset as JSON, CSV, Excel, or through the Apify API.

Input

{
  "lumaApiKey": "YOUR_LUMA_API_KEY",
  "eventId": "evt-abc123",
  "guestStatuses": ["approved", "waitlist"],
  "maxGuests": 500
}

Input Fields

• lumaApiKey - Your Luma API key. This is stored as a secret input in Apify.
• eventId - The Luma event ID to export.
• guestStatuses - One or more guest statuses to export. The default is approved.
• maxGuests - Maximum number of guests to export across the selected statuses.
• datasetId - Optional Apify dataset ID to append the same rows into another dataset.
• runId - Optional pipeline identifier copied into each output row.

If lumaApiKey or eventId is empty, the actor returns one setup_required row explaining what to add. This keeps Apify's automated checks stable without exposing a confusing demo-mode toggle.

Output Example

{
  "rowType": "attendee",
  "guestId": "gst-001",
  "userId": "usr-001",
  "guestName": "Maya Chen",
  "firstName": "Maya",
  "lastName": "Chen",
  "email": "maya@example.com",
  "approvalStatus": "approved",
  "registeredAt": "2026-06-20T16:15:00.000Z",
  "company": "Northstar Labs",
  "jobTitle": "Founder",
  "linkedinUrl": "https://www.linkedin.com/in/maya-chen-growth",
  "twitterUrl": null,
  "instagramUrl": null,
  "githubUrl": null,
  "bioOrDescription": "Building analytics tools for event-led communities.",
  "ticketTypes": ["Founder Pass"],
  "socialProfiles": {
    "linkedin": "https://www.linkedin.com/in/maya-chen-growth"
  },
  "registrationAnswers": {
    "Company": {
      "company": "Northstar Labs",
      "jobTitle": "Founder"
    },
    "LinkedIn": "maya-chen-growth",
    "What are you working on?": "Building analytics tools for event-led communities."
  },
  "followUpSegment": "Founder or executive",
  "profileCompletenessScore": 67
}

API Example

curl "https://api.apify.com/v2/acts/trovevault~luma-attendee-profile-exporter/runs?waitForFinish=120" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "lumaApiKey": "YOUR_LUMA_API_KEY",
    "eventId": "evt-abc123",
    "guestStatuses": ["approved"],
    "maxGuests": 500
  }'

After the run finishes, download rows from the default dataset URL in the run output.

Notes And Limits

• The actor only works for events your Luma API key can access.
• It requires Luma API access, which may require a paid Luma plan.
• It does not scrape public attendee pages, automate Luma login, or bypass Luma access controls.
• Social links, company, job title, and bios appear only when they are included in the event's Luma guest registration data.
• If a guest did not provide a social link or description, the corresponding output field is null.
• Selecting multiple statuses may make multiple Luma API list requests, but results are deduplicated by guest ID where possible.
• Luma's documented rate limits are 200 requests per minute for calendar API keys/OAuth tokens and 500 requests per minute for organization API keys.

Troubleshooting

I get a setup-required row. Add both lumaApiKey and eventId. The default example intentionally leaves them empty so scheduled platform checks can run without private credentials.

The run fails with a Luma API authorization error. Confirm the API key belongs to a Luma account that can manage the event and that the account has API access.

Social links or bios are missing. The actor can only export fields present in the Luma guest registration data returned by the API. Add social/profile questions to future event registration forms if you need richer rows.

I selected several statuses and got fewer rows than expected. maxGuests applies to the total export across all selected statuses.

FAQ

Does this work without Luma Plus or API access? No. The actor uses the official Luma API. A CSV-only workflow would not recover profile fields that Luma does not include in the export.

Can it export attendees from events I do not manage? No. Your API key must have access to the event.

Can I use this in automations? Yes. Use Apify schedules, webhooks, API calls, or downstream dataset processing. For repeat exports, keep maxGuests aligned with your expected event size.

Daily Test Strategy

The actor's prefilled input intentionally leaves private Luma credentials empty. That produces one setup_required row in seconds, proving the output schema, dataset view, and Apify run lifecycle without storing or requiring real attendee data. Buyer runs add their own Luma API key and event ID to export attendee rows.

Changelog

• 0.1 - Initial release with official Luma API export, multi-status filtering, social/profile normalization, setup-required daily-test path, and Apify dataset output.