Luma Attendees Scraper

Extract the full attendee list from any lu.ma event — names, headlines, LinkedIn profiles, Twitter handles, and websites — ready for outreach, networking research, or enrichment pipelines.

Whether you're preparing for a conference, building a prospect list, or identifying who to meet at a meetup, this actor gives you structured, clean data for every registered guest.

What you get

• One dataset row per attendee with contact and profile data
• Event metadata (name, date, location, topics, organizers) saved separately in the key-value store — no duplication across rows
• LinkedIn URLs as full, ready-to-use links (https://www.linkedin.com/in/...)
• Organizers flagged with isOrganizer: true so you can filter or prioritize them
• Works across multiple events in a single run

Use cases

• Event networking — know who's attending before you walk in the door
• Sales prospecting — find decision-makers attending industry events
• Recruiting — identify talent at tech meetups and conferences
• Market research — understand who attends events in your space
• Enrichment pipelines — feed LinkedIn URLs directly into LinkedIn Profile Enrichment

How it works

1. Opens the Luma event page using your session cookie
2. Extracts event metadata (name, date, location, topics, organizers)
3. Fetches the paginated attendee list via the Luma API (up to 5,000 guests)
4. Outputs one clean dataset row per attendee
5. Saves full event details to the key-value store under event-{eventId}

Input

Field	Type	Required	Description
eventUrls	string[]	Yes	One or more lu.ma event URLs, e.g. https://lu.ma/my-event
lumaCookie	string	Recommended	Session cookie from a logged-in lu.ma account. Required for the full guest list.
scrapeGuests	boolean	No (default: true)	Set to false to retrieve event metadata and organizers only, without the attendee list.

Getting your session cookie

The full guest list is only available to logged-in, registered attendees. To get your cookie:

1. Log into lu.ma in your browser
2. Open DevTools (F12) → Application → Cookies → https://lu.ma
3. Find the cookie named luma.auth-session-key and copy its value
4. Paste it into the lumaCookie field — it is stored as a secret and never logged

Tip: You must also be registered (RSVP'd) for the event. Without registration, only the ~10 public featured guests are returned. Registering is usually one click on the event page.

Output

Dataset — one row per attendee

Field	Type	Description
attendeeId	string	Luma internal user ID
name	string	Full name
headline	string | null	Job title or bio from their Luma profile
linkedinUrl	string | null	Full LinkedIn URL, e.g. https://www.linkedin.com/in/janesmith
twitterUrl	string | null	Full Twitter/X URL
website	string | null	Personal or company website
lumaUsername	string | null	Luma username slug
lumaProfileUrl	string | null	Link to their Luma profile
isOrganizer	boolean	true if this person is a host or organizer
eventId	string	Foreign key — links to the event record in the key-value store

Key-value store — event metadata

Full event details are stored once per event under the key event-{eventId}:

{
  "id": "evt-xyz789",
  "name": "AI Founders Meetup",
  "url": "https://lu.ma/ai-founders",
  "description": "Monthly gathering of AI founders in San Francisco.",
  "startAt": "2026-08-01T18:00:00Z",
  "location": "San Francisco, CA",
  "topics": ["AI", "Startups"],
  "organizers": [{ "id": "usr-host1", "name": "Alice Chen", "linkedinUrl": "https://www.linkedin.com/in/alicechen" }],
  "coverage": {
    "guestCount": 312,
    "fetchedFullList": true
  }
}

Example dataset row

{
  "attendeeId": "usr-abc123",
  "name": "Jane Smith",
  "headline": "AI Engineer at Acme Corp",
  "linkedinUrl": "https://www.linkedin.com/in/janesmith",
  "twitterUrl": "https://twitter.com/janesmith",
  "website": "https://janesmith.dev",
  "lumaUsername": "janesmith",
  "lumaProfileUrl": "https://lu.ma/user/janesmith",
  "isOrganizer": false,
  "eventId": "evt-xyz789"
}

Integrations

LinkedIn enrichment: pipe linkedinUrl from the dataset into LinkedIn Profile Enrichment to get job history, company size, and seniority level for every attendee.

AI ranking: combine this actor's output with an LLM to score and rank attendees by relevance to your goals — e.g. filtering for investors, engineers in a specific domain, or people at companies you want to partner with.

FAQ

Do I need a Luma account? Yes — a free account is sufficient. You need to be logged in to get your session cookie, and registered for the event to access the full guest list.

How many attendees can it fetch? Up to 5,000 per event. Most Luma events have well under 1,000 attendees.

Are LinkedIn profiles scraped from LinkedIn? No. LinkedIn handles come from what attendees have entered on their own Luma profiles. For full LinkedIn data (job history, company, etc.) use LinkedIn Profile Enrichment as a follow-up step.

What if the event is private or I'm not registered? The actor falls back to the ~10 publicly visible featured guests and flags coverage.fetchedFullList: false in the key-value store. Register for the event and re-run to get the full list.

Can I scrape multiple events at once? Yes — pass multiple URLs in eventUrls. Each event gets its own key-value store record; all attendees land in the same dataset with their eventId as a reference.