# Luma Scraper — Events & Organizer Leads (lu.ma) (`scrapesage/luma-scraper`) Actor Scrape Luma (lu.ma / luma.com) events by city, keyword or URL. Rich event data: date, venue geo, price, capacity, spots left, categories and hosts, plus community calendars with social handles as organizer leads. Monitor mode pulls only new events. No login. Export JSON, CSV, Excel. - **URL**: https://apify.com/scrapesage/luma-scraper.md - **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community) - **Categories:** Lead generation, Social media, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $5.00 / 1,000 event scrapeds 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/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Luma Scraper — Events & Organizer Leads (lu.ma) Extract **complete Luma event data** — **exact date/time, venue geo, ticket price, capacity & spots remaining, categories, the full host list, and the community calendar** behind every event — plus turn each **community/organizer into a B2B lead** with its description, **Instagram / LinkedIn / TikTok handles** and a lead score. Works on both `lu.ma` and `luma.com`. No login, no cookies — fast JSON extraction straight from Luma's own internal API. ### Why this Luma scraper? Luma is where the **AI, startup, crypto and tech** scene runs its events — and most scrapers can't read it at all, or grab only the event title. This actor reads Luma's internal API directly and ships the richest dataset in the category: events **plus** the communities and hosts behind them. | Data | Typical scrapers | This actor | |---|---|---| | Event title, date/time, URL | partial | ✅ | | In-person vs online + **venue city/region/geo** | ❌ | ✅ | | Ticket **price**, free/paid, **sold-out & spots remaining** | ❌ | ✅ | | Full description + **event categories** | ❌ | ✅ | | **Hosts** with website & bio | ❌ | ✅ | | **Community calendar**: name, description, **IG/LinkedIn/TikTok** | ❌ | ✅ | | Organizer **lead score** | ❌ | ✅ | | Search by **city + keyword**, or scrape a community/event URL | partial | ✅ | | **Monitor mode** — only new events since last run | ❌ | ✅ | ### Use cases - **Lead generation** — Luma communities (calendars) are run by founders, DevRel teams, VCs and agencies. Capture each one with its social handles and lead score, then reach out. - **Event discovery & aggregation** — feed calendars, newsletters and apps with structured Luma data (date, venue, price, capacity) for any tech hub: San Francisco, New York, Austin, London, Singapore, and more. - **Sponsorship & partnership prospecting** — find active communities by city and topic (AI, crypto, design, startups), then pitch the organizer directly. - **Market & trend research** — track which topics and communities are drawing crowds across the startup ecosystem. - **Competitive intelligence** — monitor specific communities for every new event they launch. ### How to use 1. [Sign up for Apify](https://console.apify.com/sign-up) — the free plan is enough to try this actor. 2. Open the **Luma Scraper**, fill in the inputs you need, and click **Start**. 3. Watch results stream into the dataset table as each record is parsed. 4. **Export** as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the [Apify API](https://docs.apify.com/api/v2). ### Input ```json { "cities": ["San Francisco", "New York"], "searchQueries": ["ai", "crypto"], "outputType": "all", "eventType": "any", "enrichEvents": true, "includeCalendarLeads": true, "maxResults": 200 } ```` - **outputType** *(default `events`)* — `events`, `calendars` (organizer leads with social handles), or `all` (events + their community calendars, each row tagged with a `type`). - **cities** — city names or Luma slugs (`San Francisco`/`sf`, `New York`/`nyc`, `Austin`, `London`, `Singapore`). Common names are mapped automatically. - **searchQueries** — optional keywords, combined with every city (`ai`, `crypto`, `startup`, `design`). Leave empty to get all of a city's events. - **eventType** *(default `any`)* — `offline` (in-person) or `online`. - **dateFrom / dateTo** — only events starting in this window (`YYYY-MM-DD`). - **onlyFreeEvents** *(default false)* — only free-registration events. - **eventUrls / calendarUrls / startUrls** — scrape specific events or communities directly (full URLs, slugs, or `evt-`/`cal-` api\_ids; `startUrls` accepts a mixed list and auto-routes each). - **enrichEvents** *(default true)* — open each event for description, categories, exact capacity/spots-left, price and the full host list. One fast API call per event; turn off for a faster run. - **includeCalendarLeads** *(default true)* — in `all` mode, emit one community-lead record per unique organizer. - **includeCalendarEvents** *(default false)* — when scraping a community, also pull its upcoming events. - **maxResults** *(default 200, 0 = no limit)* — cap on primary records; keeps test runs cheap and predictable. - **maxConcurrency** *(default 6)* — maximum parallel API calls. - **proxyConfiguration** — Apify Proxy (datacenter, the default) works well; Luma's public API is light on anti-bot. ### Output By default you get one clean table of events. Set `outputType` to `calendars` for organizer leads, or `all` to combine both (each row tagged with a `type` of `event` or `calendar`). An event record (`type: "event"`): ```json { "type": "event", "eventId": "evt-kTedGXXQYZLkTdB", "name": "AI Builders Hack Day", "eventUrl": "https://luma.com/aibuildershack", "startAt": "2026-06-18T16:30:00.000Z", "endAt": "2026-06-19T02:30:00.000Z", "timezone": "America/Los_Angeles", "durationMinutes": 600, "locationType": "in-person", "isOnline": false, "description": "A full day for SF builders to ship real AI projects…", "city": "San Francisco", "regionShort": "CA", "country": "United States", "countryCode": "US", "latitude": 37.78978, "longitude": -122.39649, "isFree": false, "price": null, "isSoldOut": false, "spotsRemaining": 835, "requireApproval": true, "categories": ["AI"], "coverUrl": "https://images.lumacdn.com/…", "hostNames": ["AWS Builder Loft", "tokens&"], "hostCount": 2, "hosts": [{ "name": "AWS Builder Loft", "website": "https://builder.aws.com/…", "bio": "…", "profileUrl": null }], "calendarId": "cal-EVJ0XV6EJegxAT7", "calendarName": "tokens&", "calendarSlug": "tokensand", "calendarUrl": "https://luma.com/tokensand", "calendarLinkedin": "/company/tokensand", "searchCity": "San Francisco", "searchQuery": "ai", "scrapedAt": "2026-06-12T19:35:55.262Z" } ``` A community record (`type: "calendar"`) carries `name`, `description`, `calendarUrl`, `instagram` / `linkedin` / `tiktok` handles, `lumaPlusActive`, `upcomingEventCount` and a `leadScore`. Luma is organizer-entered data, so some fields appear only when the organizer published them (e.g. a free event has `price: null`, some communities list no socials). A blank field means the organizer didn't publish it — not that scraping failed; nothing is dropped. Attendee personal data is not published by Luma and is not included. ### Monitoring — get only new events Turn on **`onlyNewItems`** to make every run output **only events you haven't received before**. The actor remembers what it has delivered in a persistent store, so on a schedule each run hands you just the newly listed events — ideal for newsletters, lead pipelines and Slack alerts. - Use **`monitorStateKey`** to name the monitor memory so different searches each track their own "already seen" list. Use a different key per search/schedule to keep them independent. - Monitor mode is a per-run "new items only" filter that **works alongside [Apify Schedules](https://docs.apify.com/platform/schedules)** — it does not replace or interfere with the scheduler. ### Automate & schedule Run this actor on autopilot and pull results into your own stack: - **[Apify API](https://docs.apify.com/api/v2)** — start runs, fetch datasets, and manage schedules over REST. - **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs. - **[Schedules](https://docs.apify.com/platform/schedules)** — run it on a cron to keep your data fresh. - **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions the moment a run finishes. ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' }); const run = await client.actor('scrapesage/luma-scraper').call({ cities: ['San Francisco'], searchQueries: ['ai'], outputType: 'all', enrichEvents: true, maxResults: 200, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(`Got ${items.length} records`); ``` ### Integrate with any app Connect the dataset to 5,000+ apps — no code required: - **[Make](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios. - **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new records straight into your CRM or sheet. - **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a run finds something new. - **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet. - **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse. - **[GitHub](https://docs.apify.com/platform/integrations/github)** — trigger runs from commits or releases. ### Use with AI assistants (MCP) The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the **[Apify MCP server](https://docs.apify.com/platform/integrations/mcp)** — ask your assistant to "find AI events in San Francisco on Luma with their community organizers" and let it run this scraper for you. ### More scrapers from scrapesage Build a complete event intelligence & lead-gen stack across every major event platform: - **[Eventbrite Scraper](https://apify.com/scrapesage/eventbrite-scraper)** — events plus organizer leads with contacts. - **[Sched Conference Scraper](https://apify.com/scrapesage/sched-conference-scraper)** — conference speakers, sessions, sponsors & leads. - **[Swapcard Exhibitor Scraper](https://apify.com/scrapesage/swapcard-exhibitor-scraper)** — event exhibitors, speakers & contacts. - **[Whova Event Scraper](https://apify.com/scrapesage/whova-event-scraper)** — event sessions, speakers, sponsors & exhibitors. - **[LinkedIn Jobs Scraper](https://apify.com/scrapesage/linkedin-jobs-scraper)** — filter-based LinkedIn job postings, no login. - **[Bark Listing Scraper](https://apify.com/scrapesage/bark-listing-scraper)** — service-provider directory listings & leads. - **[Facebook Ad Library Scraper](https://apify.com/scrapesage/facebook-ad-library-scraper)** — competitor ad intelligence on Meta & Instagram. - **[Telegram Scraper](https://apify.com/scrapesage/telegram-scraper)** — channels, messages, media & search. ### Tips - **Pick a single `outputType`** (Events or Community calendars) for a clean, fully-populated table. Use `all` to get events plus the communities behind them in one dataset. - **Organizer leads**: run `outputType: "all"` or `calendars` — every unique community becomes a contactable lead with social handles and a lead score. - **Scrape a whole community**: put its URL in `calendarUrls` with `includeCalendarEvents` on to pull all of its upcoming events. - **Faster runs**: turn off `enrichEvents` if you don't need description/categories/price — you still get date, geo, hosts, capacity and the community. - **Recurring monitoring**: combine [Schedules](https://docs.apify.com/platform/schedules) with `onlyNewItems` (and a distinct `monitorStateKey` per search) to capture only newly listed events each day. ### FAQ **How do I scrape Luma events for a city?** Put the city in `cities` (`San Francisco`, `New York`, `Austin`, `London`, `Singapore`, or Luma slugs like `sf`/`nyc`). Add keywords in `searchQueries` to narrow by topic. **Does it work on luma.com and lu.ma?** Yes — Luma rebranded from lu.ma to luma.com; this actor reads the same internal API that powers both. **Does it need a Luma API key or login?** No. This actor reads Luma's public internal API — no key or login needed. **Can I scrape a single community or event?** Yes — paste its URL into `calendarUrls` or `eventUrls` (or a mixed list in `startUrls`). Communities can also yield all their upcoming events with `includeCalendarEvents`. **How do I get only new events on a schedule?** Turn on monitor mode (`onlyNewItems`) and create a [Schedule](https://docs.apify.com/platform/schedules). Each run returns only events it hasn't delivered before, and works alongside the scheduler. **Where do the leads come from?** From each event's public host list and its community calendar page on Luma (description, Instagram/LinkedIn/TikTok). Attendee personal data is not published by Luma and is not included. **Can I export to Google Sheets, CSV or Excel?** Yes — one click in the dataset view, or automatically on every run via the [Google Drive integration](https://docs.apify.com/platform/integrations/drive). ### Need help? Open an issue on the actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained. # Actor input Schema ## `outputType` (type: `string`): `Events` (default) returns Luma events. `Community calendars` returns the organizers/communities behind events as leads (with social handles). `All` returns events + their community calendars, each row tagged with a `type`. ## `cities` (type: `array`): Luma curates events by city. Enter city names or Luma slugs, e.g. `San Francisco`, `New York`, `Austin`, `London`, `Singapore` (or slugs like `sf`, `nyc`, `la`). Common names are mapped automatically. ## `searchQueries` (type: `array`): Optional keywords to filter each city's events, e.g. `ai`, `crypto`, `startup`, `design`. Each keyword is combined with every city. Leave empty to get all of a city's events. ## `eventType` (type: `string`): Limit to in-person or online events. ## `dateFrom` (type: `string`): Only events starting on/after this date. Format: YYYY-MM-DD. ## `dateTo` (type: `string`): Only events starting on/before this date. Format: YYYY-MM-DD. ## `onlyFreeEvents` (type: `boolean`): Return only events with free registration. ## `eventUrls` (type: `array`): Scrape specific Luma events directly. Accepts full URLs (`https://luma.com/abc123`), `lu.ma/abc123`, bare slugs, or event api\_ids (`evt-...`). ## `calendarUrls` (type: `array`): Scrape specific Luma communities (calendars) — returns the organizer lead and, optionally, all of its upcoming events. Accepts URLs, slugs, or calendar api\_ids (`cal-...`). ## `startUrls` (type: `array`): A mixed list of Luma event or calendar URLs — each is auto-detected and routed to the right scraper. ## `enrichEvents` (type: `boolean`): Open each event for its full detail — description, categories, exact capacity/spots-left, ticket price and full host list (with websites and bios). Adds one fast API call per event. Turn off for a faster run that still includes date, geo, hosts, capacity and the community. ## `includeCalendarLeads` (type: `boolean`): When output is `All`, also emit one community-calendar lead record per unique organizer behind the events (name, description, social handles, lead score). ## `includeCalendarEvents` (type: `boolean`): When scraping calendar URLs (or communities), also pull each community's upcoming events into the dataset. ## `onlyNewItems` (type: `boolean`): Output only items that were NOT returned in previous runs. Remembers what it has delivered in a persistent store, so on a schedule each run gives you just the new events. Works alongside Apify Schedules — it does not replace or interfere with the scheduler. ## `monitorStateKey` (type: `string`): Advanced: name the monitor memory so different searches track their own 'already seen' list. Use a different key per search/schedule to keep them independent. ## `maxResults` (type: `integer`): Maximum number of primary records (events, or community calendars in calendar mode) to output (0 = no limit). Keeps test runs cheap and predictable. ## `maxConcurrency` (type: `integer`): Maximum number of parallel API calls. ## `proxyConfiguration` (type: `object`): Proxy settings. Luma's public API is light on anti-bot, so Apify Proxy (datacenter, the default) works well. ## Actor input object example ```json { "outputType": "events", "cities": [ "San Francisco" ], "searchQueries": [ "ai" ], "eventType": "any", "onlyFreeEvents": false, "enrichEvents": true, "includeCalendarLeads": true, "includeCalendarEvents": false, "onlyNewItems": false, "monitorStateKey": "default", "maxResults": 200, "maxConcurrency": 6, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): All scraped records in the default dataset. Use the Events / Community calendars views to filter the columns to one record type. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "cities": [ "San Francisco" ], "searchQueries": [ "ai" ] }; // Run the Actor and wait for it to finish const run = await client.actor("scrapesage/luma-scraper").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "cities": ["San Francisco"], "searchQueries": ["ai"], } # Run the Actor and wait for it to finish run = client.actor("scrapesage/luma-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "cities": [ "San Francisco" ], "searchQueries": [ "ai" ] }' | apify call scrapesage/luma-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapesage/luma-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Luma Scraper — Events & Organizer Leads (lu.ma)", "description": "Scrape Luma (lu.ma / luma.com) events by city, keyword or URL. Rich event data: date, venue geo, price, capacity, spots left, categories and hosts, plus community calendars with social handles as organizer leads. Monitor mode pulls only new events. No login. Export JSON, CSV, Excel.", "version": "1.0", "x-build-id": "KqapIX1Cyust49c81" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapesage~luma-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapesage-luma-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scrapesage~luma-scraper/runs": { "post": { "operationId": "runs-sync-scrapesage-luma-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scrapesage~luma-scraper/run-sync": { "post": { "operationId": "run-sync-scrapesage-luma-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "outputType": { "title": "What to output", "enum": [ "events", "calendars", "all" ], "type": "string", "description": "`Events` (default) returns Luma events. `Community calendars` returns the organizers/communities behind events as leads (with social handles). `All` returns events + their community calendars, each row tagged with a `type`.", "default": "events" }, "cities": { "title": "Cities", "type": "array", "description": "Luma curates events by city. Enter city names or Luma slugs, e.g. `San Francisco`, `New York`, `Austin`, `London`, `Singapore` (or slugs like `sf`, `nyc`, `la`). Common names are mapped automatically.", "items": { "type": "string" } }, "searchQueries": { "title": "Search keywords", "type": "array", "description": "Optional keywords to filter each city's events, e.g. `ai`, `crypto`, `startup`, `design`. Each keyword is combined with every city. Leave empty to get all of a city's events.", "items": { "type": "string" } }, "eventType": { "title": "Event type", "enum": [ "any", "offline", "online" ], "type": "string", "description": "Limit to in-person or online events.", "default": "any" }, "dateFrom": { "title": "Start date (from)", "type": "string", "description": "Only events starting on/after this date. Format: YYYY-MM-DD." }, "dateTo": { "title": "Start date (to)", "type": "string", "description": "Only events starting on/before this date. Format: YYYY-MM-DD." }, "onlyFreeEvents": { "title": "Only free events", "type": "boolean", "description": "Return only events with free registration.", "default": false }, "eventUrls": { "title": "Event URLs", "type": "array", "description": "Scrape specific Luma events directly. Accepts full URLs (`https://luma.com/abc123`), `lu.ma/abc123`, bare slugs, or event api_ids (`evt-...`).", "items": { "type": "string" } }, "calendarUrls": { "title": "Community / calendar URLs", "type": "array", "description": "Scrape specific Luma communities (calendars) — returns the organizer lead and, optionally, all of its upcoming events. Accepts URLs, slugs, or calendar api_ids (`cal-...`).", "items": { "type": "string" } }, "startUrls": { "title": "Mixed Luma URLs", "type": "array", "description": "A mixed list of Luma event or calendar URLs — each is auto-detected and routed to the right scraper.", "items": { "type": "string" } }, "enrichEvents": { "title": "Enrich events (description, categories, full hosts)", "type": "boolean", "description": "Open each event for its full detail — description, categories, exact capacity/spots-left, ticket price and full host list (with websites and bios). Adds one fast API call per event. Turn off for a faster run that still includes date, geo, hosts, capacity and the community.", "default": true }, "includeCalendarLeads": { "title": "Output community/organizer leads", "type": "boolean", "description": "When output is `All`, also emit one community-calendar lead record per unique organizer behind the events (name, description, social handles, lead score).", "default": true }, "includeCalendarEvents": { "title": "Also scrape each community's upcoming events", "type": "boolean", "description": "When scraping calendar URLs (or communities), also pull each community's upcoming events into the dataset.", "default": false }, "onlyNewItems": { "title": "Monitor mode — only new items", "type": "boolean", "description": "Output only items that were NOT returned in previous runs. Remembers what it has delivered in a persistent store, so on a schedule each run gives you just the new events. Works alongside Apify Schedules — it does not replace or interfere with the scheduler.", "default": false }, "monitorStateKey": { "title": "Monitor state key", "type": "string", "description": "Advanced: name the monitor memory so different searches track their own 'already seen' list. Use a different key per search/schedule to keep them independent.", "default": "default" }, "maxResults": { "title": "Max results", "minimum": 0, "type": "integer", "description": "Maximum number of primary records (events, or community calendars in calendar mode) to output (0 = no limit). Keeps test runs cheap and predictable.", "default": 200 }, "maxConcurrency": { "title": "Max concurrency", "minimum": 1, "maximum": 20, "type": "integer", "description": "Maximum number of parallel API calls.", "default": 6 }, "proxyConfiguration": { "title": "Proxy configuration", "type": "object", "description": "Proxy settings. Luma's public API is light on anti-bot, so Apify Proxy (datacenter, the default) works well.", "default": { "useApifyProxy": true } } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```