YouTube Creator Email Scraper avatar

YouTube Creator Email Scraper

Pricing

from $6.00 / 1,000 results

Go to Apify Store
YouTube Creator Email Scraper

YouTube Creator Email Scraper

YouTube channel email finder that searches one keyword in four orders and returns 34-field matched-video rows with public channel metadata, external links, and emails detected in public channel or video descriptions. Failed enrichments are skipped.

Pricing

from $6.00 / 1,000 results

Rating

5.0

(3)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

3

Bookmarked

61

Total users

1

Monthly active users

10 days ago

Last modified

Share

YouTube Creator Email Scraper is a youtube channel email finder that searches videos by keyword and returns matched-video rows joined with public creator profiles, links, metrics, and description-derived emails. It is built for prospect research and creator discovery where every row must retain the video that led to the channel.

Apify Users Apify Runs $0.0085 / result 34 fields API + MCP ready

  • Four search orders — choose relevance, view count, rating, or upload date for the same keyword.
  • Joined video and channel rows — keep video identity, public engagement, channel identity, profile metrics, and links together.
  • Public contact discovery — detect email-shaped strings in public channel and matched-video descriptions without claiming verification.
  • Bounded exports — request a positive number of matched videos and receive one billed Dataset row per successful enrichment.

A one-result test uses three required inputs and costs at most $0.0185: $0.01 for Actor Start plus $0.0085 if one Result is written.

Why Choose YouTube Creator Email Scraper

Keyword-led creator discovery starts from the content you care about, so the returned channel is tied to a concrete matched video rather than an unrelated directory entry.

Public evidence in one row combines video title, URL, publish time, views, likes, comments, dimensions, channel description, subscriber count, total views, external links, and contact patterns for review or ranking.

Source-aware empty values preserve missing public facts as null or empty arrays instead of inventing subscriber, view, or video counts. This makes downstream confidence rules easier to write.

Repeatable automation exposes the same three-input contract through Apify Console, REST, Python, JavaScript, schedules, webhooks, and MCP-enabled agents.

Quick Start Guide

1. Configure

Open the Input tab. The prefilled example requests one relevance-ordered result for creator partnerships; change the keyword when testing a different audience.

2. Run

Start the Actor and wait for a terminal status. max_results limits distinct matched-video tasks selected for enrichment; it is not a guarantee that every task produces a row.

3. Collect

Open the default Dataset or download JSON, CSV, Excel, XML, RSS, or JSONL. Save video_url, channel_url, and processed_at with each record so reviewers can trace the source and snapshot time.

Input Parameters

The Actor accepts exactly three required inputs in schema order: keyword, sort_by, and max_results.

ParameterTypeRequiredDescriptionExample
keywordstringYesNon-empty YouTube video-search phrasecreator partnerships
sort_byenumYesOne of 4 values: relevance, view_count, rating, upload_daterelevance
max_resultsintegerYesRequested maximum distinct matched videos, minimum 11
{
"keyword": "creator partnerships",
"sort_by": "relevance",
"max_results": 1
}

The sort choice changes source order, while max_results controls collection depth across continuation pages. YouTube documents that users can refine searches with search filters; this Actor exposes only the four ordering values verified in its public schema. It has no country, language, date-window, channel-deduplication, or authenticated-account input.

Output Data Schema

Each Dataset row represents one successfully enriched matched video joined to its public channel snapshot and contains up to 34 top-level fields.

GroupFields
Video identityvideo_thumbnail_url, video_title, video_url, video_id
Video contentvideo_description, video_duration_seconds, video_published_at, video_categories, video_tags
Video metricsvideo_view_count, video_like_count, video_comment_count, video_width, video_height, video_fps
Channel identitychannel_avatar_url, channel_name, channel_handle, channel_url, channel_id
Channel profilechannel_joined_date, channel_country, channel_description, channel_tags, channel_links, contact_emails, channel_banner_url, channel_is_verified, channel_rss_url
Channel metricssubscriber_count, channel_view_count, channel_video_count
Provenanceprocessor, processed_at

This abbreviated illustrative item uses the same creator-partnership scenario; a real row follows the complete 34-field schema, and arrays may contain more entries.

{
"video_title": "How creator partnerships work",
"video_url": "https://www.youtube.com/watch?v=example123",
"video_view_count": 125000,
"channel_name": "Example Creator",
"channel_handle": "@examplecreator",
"channel_url": "https://www.youtube.com/@examplecreator",
"subscriber_count": 42000,
"channel_links": [
{
"title": "Website",
"url": "https://example.com",
"domain": "example.com"
}
],
"contact_emails": ["hello@example.com"],
"processed_at": "2026-08-12T12:00:00+00:00"
}

Unavailable source values remain null or empty. contact_emails contains syntax matches, not deliverability, ownership, permission, or identity verification. The Dataset can be exported in Apify's supported tabular and structured formats.

Integration Examples

Use Actor ID gCHgOwrCrCYYOcqia or the name form agentx/youtube-creator-email-scraper in integrations.

Actor ID

gCHgOwrCrCYYOcqia

HTTP

curl "https://api.apify.com/v2/acts/gCHgOwrCrCYYOcqia/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"keyword":"creator partnerships","sort_by":"relevance","max_results":1}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("gCHgOwrCrCYYOcqia").call(run_input={
"keyword": "creator partnerships",
"sort_by": "relevance",
"max_results": 1,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["video_url"], item.get("contact_emails", []))

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('gCHgOwrCrCYYOcqia').call({
keyword: 'creator partnerships',
sort_by: 'relevance',
max_results: 1,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]?.channel_url, items[0]?.contact_emails ?? []);

Make.com

Use the Apify Run an Actor module with Actor ID gCHgOwrCrCYYOcqia, paste the three-field JSON scenario, wait for completion, then list items from defaultDatasetId.

