# Luma Email Scraper - Keyword Search & Domain Filter (`parse-point/luma-email-scraper-lightning-fast-and-accurate`) Actor

✨ Luma Email Scraper pulls event host and organizer emails with keyword and location filters. 🎯 Limit to chosen domains, decode hidden addresses and drop duplicates. 🎤 Built for event sponsorship and community sales.

- **URL**: https://apify.com/parse-point/luma-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — 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 Email Scraper 🔍

**Luma Email Scraper** helps you extract emails from publicly available Luma content without manual hunting. It’s built for marketers, recruiters, sales pros, researchers, and anyone doing Luma lead generation, Luma contact scraper work, or Luma email finder tasks at scale. 🚀

### 🌟 Key Features of Luma Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Use your keywords to find relevant Luma profiles, helping you focus on the right audience faster. |
| ✅ **Custom Domain Filtering** | Narrow results to specific email domains like `@gmail.com` or `@yahoo.com` for better Luma contact extraction. |
| ✅ **Location Filter** | Add a location to refine results for more precise Luma audience scraping and lead discovery. |
| ✅ **Max Emails Limit** | Set a cap on results to control run size, time, and costs. |
| ✅ **Built-In Proxy Support** | Uses built-in proxy support for more reliable scraping and smoother runs. |
| ✅ **Incremental Saving** | Saves results as they are found, reducing the risk of losing data during longer runs. |
| ✅ **Resume Progress** | Can continue from saved progress, which is helpful for larger Luma event scraping jobs. |
| ✅ **Public Data Extraction** | Scrapes email addresses from publicly available sources on Luma for practical lead generation. |

### 📥 Input — Luma Email Scraper Parameters

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager","founder"]` | A list of keywords or queries to find relevant Luma results. |
| `location` | String | No | `""` | Optional location filter to narrow your search results. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | A list of email domains to match, such as personal or company domains. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

### 📤 Output — What Luma Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset. 📦

```json
[
  {
    "keyword": "founder",
    "title": "Startup Growth Summit",
    "description": "Community event for founders, operators, and builders in San Francisco.",
    "url": "https://lu.ma/startup-growth-summit",
    "email": "alex.johnson@gmail.com"
  }
]
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that produced the result. |
| `title` | Title | text | The title associated with the result. |
| `description` | Description | text | The public description text captured for the result. |
| `url` | Url | link | The public link for the result. |
| `email` | Email | text | The email address found in the public content. |

### 💻 How to Use Luma Email Scraper — Step-by-Step

1. **Open the Actor** — Start **Luma Email Scraper** in Apify and get ready to find public Luma contacts.
2. **Enter Keywords** — Add keywords that match the people, roles, or topics you want to target.
3. **Set Location** — Optionally narrow results with a location for more focused Luma event lead generation.
4. **Add Email Domains** — Include the domains you want to prioritize, such as `@gmail.com` or `@yahoo.com`.
5. **Set Max Emails** — Control how many leads you want in a single run.
6. **Run the Actor** — Launch the actor and monitor progress in real time.
7. **Export Results** — Download the dataset and use it for outreach, analysis, or CRM enrichment.

No coding required — results are ready in minutes. ⚡

### 💡 Best Use Cases for Luma Email Scraper

- 🎯 **B2B Lead Generation** — Build targeted contact lists from public Luma data.
- 📣 **Email Marketing** — Collect contacts for newsletters, outreach, and follow-up campaigns.
- 🤝 **Recruitment** — Find public contact details for candidates, speakers, and event organizers.
- 🔬 **Market Research** — Support Luma registration data scraping and audience analysis.
- 📊 **CRM Enrichment** — Add new public contacts to existing lead records and prospect databases.

### Disclaimer

This actor only accesses **publicly available data** on Luma. It does not scrape private profiles, authenticated content, or password-protected pages. Users are solely responsible for ensuring their use complies with Luma’s Terms of Service, GDPR, CCPA, and applicable anti-spam laws. This tool is intended for legitimate purposes only — including research, lead generation, and marketing in compliance with local regulations. For data-removal requests, contact 📧 <hello.parsepoint@gmail.com>.

### 🆘 Support & Feedback

Have a question or found an issue with the **Luma Email Scraper**? We’re here to help.

- 🐞 **Bug Reports:** Share the issue details so it can be investigated quickly.
- ✨ **Custom Solutions & Feature Requests:** Reach out if you need tailored Luma automation tool support.
- 📧 **Email:** <hello.parsepoint@gmail.com>

Your feedback helps improve the Luma email extraction tool for everyone.

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Location to filter search results.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

# Actor output Schema

## `dataset` (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 = {
    "keywords": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("parse-point/luma-email-scraper-lightning-fast-and-accurate").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 = {
    "keywords": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parse-point/luma-email-scraper-lightning-fast-and-accurate").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 '{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call parse-point/luma-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/luma-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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/ouApeyitZ7A0bCOSV/builds/msz0mnb4YdVspVnTH/openapi.json