YouTube Email Scraper
Pricing
from $2.99 / 1,000 channel emails
YouTube Email Scraper
Collect only email addresses that channel owners publicly expose in YouTube channel descriptions or public link metadata.
Pricing
from $2.99 / 1,000 channel emails
Rating
0.0
(0)
Developer
w3crawler
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Find email addresses that are literally present in public YouTube channel descriptions or public channel-link metadata. The actor does not reveal hidden contact addresses, click contact-reveal controls, call private endpoints, or bypass access controls.
Input
| Field | Default | Description |
|---|---|---|
channelUrls | — | Public channel URLs, @handles, /channel/UC… IDs, /user/… URLs. |
searchQuery | — | Optional public YouTube channel search query. It can be combined with channelUrls. |
emailDomain | — | Optional exact domain filter, for example gmail.com. |
maxItems | 20 | Maximum channels to scan, from 1 to 100. |
enableProxyFallback | true | Try standard account-authorized Apify Proxy after direct access fails. |
maxRetries | 2 | Bounded retries per route, from 0 to 3. |
requestDelayMs | 250 | Delay between channel pages. |
requestTimeoutSecs | 60 | Public-page timeout. |
proxyConfiguration | — | Standard Apify Proxy or credential-free HTTP/SOCKS configuration. |
Output
When a public email is found, the dataset includes the primary and complete matching email list, email source, channel ID/name/handle/canonical URL, description and length, displayed and parsed subscriber/video counts, public country/joined date, avatar, public external links, input/search provenance, explicit metadata source and extraction method, and timestamp.
When no address is exposed, the actor logs and counts a NO_PUBLIC_EMAIL_FOUND event (if diagnostics are enabled) and still completes successfully when the public page itself was read. It writes no placeholder contact record.
Diagnostic details remain in logs and the OUTPUT count, not in the dataset. OUTPUT summarizes discovery, scanning, findings, failures, blocks, proxy state, and duration.
Verification
npm testnpx apify validate-schema .actor/input_schema.jsonnpx apify run --purge --input-file qa-inputs/youtube-email-scraper/local-validation.jsonnpm run validate-datasetnpx apify actors call <ACTOR_ID> --build latest --input-file qa-inputs/youtube-email-scraper/cloud-validation.json --timeout 300 --json