YouTube Creator Email Finder — Contacts & Channel Stats

The YouTube Creator Email Finder finds publicly available contact emails for YouTube channels — in any country or language — plus subscriber counts, view counts, join date, country and external links. Server-side, no login, no browser, no email sending. You pay only for emails found.

What it does

Input	Result
Channel handles / URLs / IDs (@mkbhd, https://youtube.com/@x, UC...)	One dataset row per channel with stats + public emails
Search queries ("tech review", "beauty tips")	The top channel results of the query (up to 30), then processed like above

Per channel the actor:

1. Reads the public .../about page (embedded ytInitialData payload — the same data the page renders from).
2. Extracts description, subscriber count, views, join date, country and external links (redirects resolved).
3. Extracts public emails from the description and, optionally, from the channel's own linked website (homepage + up to 2 contact/about pages; social profiles are never crawled). Common obfuscations like name [at] domain [dot] com are converted.
4. Validates every address through the full set: format checks, domain mail-server lookup (DNS "MX" records) and noise filtering — dead or malformed addresses are dropped (valid_syntax, has_mx, mx_hosts in the output). No email is ever sent.
5. Flags channels whose business email exists but requires sign-in (email_hidden_behind_login: true) — the address itself is not returned, because it is not public.

When should you use this Actor?

• "I need contact emails of YouTube creators for outreach or sponsorships." — give it channels or a niche search and get validated contacts back.
• "I have a list of channel handles or URLs and need their emails and stats." — one row per channel: emails, subscribers, views, country and links.
• "I want to discover creators in a niche and reach out." — run search queries like "tech review" and get the top channels with contacts.
• "I need to watch for new creator contacts over time." — enable Only new emails and schedule the run; each run returns only emails not seen before.

Why this Actor

• Pay only for emails found — $5 per 1,000 emails; channels without a discoverable public email are free to process.
• Validated, not guessed — every address passes format checks, mail-server ("MX") record lookup and noise filtering before it reaches the output.
• Honest about limits — business emails hidden behind sign-in are flagged (email_hidden_behind_login), never invented; no captcha bypass, no login walls, no SMTP probing. Observed coverage is typically 20–35% of channels, depending on the niche.
• Worldwide — channels from any country and language, with subscriber/view stats and typed external links.

Use cases

• Influencer outreach & sponsorships — build creator contact lists for brand deals.
• Niche discovery — run keyword searches ("fitness", "SaaS reviews") and get the top channels in that niche, with contacts.
• Ongoing monitoring — schedule weekly runs with onlyNewEmails to receive only the contact details that are new.
• CRM enrichment — feed handles you already have; get stats + contacts as clean JSON.

Input example

{
  "channels": ["@mkbhd", "https://www.youtube.com/@MrBeast"],
  "searchQueries": ["tech review"],
  "maxChannels": 50,
  "enrichFromLinks": true,
  "validateMx": true,
  "onlyNewEmails": false
}

All fields are optional — provide channels, searchQueries, or both. The full field reference is in the Input tab.

Output

One row per channel: handle, url, title, description, subscriber_count, view_count, joined_date, country, links (typed: website / social / other), emails (with source + validation: valid_syntax, has_mx, mx_hosts), email_hidden_behind_login, scraped_at. See the Output tab for a real example.

Pricing

Pay per event — you are charged only for emails found (email-found event): $5.00 per 1,000 email addresses returned (plus a nominal run start fee). Channels without a discoverable public email are free to process, and full email validation (format + mail records) is included at no extra charge.

Honest scope

• Only publicly visible emails are returned. Channels without a public contact email produce a row with an empty emails array — never a guessed address.
• Observed public-email coverage on samples: roughly 20–35% of channels, depending on niche.
• No captcha bypass, no login walls, no SMTP probing, no personal-data guessing.

FAQ

• Do I pay for channels with no email? No — only found emails are charged.
• Why is an email I see on YouTube not in the output? Some business emails sit behind YouTube's sign-in wall; those channels are flagged (email_hidden_behind_login) instead of pretending to fetch the address.
• Which countries and languages are covered? All — channels are processed worldwide, in any language; the channel's public country (when set) is included in the output.
• Does it send emails or test mailboxes? Neither — validation is address format + the domain's public mail-server (MX) records. Nothing is ever sent or probed.
• How do I monitor for new emails? Enable onlyNewEmails and schedule the actor; each run returns only emails not seen in previous runs.

Run via API or MCP

curl -X POST "https://api.apify.com/v2/acts/devjoi~youtube-creator-emails/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"channels": ["@mkbhd"], "maxChannels": 20}'

The Actor is fully described by its input/output schemas, so LLM agents can discover and call it through the Apify MCP server.

Development

npm install
npm test                 # 32 tests: unit (parsing, emails), e2e pipeline (stubbed HTTP + real-shaped fixtures), dataset schema (incl. negative cases)
npm run local            # live run against YouTube with a demo input (writes local-output.json)
RUN_LIVE=1 npm run test:live   # live integration test (real network)
node scripts/validate-dataset-schema.mjs   # validate local-output.json against .actor/dataset_schema.json

Layout: src/main.js (Apify wiring) · src/core/pipeline.js (all business logic, dependency-injected) · src/lib/ (http, html-json, youtube, emails, pool) · .actor/ (schemas) · tests/ (fixtures modeled on real page shapes).