# YouTube Email Finder — Creator & Channel Business Emails (`apricot_blackberry/youtube-email-finder`) Actor

Find the business email behind any YouTube channel. Handle or URL in, verified contact out: About-page business email + website-crawled emails, MX-validated, 1-5 confidence, socials. No login, MCP-ready. Undercuts the $0.12+ competitors.

- **URL**: https://apify.com/apricot\_blackberry/youtube-email-finder.md
- **Developed by:** [Creator Fusion](https://apify.com/apricot_blackberry) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 business email founds

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/actors/running/actors-in-store.md#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

## YouTube Email Finder — Creator & Channel Business Emails

**Reach any YouTuber where it counts: their business inbox.** Give it a channel handle or URL and get the business email behind the channel — the one in the About page *and* the verified addresses on the creator's own website — MX-checked and confidence-scored, in clean typed JSON.

Built for brand-deal outreach, influencer marketing, sponsorship sales, and AI agents that need creator contacts on demand.

### What you get, per channel

- **About-page business email** — the address creators put in their channel description (`found_on: "youtube-about"`), highest intent.
- **Website emails** — if the channel links a website, it's crawled (`/`, `/about`, `/contact`, `/team`, ...) for additional real addresses using the same engine as our Contact Email Finder.
- **MX validation + 1–5 confidence** on every email, so you can filter to deliverable contacts.
- **Social links** the creator published, and the channel's name, URL, and subscriber count.

### Quick start

Just press **Start** (defaults to a couple of demo channels), or:

```json
{ "channels": ["@MrBeast", "https://youtube.com/@mkbhd"] }
```

Add role-pattern fallbacks and cap results:

```json
{ "channels": ["@mkbhd"], "include_patterns": true, "max_emails_per_domain": 5 }
```

### Why this one

- **Two sources, one call** — the About-page email *and* website-crawled emails, not just a regex over the page.
- **Verified, not guessed** — every address is MX-checked and scored; you see *why* each is ranked.
- **Priced to use in bulk** — a fraction of the per-result cost of the incumbent YouTube-email actors.
- **Cookie-free & resilient** — no login, no API key; direct first, proxy only if a website blocks the crawl (billed to you only on fallback).
- **Agent-ready** — typed rows with a `rowType` discriminator and a machine-readable `SUMMARY` in the key-value store.

### Output (by rowType)

- **channel**: `handle`, `channelName`, `channelUrl`, `subscribers`, `website`, `websiteDomain`, `bestEmail`, `emailCount`, `emails[]` (`address`, `source`, `found_on`, `mx_valid`, `confidence`, `format`), `socialLinks[]`.
- **notice**: a guidance row (e.g. no channels supplied) — a run always returns something useful instead of failing.

### Integrations

**REST API (synchronous):**

```bash
curl -X POST "https://api.apify.com/v2/acts/apricot_blackberry~youtube-email-finder/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channels":["@mkbhd"]}'
```

**JavaScript / Python:** use `apify-client` — `client.actor("apricot_blackberry/youtube-email-finder").call({ channels: ["@mkbhd"] })`.
**AI agents (MCP):** exposed via the Apify MCP server — point any MCP client at `https://mcp.apify.com/?tools=apricot_blackberry/youtube-email-finder`.
**No-code:** use the official Apify app in **n8n, Make, and Zapier** and pick `youtube-email-finder`; wire a webhook on run completion.

### 🔗 Works with

- **Don't know which channels to chase yet?** [Data Source Finder](https://apify.com/apricot_blackberry/data-source-finder) finds the creator directories and niche lists to pull handles from.
- **Before you send:** run the emails through [Scrape Trust Score](https://apify.com/apricot_blackberry/scrape-trust-score) to flag dead domains and disposable addresses — so you only pitch real inboxes.

### Honest limits

- Not every channel publishes a business email or a website — those channels return a row with `emailCount: 0` (and you are **not** charged for them; you only pay when an email is returned).
- Emails come from what the creator has made public (About page + their linked site). This does not defeat logins, captchas, or contact forms.
- Inline About-page emails are lightly cleaned for trailing-text artifacts; always verify before sending.

# Actor input Schema

## `channels` (type: `array`):

Channel handles or URLs — e.g. "@MrBeast", "https://youtube.com/@mkbhd". Business email + website emails are returned per channel.

## `channel` (type: `string`):

Convenience field for one channel handle or URL.

## `crawl_website` (type: `boolean`):

If the channel links a website, crawl it (/, /about, /contact, /team...) for additional verified emails.

## `include_patterns` (type: `boolean`):

Add common role emails (info@, contact@, press@) for the creator's website domain when few are found.

## `mx_validate` (type: `boolean`):

Check that each email's domain accepts mail (MX lookup) and reflect it in the confidence score.

## `max_emails_per_domain` (type: `integer`):

Cap emails returned per channel.

## `maxChannels` (type: `integer`):

Cap channels processed in one run.

## `proxyConfiguration` (type: `object`):

Optional. Used only if a direct website crawl is blocked.

## Actor input object example

```json
{
  "channels": [
    "@MrBeast",
    "@mkbhd"
  ],
  "crawl_website": true,
  "include_patterns": false,
  "mx_validate": true,
  "max_emails_per_domain": 8,
  "maxChannels": 50
}
```

# Actor output Schema

## `channels` (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 = {
    "channels": [
        "@MrBeast",
        "@mkbhd"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apricot_blackberry/youtube-email-finder").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 = { "channels": [
        "@MrBeast",
        "@mkbhd",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("apricot_blackberry/youtube-email-finder").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 '{
  "channels": [
    "@MrBeast",
    "@mkbhd"
  ]
}' |
apify call apricot_blackberry/youtube-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apricot_blackberry/youtube-email-finder"
        }
    }
}

```

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/q332EgXxAA5l0l5Gd/builds/Lnkg4QQEhaV2aBzEi/openapi.json