# Luma Event Scraper | Organizer Leads + Socials (`zrk1212/luma-organizer-leads`) Actor

Scrape Luma (lu.ma) events by city, category, calendar or host, and get one lead row per organizer: website, socials, followers, events hosted, average guests, paid-ticket share.

- **URL**: https://apify.com/zrk1212/luma-organizer-leads.md
- **Developed by:** [zachary klein](https://apify.com/zrk1212) (community)
- **Categories:** Lead generation, Social media, Other
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 organizer leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Luma Event Scraper: Organizer Leads, Socials, Event Stats

Find the people and companies who run events on Luma (lu.ma) in any city or category. Get one clean lead row per organizer with their website, socials, follower count, how often they host, how big their events are, and whether they sell tickets.

### What does it do?

- **Organizer leads (default):** one de-duplicated row per Luma calendar or host, with website, LinkedIn, Instagram, X, TikTok, YouTube, followers, events hosted (all time, last 90 days, upcoming), average and max guests, paid-ticket share, price range, cities, categories and Luma Plus status.
- **Full city coverage:** searches every public event near a city, not only Luma's small curated feed. In New York that is about **1,300 events instead of 72**.
- **Category filters that work:** tech, ai, arts, fitness, wellness, climate, food, books, games, running, family, crypto, combined with any city.
- **Events mode:** one row per event with date, venue, coordinates, guest count, ticket prices, sold-out status and organizer.
- **Privacy by design:** no attendee data, no guest lists, and hosts who opted out of robots on Luma are never returned as organizer rows.

### Who is it for?

- **Event sponsors and brands** looking for active communities in a city to sponsor.
- **Venues and coworking spaces** looking for hosts who need a room every month.
- **Event-tech and community SaaS sales teams.** Target organizers on the free Luma plan who host a lot, or organizers already paying for Luma Plus.
- **VCs and DevRel teams** mapping the AI and tech community scene in a city.
- **Agencies** prospecting organizers who sell tickets.

### What data do you get?

#### Organizers mode (one row per organizer)

| Field | Example |
|---|---|
| `name` | Tech Weekend by Founders Village |
| `organizerType` | `calendar` (an organization or community) or `host` (a person's profile) |
| `lumaUrl` | https://luma.com/tech-weekend |
| `website` | https://techweekend.org |
| `linkedinUrl`, `instagramUrl`, `xUrl`, `tiktokUrl`, `youtubeUrl` | https://www.linkedin.com/company/foundersvillage |
| `followerCount` | 132 |
| `hostedEventCount` | 58 (all public events, past and future) |
| `eventsLast90Days` | 6 |
| `upcomingEventCount` | 15 |
| `firstEventAt`, `lastEventAt`, `nextEventAt` | 2024-05-03T17:00:00.000Z |
| `avgGuestCount`, `maxGuestCount` | 84, 210 |
| `paidEventShare` | 1 (share of events found that sell tickets, 0 to 1) |
| `minTicketPrice`, `maxTicketPrice`, `currency` | 25, 1999, usd |
| `lumaPlan` | `plus` (paid Luma plan, a buying-power signal) or `free` |
| `cities`, `categories` | \["San Francisco"], \["tech"] |
| `homeLocation` | San Francisco, California, United States |
| `usesMetaPixel`, `usesGoogleAnalytics` | true (marketing maturity signal; the IDs are never returned) |
| `eventsFoundInRun` | 3 |
| `sampleEventUrls` | up to 5 event links |

#### Events mode (one row per event)

| Field | Example |
|---|---|
| `name`, `url` | Startup Pitch & Networking in NYC Manhattan, https://luma.com/lxpcykxv |
| `startAt`, `endAt`, `timezone` | 2026-11-18T23:00:00.000Z, America/New_York |
| `venueAddress`, `city`, `region`, `country` | 77 E 7th St, New York, NY 10003, USA |
| `latitude`, `longitude`, `addressIsApproximate` | 40.7274, -73.9863, false |
| `guestCount` | 71 |
| `isFree`, `isSoldOut`, `requiresApproval`, `spotsRemaining` | false, false, true, 46 |
| `minTicketPrice`, `maxTicketPrice`, `currency` | 29, 500, usd |
| `organizerName`, `organizerUrl`, `organizerType` | Startup Valley, https://luma.com/StartupValley |
| `hosts` | names and Luma profile links of the listed hosts |
| `category`, `discoveredVia` | tech, city:nyc |

**Notes on the numbers**

- Guest counts on upcoming events are RSVPs so far, not final attendance.
- When an organizer hides the guest list, Luma does not share the count, so `guestCount` is `null` (not 0) and those events are left out of the averages.
- When an organizer shows the address to guests only, `venueAddress` is `null` and the coordinates are Luma's approximate public location (`addressIsApproximate: true`).

### How much does it cost?

Pay only for the rows you get. Error rows are free.

| Result | Price per 1,000 | 100 | 1,000 | 10,000 |
|---|---|---|---|---|
| Organizer lead row | $6.00 | $0.60 | $6 | $60 |
| Event row | $1.00 | $0.10 | $1 | $10 |

The Apify free plan's monthly credit is enough to try it on a few hundred organizers.

### How to use it

1. Pick **Organizers** (lead rows) or **Events**.
2. Add one or more **cities** (for example `nyc`, `London`, `San Francisco`) or coordinates like `40.7128,-74.006`.
3. Optionally add **categories** like `ai` or `tech`.
4. Optionally add specific **calendars** (`https://luma.com/langchain`) or **hosts** (`https://luma.com/user/...`).
5. Click **Start** and download the results as CSV, Excel or JSON.

```json
{
  "mode": "organizers",
  "cities": ["nyc", "london"],
  "categories": ["ai"],
  "maxEvents": 500,
  "maxOrganizers": 100,
  "minFollowers": 200
}
```

**Full vs featured coverage.** `discoveryScope: "full"` (the default) searches all events within about 70 km of the city center (for example 1,322 events in New York on 2026-11-17). `featured` only reads Luma's curated city page (72 events in New York). Use `maxDistanceKm` to stay closer to the center.

**Which organizers come first?** The most active ones: organizers are ranked by how many of their events were found in your search, then enriched with their full Luma profile.

#### Example output (organizer)

```json
{
  "id": "cal-6TRJNtGExd4uLaW",
  "organizerType": "calendar",
  "name": "Tech Weekend by Founders Village",
  "lumaUrl": "https://luma.com/tech-weekend",
  "website": "https://techweekend.org",
  "instagramUrl": "https://instagram.com/founders.village",
  "xUrl": "https://x.com/foundersvillge",
  "linkedinUrl": "https://www.linkedin.com/company/foundersvillage",
  "youtubeUrl": "https://www.youtube.com/@foundersvillage",
  "lumaPlan": "plus",
  "followerCount": 132,
  "hostedEventCount": 58,
  "upcomingEventCount": 15,
  "pastEventCount": 46,
  "eventsLast90Days": 6,
  "nextEventAt": "2026-11-19T17:00:00.000Z",
  "paidEventShare": 1,
  "minTicketPrice": 25,
  "maxTicketPrice": 1999,
  "currency": "usd",
  "cities": ["Menlo Park"],
  "categories": ["tech"],
  "homeLocation": "San Francisco, California, United States",
  "eventsFoundInRun": 3
}
```

#### Example output (event)

```json
{
  "id": "evt-jAB5jfvYuJT0jMi",
  "url": "https://luma.com/lxpcykxv",
  "name": "Startup Pitch & Networking in NYC Manhattan",
  "startAt": "2026-11-18T23:00:00.000Z",
  "city": "New York",
  "venueAddress": "Whiskey Cellar NYC, in the cellar, 77 E 7th St, New York, NY 10003, USA",
  "guestCount": 71,
  "isFree": false,
  "minTicketPrice": 29,
  "maxTicketPrice": 500,
  "currency": "usd",
  "organizerName": "Startup Valley",
  "organizerUrl": "https://luma.com/StartupValley",
  "category": "tech"
}
```

### Use it via API, MCP, n8n, Make or Zapier

```bash
curl -X POST "https://api.apify.com/v2/acts/Zrk1212~luma-organizer-leads/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"organizers","cities":["nyc"],"categories":["ai"],"maxOrganizers":50}'
```

AI agents can call it through the Apify MCP server, and it works with the Apify integrations for n8n, Make and Zapier.

### Supported cities

Any coordinates work. These 87 Luma city names and slugs are also recognized:

Washington DC (`dc`), Philadelphia, Pittsburgh, New York (`nyc`), Raleigh, Toronto, Waterloo, Detroit, Cincinnati, Boston, Montréal, Atlanta, Chicago, Minneapolis, Miami, Dallas, Houston, Austin, Denver, Salt Lake City, Mexico City, Calgary, Phoenix, Edmonton, Las Vegas, San Diego (`sd`), Los Angeles (`la`), Medellín, Seattle, Portland, Vancouver, Sacramento, Bogotá, San Francisco (`sf`), Dublin, Lisbon, London, Madrid, Paris, Amsterdam, Brussels, Oslo, Hamburg, Barcelona, Copenhagen, Frankfurt, Geneva, Lausanne, Stockholm, Zurich, Berlin, Milan, Munich, Prague, Helsinki, Vienna, Warsaw, Rome, Budapest, São Paulo, Honolulu, Rio de Janeiro, Istanbul, Buenos Aires, Lagos, Tel Aviv, Tokyo, Seoul, Osaka, Dubai, New Delhi, Nairobi, Taipei, Cape Town, Mumbai, Hong Kong, Bengaluru, Manila, Auckland, Bangkok, Ho Chi Minh City, Brisbane, Kuala Lumpur, Singapore, Sydney, Jakarta, Melbourne.

### FAQ

**Do you scrape attendees or guest lists?**
No. Only organizer information that Luma shows publicly on event and profile pages. Attendee data is never collected or returned.

**Can I get emails or phone numbers?**
No. Luma does not show them. Use the website and social links to reach organizers.

**Is it legal?**
It reads public data with no login. Luma's terms restrict automated access to its service, so you are responsible for how you use the data, including GDPR, CAN-SPAM and other anti-spam and privacy rules. Hosts who opted out of robots on Luma are never returned as organizer rows (events mode still shows the host names printed on public event pages).

**Why are some host fields empty?**
People who host from a personal profile have no follower count or event history on Luma, so those fields are `null`. Set `includePersonalHosts` to false to get calendars only.

**Why did my run stop early?**
Luma rate limits fast traffic. The actor already paces itself (about 1.5 requests per second) and backs off when Luma pushes back. If Luma still blocks it, the run returns the results collected so far plus one `RATE_LIMITED` row instead of failing. Try again later or turn on a proxy.

**How fresh is the data?**
Live. Every run reads Luma at that moment.

**Something broke or a field is missing?**
Open an issue in the Issues tab. We respond within 24 hours.

# Changelog

This Actor's version history is a separate document: https://apify.com/zrk1212/luma-organizer-leads/changelog.md

# Actor input Schema

## `mode` (type: `string`):

Organizers: one lead row per organizer (a Luma calendar or a person who hosts), with website, socials, followers and event stats. Events: one row per event.

## `cities` (type: `array`):

Luma city names or slugs, for example nyc, New York, london, San Francisco, berlin. Or coordinates like 40.7128,-74.006 for any place on earth. 87 Luma cities are recognized (see the README).

## `categories` (type: `array`):

Luma categories: tech, ai, arts, fitness, wellness, climate, food, books, games, running, family, crypto. Leave empty for all events. Categories need at least one city.

## `calendars` (type: `array`):

Specific Luma calendars as URLs, slugs or IDs, for example https://luma.com/langchain, langchain or cal-... Returns that organizer (and its upcoming events in Events mode).

## `hosts` (type: `array`):

Luma user profile URLs or usernames, for example https://luma.com/user/hellosteady. Only public profile fields are returned. People who opted out of robots on Luma are skipped.

## `discoveryScope` (type: `string`):

Full: every public event near the city (about 70 km radius), for example about 1,300 events in New York. Featured: only Luma's small curated city feed (about 70 events in New York). Category searches always use Full.

## `maxDistanceKm` (type: `integer`):

Optional. Drop events farther than this from the city center. 0 means no limit.

## `maxEvents` (type: `integer`):

How many events to scan for each city and category combination. Organizers are built from these events.

## `maxOrganizers` (type: `integer`):

Maximum organizer rows in total. The most active organizers (most events found) come first.

## `onlyPaidEvents` (type: `boolean`):

Events mode: keep only events that sell tickets. Organizers mode: keep only organizers with at least one paid event found.

## `minFollowers` (type: `integer`):

Skip calendars with fewer followers. Personal hosts have no follower count on Luma, so any value above 0 also skips them.

## `includePersonalHosts` (type: `boolean`):

Include people who host from a personal Luma profile instead of a calendar. Only their public profile fields are returned.

## `dateFrom` (type: `string`):

Optional. Keep events that start on or after this date (UTC).

## `dateTo` (type: `string`):

Optional. Keep events that start on or before this date (UTC).

## `proxyConfiguration` (type: `object`):

Not needed normally. Turn it on only if you see rate limit errors.

## Actor input object example

```json
{
  "mode": "organizers",
  "cities": [
    "sf"
  ],
  "categories": [
    "tech"
  ],
  "discoveryScope": "full",
  "maxDistanceKm": 0,
  "maxEvents": 100,
  "maxOrganizers": 25,
  "onlyPaidEvents": false,
  "minFollowers": 0,
  "includePersonalHosts": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `organizers` (type: `string`):

No description

## `events` (type: `string`):

No description

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "organizers",
    "cities": [
        "sf"
    ],
    "categories": [
        "tech"
    ],
    "maxEvents": 100,
    "maxOrganizers": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("zrk1212/luma-organizer-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "organizers",
    "cities": ["sf"],
    "categories": ["tech"],
    "maxEvents": 100,
    "maxOrganizers": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("zrk1212/luma-organizer-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "organizers",
  "cities": [
    "sf"
  ],
  "categories": [
    "tech"
  ],
  "maxEvents": 100,
  "maxOrganizers": 25
}' |
apify call zrk1212/luma-organizer-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zrk1212/luma-organizer-leads"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/0KrZihjLlP0Ti1eFQ/builds/MDUtN8tpzd5UD5gKF/openapi.json
