# YouTube Email Scraper - Creator Contact Finder (`ritaya/youtube-creator-finder`) Actor

Find YouTube creators by niche and extract channel contact emails, subscribers, country & social links. No login - pay only per result.

- **URL**: https://apify.com/ritaya/youtube-creator-finder.md
- **Developed by:** [Zane](https://apify.com/ritaya) (community)
- **Categories:** Lead generation, Social media, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

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/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

## YouTube Email Scraper - Creator & Channel Contact Finder

**YouTube email scraper** and **creator contact finder**: discover YouTube channels by
niche, enrich each with **no-login** data (subscribers, country, total views, social
links), and recover a **contact email** from the creator's linked website / Linktree.

Built for **lead generation**, influencer-marketing outreach, sponsorship prospecting and
B2B-to-creator sales. Keywords: youtube email scraper, youtube channel email extractor,
creator contact finder, influencer email finder, youtube lead generation, bulk youtube
channel scraper.

This is the **Path A** (no-account) build. See *Roadmap* for the premium Path B.

### Why this works without a logged-in account

The channel `/about` page is server-rendered with an embedded `ytInitialData` JSON blob.
It already contains the header stats and the creator's external links
(`channelExternalLinkViewModel`). Only YouTube's *native* business-email reveal is gated
behind `signInForBusinessEmail` (a Google account + CAPTCHA) — that is **Path B**, out of
scope here. Path A recovers emails by following the linked sites instead.

Validated live from a US residential IP: discovery, enrichment and link extraction are
100% reliable; linked-site email recovery lands a real creator email for ~20–35% of
channels (the rest expose only social links or a contact form).

### Input

| field | meaning |
|---|---|
| `searchQueries` | niches/keywords to discover creators by |
| `channelUrls` | known `@handle` / `/channel/ID` list to enrich directly |
| `maxChannelsPerQuery` | cap per keyword (default 10) |
| `minSubscribers` | drop channels below this size (lead quality filter) |
| `country` | keep only channels whose About-page country matches |
| `scrapeEmails` | follow linked sites to recover an email (default true) |
| `concurrency` | parallel channels (default 5) |
| `proxyConfiguration` | residential proxy; match group country to `country` |

### Output (one item per channel)

```json
{
  "channelName": "Nischa", "handle": "@nischa",
  "channelUrl": "https://www.youtube.com/@nischa", "channelId": "UC...",
  "subscribers": 2210000, "subscribersText": "2.21M subscribers",
  "totalViews": "136,276,016 views", "videosText": "300 videos",
  "country": "United Kingdom",
  "emails": ["team@nischa.me"],
  "links": ["https://nischa.me/links", "..."],
  "description": "...", "sourceQuery": "personal finance youtuber"
}
```

### Pricing (PAY\_PER\_EVENT)

Register these in the Apify console at publish time (names must match `Actor.charge`):

| event | suggested price | when |
|---|---|---|
| `channel-enriched` | $0.01 | every channel returned |
| `email-found` | $0.04 | only when an email is recovered |

Mid-market vs the niche: cheap bulk scrapers charge ~$0.03/result, the premium
account-based reveal (dataovercoffee) charges $0.12. Path A sits in between on value:
always-on enrichment + best-effort email.

### Run locally

```bash
mkdir -p storage/key_value_stores/default
cp .actor/input.example.json storage/key_value_stores/default/INPUT.json   # or write your own
APIFY_LOCAL_STORAGE_DIR="$PWD/storage" \
  uv run --with apify --with "httpx[http2]" python -m src.main
```

Locally pass `"proxyConfiguration": {"useApifyProxy": false}` to go direct (e.g. from a
residential machine). On the platform, keep the `RESIDENTIAL` default.

### Deploy

```bash
npm i -g apify-cli
apify login
apify push
```

### Roadmap — Path B (premium tier)

Add a `revealNativeEmail` flag that performs YouTube's native business-email reveal:
requires a pool of logged-in Google accounts + a CAPTCHA solver (2captcha/CapSolver) +
residential IP. This is the 60–80%-hit-rate tier that commands ~$0.10–0.12/email. The
event (`native-email-revealed`) and account-pool plumbing are not in this build.

Then reuse the discover→enrich→email engine for Instagram and TikTok creators to build a
multi-platform creator-contact actor family.

# Actor input Schema

## `searchQueries` (type: `array`):

Discover creators by niche, e.g. "personal finance", "home barista". One search per item.

## `channelUrls` (type: `array`):

Enrich a known list directly. Accepts https://youtube.com/@handle or /channel/ID.

## `maxChannelsPerQuery` (type: `integer`):

How many channels to take from each search keyword (1-50).

## `minSubscribers` (type: `integer`):

Drop channels below this size (0 = no filter). Quality filter for lead lists.

## `country` (type: `string`):

Keep only channels whose About-page country matches, e.g. "United States". Pair with a same-country residential proxy.

## `scrapeEmails` (type: `boolean`):

Follow each creator's linked website / Linktree and recover a contact email (best-effort, no login).

## `concurrency` (type: `integer`):

Number of channels processed in parallel (1-20).

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

Residential proxy strongly recommended; match the group country to the Country filter.

## Actor input object example

```json
{
  "searchQueries": [
    "home barista coffee",
    "indie game developer"
  ],
  "maxChannelsPerQuery": 10,
  "minSubscribers": 0,
  "scrapeEmails": true,
  "concurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# 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 = {
    "searchQueries": [
        "personal finance youtuber"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ritaya/youtube-creator-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 = { "searchQueries": ["personal finance youtuber"] }

# Run the Actor and wait for it to finish
run = client.actor("ritaya/youtube-creator-finder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "personal finance youtuber"
  ]
}' |
apify call ritaya/youtube-creator-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ritaya/youtube-creator-finder",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ptmwhkQrBD2cu7P4U/builds/FC9goZnCCLIdPyXf0/openapi.json