Twitch Email Scraper - Keyword & Location Targeting
Pricing
from $2.50 / 1,000 results
Twitch Email Scraper - Keyword & Location Targeting
🟣 Twitch Email Scraper finds streamer business emails by keyword and location. 🔓 Custom domain filters, decoding and duplicate handling. 📤 Export Twitch leads to CSV, JSON or Excel for gaming sponsorship outreach.
Pricing
from $2.50 / 1,000 results
Rating
0.0
(0)
Developer
Scrapido
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Twitch Email Scraper
Twitch Email Scraper is an Apify actor that automates contact research by extracting email addresses from Twitch based on your chosen keywords and email-domain filters. If you’re a marketer, recruiter, or data team spending hours finding outreach contacts manually, this tool helps you scale Twitch streamer email finder work into minutes—turning leads into actionable lists with strong ROI.
What is Twitch Email Scraper? 🔍
Twitch Email Scraper is an automated web scraping tool (an Apify actor) built to extract email addresses from Twitch using keywords you provide. It helps solve the biggest pain point in Twitch creator outreach: manual searching and copy/paste contact research that doesn’t scale. This actor is used by marketers, recruiters, sales teams, and analysts to quickly discover publicly available Twitch contact information at scale—often generating thousands of candidate leads across keyword variations in a single run. If you’re looking for a Twitch email extractor, Twitch contact scraper, or a Twitch lead generation tool, this actor gives you structured, export-ready results you can trust for downstream work.
What Data Does a Twitch Email Scraper Collect? 📊
This actor captures contact emails plus the context needed to understand where each email came from on Twitch. You’ll get profile identity, bio/summary text, discovery keyword, direct navigation link, and any location listed.
| Data Category | Fields Extracted | Description |
|---|---|---|
| Contact | email | Public email address found on a Twitch profile |
| Identity | title | Profile name, business title, or similar text associated with the result |
| Context | description | Text describing the profile (e.g., bio/tagline/summary content) |
| Discovery | keyword | Search term used to surface this result |
| Navigation | url | Direct link to the Twitch profile page |
| Location | (not provided by dataset schema) | The dataset schema includes no separate location field |
Note: Although the user-facing input includes
location, the dataset output schema provided for this actor contains only:keyword,title,description,url,
What Do Results from Twitch Email Scraper Look Like? 👀
Each result is a structured record saved to your Apify dataset. Here’s a real example:
{"keyword": "manager","title": "Lena Hart","description": "Studio Ops Manager | Partnered streamer | Contact me for collaborations and brand deals.","url": "https://www.twitch.tv/lenahart","email": "lena.hart@studioworks.com"}
Each dataset row is ready for JSON export in Apify (and CSV export via Apify Console).
Core Features: Twitch Email Scraper ⚡
| Feature | Benefit |
|---|---|
| ✅ Keyword-Driven Targeting | Use your own search terms to find relevant Twitch streamer email finder leads |
| ✅ Location Filter (Input) | Narrow discovery with the optional location parameter |
| ✅ Custom Domain Filter | Restrict extraction to specific email domains via customDomains (e.g., @gmail.com, @yahoo.com) |
| ✅ Configurable Result Cap | Use maxEmails to control how many emails are collected in one run |
| ✅ Proxy Support | Built-in proxy support helps maintain reliable scraping at scale |
| ✅ Real-Time Data Saving | Results are pushed incrementally so you don’t lose everything if a run stops early |
| ✅ Structured Dataset Output | Clean dataset rows with exactly these fields: keyword, title, description, url, email |
| ✅ Designed for Outreach Lists | Supports Twitch data mining and creator outreach workflows with a straightforward dataset |
| ✅ Public Data Only | Focused on extracting publicly available data from Twitch profiles |
Getting Started with Twitch Email Scraper 🚀
- Open Apify Store — Go to apify.com/store and search Twitch Email Scraper
- Click Try for Free — Sign in or create a free Apify account
- Open the Input Tab — Configure your keywords and optional filters
- Add Keywords — Enter the roles or terms you want to match (e.g.,
manager,founder) - Set Optional Filters — Add a
locationfilter andcustomDomainsto target specific email providers - Cap Your Results — Set
maxEmailsto control run size, cost, and speed - Click Start — Launch and monitor the run
- Access Your Data — Open the Dataset tab to preview and export your leads
Ways to Use Twitch Email Scraper 💡
- 🎯 Twitch creator outreach — Build segmented Twitch outreach lists using targeted keywords and domain filters
- 📣 Email harvesting tool — Automate extraction of contact emails from Twitch profiles where emails are publicly listed
- 🤝 Twitch streamer email finder — Speed up finding the right point of contact for campaigns and collaborations
- 🧠 Twitch data mining — Analyze which niches and roles produce email coverage
- ⚙️ Automated outreach pipeline — Feed clean dataset rows into CRM enrichment and follow-up automation
- 🔬 Contact info extraction — Collect leads for B2C outreach lists and creator partnership outreach
Input Parameters — Twitch Email Scraper
Provide your settings in the Apify input. Example:
{"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 used to find relevant Twitch profiles |
location | String | No | "" | Location to filter search results (leave empty to run without a geo constraint) |
customDomains | Array | No | ["@gmail.com","@yahoo.com"] | Only extract emails that match these domains (for example @gmail.com) |
maxEmails | Integer | No | 20 | Maximum number of emails to collect. Higher caps can increase runtime but doesn’t guarantee the exact count |
Output Parameters — Twitch Email Scraper
The actor saves results into the default Apify dataset view (“Scraped Leads”) with the following schema:
Example dataset row:
{"keyword": "creative director","title": "Maya Kline","description": "Creative Director | Streaming live + building brand partnerships. Email for business inquiries.","url": "https://www.twitch.tv/mayakline","email": "maya.kline@brandsatelier.com"}
| Field | Label | Format | Description |
|---|---|---|---|
keyword | Keyword | text | The keyword used to surface this result |
title | Title | text | Profile name, business title, or similar identifying text |
description | Description | text | Profile description/bio/summary text extracted from the public page |
url | Url | link | Direct link to the Twitch profile |
email | text | Extracted public email address |
Why Choose This Twitch Email Scraper? 🏆
Twitch Email Scraper is built for speed and usability: you provide keywords and optional filters, and you get a structured dataset ready for downstream work like CRM import and outreach segmentation. It supports proxy usage for more reliable scraping at scale, saves results incrementally, and lets you tightly control output volume with maxEmails. If you’re comparing alternatives, this approach is often more cost-efficient than broad subscriptions because you can cap exactly how many emails you want per run—so your automated outreach pipeline starts with predictable inputs and clear outputs. For tailored help, contact: scrapidocontact@gmail.com.
How Many Results Can You Scrape? 📈
Use maxEmails to set an upper cap from 1 up to 10,000. Actual yield depends on how many Twitch profiles that match your keywords and customDomains publicly list emails. For larger batches, consider using broader keywords or more relevant email domains to improve coverage. Results are stored in the Apify dataset, and you can export any time after the run finishes.
Legal Guidelines for Scraping Twitch ⚖️
Twitch Email Scraper extracts information from publicly accessible sources on Twitch profiles. It does not access private or password-protected pages. You are responsible for complying with Twitch’s Terms of Service, applicable privacy laws (like GDPR/CCPA where relevant), and anti-spam regulations. Use extracted contacts for legitimate business purposes only. If you need data removal, contact: scrapidocontact@gmail.com.
FAQ — Twitch Email Scraper ❓
How does the Twitch Email Scraper identify data?
The actor uses the keywords you provide to discover relevant Twitch pages and then extracts email addresses and associated public profile text into the dataset. It relies on publicly displayed content and does not require authentication.
What Twitch profile types can I scrape?
You can scrape public Twitch profiles that display an email address and associated public profile text. If a profile does not include a public email address, it won’t produce an email value in the dataset row.
How did the Twitch Email Scraper perform in our tests?
Performance depends on how well your chosen keywords match Twitch profiles and how many matching profiles include public emails for the domains you specify in customDomains. If results are limited, broadening keywords or adding more domains usually improves coverage.
Why scrape Twitch for contacts?
Twitch hosts creators, communities, and business-minded streamers who often publish contact emails publicly. Twitch Email Scraper automates contact info extraction, making it easier to create outreach-ready lead lists without manual searching.
How much does the Twitch Email Scraper cost?
Cost is controlled by output volume. Use maxEmails to cap how many emails are collected per run, helping you manage spend. (Exact pricing depends on Apify’s marketplace plan and run configuration.)
How does the Twitch Email Scraper help my business?
It helps you build Twitch creator outreach lists and B2C outreach lists faster by producing a structured dataset with keyword, title, description, url, and email—ready for CRM enrichment and email outreach workflows.
What challenges should I expect when using the Twitch Email Scraper?
Not every Twitch profile includes a public email address, so final output can be lower than your maxEmails target. If you see fewer results than expected, try wider keywords, related terms, different customDomains, or add/remove the location filter.
How do I choose a high-performing Twitch Email Scraper?
Choose runs that use targeted keywords, appropriate email-domain filters in customDomains, and a sensible maxEmails cap. This actor is especially useful when you want clean, exportable results for automated outreach pipelines and lead generation from Twitch.
Conclusion 🏁
Twitch Email Scraper is a fast, structured way to extract publicly available Twitch emails at scale. Whether you’re building lead lists, enriching a CRM, or running an automated outreach pipeline, you can start with keywords and fine-tune domains and caps for efficient results on Apify.
🆘 Support & Feedback
Have a question or feature request for Twitch Email Scraper?
Please email scrapidocontact@gmail.com.
Multiple Email Types
Email Types replaces the old single Audience Type choice: select as many kinds of mailbox as you want and the run chases all of them together.
| Type | What it matches |
|---|---|
| Personal / free webmail | Gmail, Outlook, Yahoo, iCloud, AOL, Proton, ... |
| Business / corporate | Company domains - free webmail and institutions excluded |
| Education (.edu / .ac) | .edu, .ac.uk, .edu.au, .ac.in and other academic suffixes |
| Government (.gov / .mil) | .gov, .mil, .gov.uk, .gc.ca, ... |
| Non-profit (.org) | .org, .ngo, .org.uk, ... |
Each selected type contributes its own Google dork patterns and its own domain
test, so a result is only kept if it genuinely belongs to the type that found
it. Every row carries an emailType field recording which one that was.
Suffixes are matched as real domain suffixes, so cs.mit.edu counts as
Education while notedu.com does not.
Setting Custom Email Domains still overrides everything: an explicit domain
list is a manual override and replaces the type-driven patterns. The legacy
audienceType value is still accepted, so saved inputs keep working.