YouTube Email Finder

Find the contact email behind any YouTube channel — at scale, in a single run.

Submit one or multiple YouTube channels by handle or URL. By default the actor waits until every channel has been processed and returns the emails directly in the dataset. You can also run it fire-and-forget and collect results later with a Job ID, backed by the lead24.email platform.

---

What it does

1. You provide YouTube channel handles or URLs
2. The actor validates them and submits a job
3. It waits while the emails are found (typically well under a minute per channel)
4. Every channel is pushed to the dataset as its own row — email included

Channels that were already processed before are returned instantly from cache.

---

Input

Field	Type	Default	Description
channel_handles	array	—	One or more channel handles, with or without @. e.g. MrBeast, @PewDiePie
channel_urls	array	—	One or more channel @handle URLs. e.g. https://youtube.com/@mkbhd
job_id	string	—	Collect the results of a previous job instead of submitting channels.

Capping how long a run waits: use Apify's own Timeout in the Run options. If the run is stopped before the job finishes, the job_id is already saved in the run's OUTPUT — re-run the actor with that job_id to collect the results.

You can use channel_handles and channel_urls at the same time. Duplicates are merged.

URL format matters: use the channel's @handle URL (open the channel page and copy the address — it looks like youtube.com/@Name). URLs like youtube.com/channel/UC…, youtube.com/c/Name or video links are rejected with a clear reason in the dataset, instead of producing wrong results.

Example input:

{
  "channel_handles": ["MrBeast", "@PewDiePie"],
  "channel_urls": ["https://youtube.com/@mkbhd"]
}

Example dataset row:

{
  "channel_handle": "@MrBeast",
  "email": "contact@mrbeastbusiness.com",
  "email_found": true,
  "subscribers": 484000000,
  "is_done": true,
  "status": "complete",
  "cached": false,
  "job_id": "550e8400-e29b-41d4-a716-446655440000"
}

---

Collecting results later

If a run was stopped before the job finished (e.g. by the run Timeout you set in Apify's Run options), nothing is lost — the job keeps processing on our platform. Re-run the actor with just the Job ID from the stopped run's OUTPUT:

{
  "job_id": "550e8400-e29b-41d4-a716-446655440000"
}

The run waits until the job is complete and pushes every channel (with emails) to the dataset.

---

Result statuses

Where	Status	Meaning
dataset row	complete	Channel processed — email is filled if one exists (email_found: true)
dataset row	invalid	Input couldn't be used — see the reason field
output	running	Written as a checkpoint while waiting — contains the job_id
output	complete	All channels processed and pushed to the dataset
output	not_found	The job_id you provided does not exist

---

Tracking your job

Track the live status of any job without running the actor:

https://lead24.email/status/<your-job-id>

You'll see a real-time page showing each channel and whether its email has been found.

---

Tips

• Handles work with or without @ — MrBeast and @MrBeast are treated the same.
• Bulk submissions — add as many channels as you need in a single run; each gets its own result row.
• Cached channels are free and instant — resubmitting a known channel returns the stored email immediately.
• A channel with no public email still completes, with email: null and email_found: false.

---

About lead24.email

lead24.email is the platform powering this actor. It handles job processing, result storage, and provides a live tracking dashboard for your jobs.

---

Support

For bulk pricing or support — visit lead24.email.