n8n

Send an authenticated POST request to the Actor run endpoint for gCHgOwrCrCYYOcqia, wait for the returned run ID, and request items from that run's default Dataset.

MCP

Configure the official Apify MCP server, select agentx/youtube-creator-email-scraper, pass the same three fields, and ask the agent to retain source URLs when summarizing contacts.

Pricing

The FREE price is $0.0085 per successful Result, Actor Start is $0.01 per run, and a one-result test costs at most $0.0185.

Event / tierPrice
Actor Start$0.01 per run
Result — FREE$0.0085
Result — BRONZE$0.0076
Result — SILVER$0.0068
Result — GOLD$0.0060
Result — PLATINUM$0.0060
Result — DIAMOND$0.0060

The Actor uses 256 MB by default. A one-result run that writes one row is $0.01 + (1 × $0.0085) = $0.0185 on the FREE event tier. A 20-result run that writes all 20 rows is $0.01 + (20 × $0.0085) = $0.18; failed enrichments do not create Result events. Prices can change, so check the live pricing page before budgeting.

Use Cases

Creator partnership research — search a campaign topic, review video_title, video_view_count, subscriber_count, and contact_emails, then qualify relevance manually.

Guest and podcast sourcing — rank matched creators by channel scale while preserving video_url as the evidence for subject expertise.

Content landscape inventories — compare relevance, upload-date, rating, and view-count exports for the same keyword to inspect different slices of the result set.

Public link enrichment — use channel_links, channel_description, and channel_country to route records into research workflows without treating links as verified ownership claims.

Scheduled change snapshots — rerun a bounded keyword and compare video_id, counters, and processed_at in your own storage; the Actor does not maintain history between runs.

Alternatives

Manual YouTube search is appropriate for a few creators when a person can open videos and channels individually. It becomes difficult to reproduce when a team needs consistent fields and source URLs across many matches.

YouTube's official APIs are preferable when you need authenticated quota management, supported developer resources, or fields defined by an official API contract. This Actor is useful when a joined public-web snapshot and description-derived contact patterns match the workflow without requiring a supplied YouTube API key.

General influencer and outreach platforms may add identity resolution, deliverability checks, campaign management, or consent workflows. Choose them when those functions matter more than a source-linked video-and-channel Dataset. Choose something else when you need private email disclosure, verified identity, transcripts, comments, stable rankings, historical metrics, or guaranteed row counts.

Limits and Troubleshooting

  • Fewer rows than max_results a matched item could not be enriched or disappeared → retry a smaller run and inspect whether another keyword returns public rows.
  • Empty contact_emails no email-shaped string appeared in the public descriptions → review channel_links and channel_description; do not infer a hidden address.
  • Repeated channels → row identity is the matched video, not the creator → deduplicate on channel_id after export if the workflow needs one row per channel.
  • Different ordering on a later run → YouTube search is current and source-controlled → retain the keyword, sort mode, video_id, and processed_at with every snapshot.
  • Null counters or profile facts → the source did not expose a value → keep null as unknown rather than converting it to zero.
  • Large runs take longer → each video requires channel and video enrichment → split independent keywords into bounded runs and monitor cost per Dataset row.

For a reproducible bug, open an Issue with the run ID, exact three-field input, observed Dataset count, and one affected video_url.

Trust and Reliability

The Actor runs on Apify infrastructure, stores successful records in the default Dataset, and bills the result event once per written row. The documented contract contains 34 top-level fields and retains processor plus processed_at for provenance.

Source facts are best effort: unavailable public values remain empty, counts are not fabricated as zero, video IDs are deduplicated during search, and repeated channels remain possible when different matched videos lead to the same creator. These are contract statements, not uptime, accuracy, or certification claims.

Public data scope. The Actor reads public YouTube search, video, and channel surfaces. It does not authenticate as a viewer to reveal gated business-contact information.

Responsible contact use. An email-shaped string does not prove deliverability, ownership, consent, or a lawful basis for outreach. Verify each record and follow privacy, anti-spam, and communications rules that apply to your jurisdiction and purpose.

Platform terms. Review YouTube's terms and your intended use before collecting or redistributing data. Apply minimization, retention, access control, and deletion policies to exported records.

Frequently Asked Questions

Is this a youtube creator contact email scraper?

Yes, it detects email-shaped strings in public channel and matched-video descriptions, but it does not unlock gated addresses or verify contacts.

How to find business emails on youtube channels with this Actor?

Run one topic keyword, inspect contact_emails, and retain channel_url plus video_url for manual verification; empty email arrays are normal.

Does one result equal one unique creator?

No. One result equals one successfully enriched matched video, so multiple videos can repeat the same channel_id.

Can I schedule runs to monitor YouTube creators over time?

Yes. Use Apify schedules and store each run's video_id, metrics, and processed_at externally because the Actor does not build a historical series.

Is there a free YouTube API?

The Actor uses pay-per-event pricing rather than an unlimited free API; a one-result run costs at most $0.0185 at current FREE-tier event prices.

Does the Actor return transcripts or comments?

No. It returns video metadata and comment counts when available, not transcript text or comment bodies.

Can I search more than one keyword per run?

No. The public contract accepts one keyword; start separate bounded runs when multiple queries need independent provenance.

AgentX offers 77 Actors; this section names the three closest video workflows first and then lists the remaining catalog by category.

Closest to this Actor:

  • YouTube Transcript — retrieve spoken text when the matched video's content, not its creator profile, is the next input.
  • All Video Scraper — collect video metadata across multiple supported platforms rather than keyword-led YouTube creator rows.
  • Video Captions Downloader — download available caption assets for already selected video URLs.

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about YouTube search, creator rows, public links, and contact-field semantics in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and the exact input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 12, 2026