Youtube Channel Email Scraper

Overview Extract verified YouTube business emails with DataOverCoffee’s premium Apify YouTube email extractor—no public-data fluff, no subscription, and pay-per-result email extraction. Submit up to 1000 channels per run, let our async email extraction workflow process in 24-48 hours, then revive the actor to collect accurate, creator-published business contacts. 1. Submit your list (1000 channels per run) Paste or upload up to 1000 YouTube channel URLs, handles (e.g. @ChannelName), or 24-character IDs. 2. Async processing The actor quickly forwards your channels to our backend, then exits. 3. Backend brewing (CAPTCHA-solving email scraper) Over 24-48 hours, DataOverCoffee's fleet of logged-in Google accounts solves CAPTCHAs and extracts each channel’s official business email. 4. Collect your results (extract YouTube emails) Restart the actor once processing completes (usually 24-48 hours). All found business emails appear instantly in your dataset—pay only for the emails we deliver. ## 📝 Inputs When submitting your input list, ensure that the 'Maximum Charged Results' or 'Maximum Results' setting is set to unlimited or to a number equal to or greater than your total number of input channels. If you set this value lower than your input count, the actor will skip processing all inputs. Always match or exceed your input size for successful processing. ## 📤 Outputs After you revive the actor, your dataset shows one row per channel with these columns: ## 💰 Pricing - $12 per 100 emails extracted (only for delivered emails). - No hidden fees—you pay per result. - Apify Free tier is limited to a maximum of 50 inputs per run. Upgrade to Apify paid to access 1000 channel input quota. ## ❓ FAQ ### Why use this actor? DataOverCoffee’s YouTube Channel Email Extractor is the only Apify actor that uses logged‑in Google accounts and automatic CAPTCHA solving to pull real, creator‑published business emails at scale. Simply bulk import up to 1000 channels, then sit back as your dataset brews—no fluff, no BS. ### Do I pay for channels without an email? No. If there’s no email, the actor simply ignore that channel. So you won't be charged. ### How do I get my results? 1. ▶️ Initial run: The actor submits your channels and exits within minutes. Check run logs on your apify console to see more details 2. 🕒 Background processing: Our backend continues extracting emails over the next 24-48 hours. 3. 🔄 Revive run: After at least 24-48 hours, restart (use Resurrect and not Re-run from start) the actor—completed results appear instantly in your default dataset. Run logs can look like this: ### Why isn’t this synchronous? YouTube limits daily email extractions per account and requires CAPTCHA solving. Our async email extraction offloads work to backend servers. Come back in 12–24 hours to retrieve results. Be sure to check the actor run logs for more info. ### Who should use this? Marketers, agencies, and sales teams needing direct creator contacts for outreach, partnerships, and lead generation—no coding needed. ### Can I test with a small list first? Yes—try 5–10 channels to see how the YouTube contact scraper works before scaling up. ### How can I optimize runs? Submit only channels with known business emails to maximize efficiency and reduce input usage. ### Actor not returning results for all inputs? Please ensure that all input URLs, channel handles, or channel IDs are valid and correctly formatted. Invalid entries will be ignored by the system and will not be processed. You can find which inputs are still pending or were ignored by viewing your run’s state file, usually located at: https://api.apify.com/v2/key-value-stores/<Store ID>/records/STATE Replace <Store ID> with your actual Store ID, which can be found under Last Run -> Storage -> Key-value store in Apify. You can also click the "view" button on STATE to see the current state. ### Still experiencing issues with the actor? If you continue to encounter problems or errors, please contact support at dataovercoffee[at]proton.me with a detailed description of the issue. Ideally with the Run ID