Luma Email Scraper
Pricing
from $2.99 / 1,000 results
Luma Email Scraper
📧 Luma Email Scraper automatically extracts verified emails from Luma profiles with smart filters for accurate lead lists. Perfect for sales, recruiting, and marketing teams—faster outreach, less manual work. 🚀
Pricing
from $2.99 / 1,000 results
Rating
0.0
(0)
Developer
SolidScraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Luma Email Scraper 📬
Luma Email Scraper is an Apify actor that helps you extract email addresses related to Luma profiles using your selected keywords and custom email-domain filters. Whether you're a marketer, lead researcher, or data analyst, this Luma email scraper makes it easier to build outreach lists by collecting contact emails surfaced from publicly available data tied to your topic. It’s designed for “email scraper for Luma” and “Luma lead scraper” workflows—so you can scale contact discovery and save hours of manual work.
Why choose Luma Email Scraper?
| Feature | Benefit |
|---|---|
| ✅ Keyword-based Luma email discovery | Finds emails associated with Luma bios/posts related to your keywords |
| ✅ Custom email-domain targeting | Filters results using your customDomains (e.g., @gmail.com) for better-fit leads |
| ✅ Two scraping engines | Switch between legacy and cost-effective to match speed vs reliability needs |
| ✅ Reliability with retries & fallbacks | Includes retries and fallbacks for resilience when results are limited |
| ✅ Structured dataset output | Outputs a consistent row format with network, keyword, title, url, and email |
| ✅ Scale controls | Use maxEmails to stop when you reach your desired volume (helps control time and cost) |
Key features
- 🔎 Targeted email extraction: Extracts email addresses that match your specified email-domain filters from publicly available Luma-related content
- 🧠 Keyword-driven lead generation: Uses your
keywordsto surface relevant contacts for your “email scraper for Luma” use case - 🎯 Domain filtering (precision): Use
customDomainsto focus on emails from domains you care about (like@gmail.com) - 🛡️ Resilient scraping behavior: Built-in retry logic and fallback handling to keep runs effective when results are inconsistent
- ⚙️ Engine flexibility: Choose between
cost-effective(faster/cheaper approach using residential proxies) andlegacy(more traditional, reliability-focused approach) - 💾 Real-time saving to dataset: Each discovered email row is pushed to the dataset as soon as it’s found
- ⏱️ Practical scale controls: Stops automatically once
maxEmailsis reached, so you can run bulk email scraping tool workflows without uncontrolled runtimes
Input
Provide input via an input.json file. Example structure:
{"keywords": ["dj event"],"location": "","platform": "Luma","customDomains": ["@gmail.com"],"maxEmails": 20,"engine": "legacy","proxyConfiguration": {}}
Input Fields
| Field | Required | Description |
|---|---|---|
keywords | ✅ Yes | A list of keywords to search for (these drive which Luma bios/posts are considered for email extraction). |
location | ❌ No | Location to filter results. Leave empty ("") for no location filtering. |
platform | ❌ No | Select platform. This actor supports Luma (default: Luma). |
customDomains | ❌ No | List of custom email domains used to filter extracted emails (default includes @gmail.com). |
maxEmails | ❌ No | Maximum number of emails to collect. The scraper stops once this limit is reached. Default is 20. |
engine | ❌ No | Choose scraping engine: cost-effective (cost effective using residential proxies) or legacy (more traditional approach). Default is legacy. |
proxyConfiguration | ❌ No | Proxy configuration for this Actor (configured via Apify proxy settings). |
Output
The actor saves discovered leads as rows in a JSON dataset. Each pushed row represents one email contact tied to a keyword result.
[{"network": "Luma.com","keyword": "dj event","title": "No title","description": "No data","url": "No URL","email": "example@gmail.com"}]
Output Fields
| Field | Type | Description |
|---|---|---|
network | string | Source label for the extracted results (set to Luma.com). |
keyword | string | The keyword that led to this result. |
title | string | Title associated with the result item. |
description | string | Description/snippet text where the email was found. |
url | string | URL associated with the result item. |
email | string | The extracted email address that matches your domain filters. |
Export tip: Apify lets you export dataset results to formats like JSON/CSV from the dataset page, which is handy for CRM import or spreadsheet analysis.
How to use Luma Email Scraper (via Apify Console)
-
Open Apify Console
Log in at https://console.apify.com and open the Actors section. -
Find the actor
Search for Luma Email Scraper and open the actor details page. -
Go to the INPUT tab and configure your run
Fill inkeywords(required). AddcustomDomainsif you want tighter targeting (for example, only emails like@gmail.com). -
Set engine and limits
Chooseengine(legacyorcost-effective) and optionally setmaxEmailsto control how many emails you want per run. -
(Optional) Configure proxies
If you’re running large searches or need more resilience, configureproxyConfigurationusing the Apify proxy settings. -
Click Run
Start the actor and monitor progress in the logs. You’ll see messages when pages are fetched successfully and when emails are pushed to the dataset. -
Open the OUTPUT dataset
Once the run finishes, open the dataset to view and export the collectednetwork,keyword,title,description,url, andemailrows.
No coding required—get relevant Luma contact emails in minutes with Luma Email Scraper. 🚀
Advanced features & SEO optimization
- 🧩 Engineered for Luma email extraction: Optimized for “Luma email scraper” workflows like automated email discovery and lead generation email scraper pipelines.
- 🔄 Rate-limit friendly resilience: Includes retries and fallbacks when results are limited or inconsistent, helping improve outcomes for automatic email scraping runs.
- 🎛️ Input normalization & filtering: Uses your
keywordsplus yourcustomDomainsto focus extraction on emails from the domains that matter to your campaign. - 📝 Progress-aware runs: Maintains persistent progress (cursor and seen emails) so long runs don’t lose work when interrupted.
- 📊 Bulk-ready dataset rows: Each email is immediately pushed as a structured record—ideal for B2B email scraper analysis and downstream automation.
Best use cases
- 📈 B2B lead generation teams: Quickly assemble contact emails for outreach campaigns based on event and audience keywords.
- 🧪 Market researchers: Build datasets of Luma contact emails to compare niches, topics, and community segments.
- 🎯 Email marketing analysts: Validate list quality by exporting consistent
keyword-linked email results for segmentation. - 🧰 CRM and outreach operations: Use the structured dataset rows to automate enrichment and keep lead sources traceable by
urlandkeyword. - 🔎 Growth marketers: Run bulk email scraping tool tasks to expand prospect lists around specific themes.
- 💻 Developer and data workflows: Treat Luma Email Scraper as a data source that outputs clean JSON rows for ETL pipelines.
- 🌐 Contact data enrichment: Combine keyword context (
keyword,title,description) withemailto improve matching in downstream systems.
Technical specifications
-
Supported Input Formats
- ✅
keywordsas an array of strings - ✅
locationas a string (optional) - ✅
platformasLuma(default) - ✅
customDomainsas an array of strings (optional) - ✅
maxEmailsas an integer between1and10000 - ✅
proxyConfigurationas an object configured via Apify proxy editor
- ✅
-
Proxy Support
- ✅ Built-in proxy configuration via
proxyConfiguration - ✅
enginesupportscost-effectiveandlegacybehaviors for different reliability/speed needs
- ✅ Built-in proxy configuration via
-
Retry Mechanism
- ✅ Includes retries and fallbacks for improved resilience when fetching or parsing results
-
Dataset Structure
- ✅ JSON dataset rows with:
network,keyword,title,description,url,email
- ✅ JSON dataset rows with:
-
Rate Limits & Performance
- ✅ Uses
maxEmailsto stop once you reach the target count - ✅ Large searches or high email limits may increase runtime (default guidance in the actor input notes)
- ✅ Uses
-
Limitations
- ❌ Results depend on what’s available in publicly accessible sources tied to the provided keywords and filters
- ❌ Reaching
maxEmailsis not guaranteed if fewer matching emails are found
FAQ
What does the Luma Email Scraper output?
✅ It outputs a dataset of JSON rows where each row includes network, keyword, title, description, url, and the extracted email.
Which inputs are required to start?
✅ You must provide keywords. Other fields like customDomains, location, maxEmails, and engine are optional.
Can I restrict results to specific email domains?
✅ Yes. Use customDomains to filter extracted emails by domain (for example, @gmail.com).
How do I increase results when the email count is low?
✅ Try re-running with broader keywords and more related terms, and/or add more domains to customDomains to match a wider set of publicly available contacts.
Does this scraper require coding or an API key?
❌ No coding is required to run it in Apify Console. You only provide input fields through the built-in form or an input.json file.
Can I control how many emails I collect?
✅ Yes. Set maxEmails. The actor stops when the limit is reached (up to the schema max of 10000).
What’s the difference between legacy and cost-effective engines?
✅ engine lets you choose between legacy and cost-effective behaviors. The input description explains that cost-effective is designed to be faster/cheaper using residential proxies, while legacy is positioned as more reliable but slower and more expensive.
Is this legal and compliant to use for lead generation?
✅ The actor works with publicly accessible sources. You’re responsible for complying with applicable laws and relevant platform policies, including GDPR/CCPA and spam regulations.
Support & feature requests
If you’re using Luma Email Scraper and want to share feedback or ask for improvements, we’re happy to help.
- 💡 Feature Requests: Examples include CSV export enhancements, additional filtering options, or CRM-friendly formats tailored to your workflow.
- 📧 Contact: Send a message to dataforleads@gmail.com.
Your feedback helps shape what we build next for Luma Email Scraper. 🙌
Closing CTA / Final thoughts
If you need an SEO-optimized Luma lead scraper that turns keywords into structured email results, Luma Email Scraper is built for you.
Run it with the right keywords and domain filters—and scale your contact discovery confidently. 🚀
Disclaimer
This tool only accesses publicly accessible sources. It does not access private profiles, authenticated data, or password-protected content.
You are responsible for ensuring your use complies with applicable laws and regulations (including GDPR/CCPA), as well as spam regulations and relevant platform terms of service. For data removal requests, contact dataforleads@gmail.com.
Please use Luma Email Scraper responsibly, ethically, and for legitimate purposes only.