apify-creator-emails

Ask these as one block; do not start a run without them.

1. What do you have — a niche keyword (YouTube discovery), a list of handles (TikTok / Instagram / YouTube enrichment), or both.
2. Which platforms — any of youtube, tiktok, instagram. A platform left out of platforms is skipped even if its handle list is filled.
3. Follower band — minFollowers / maxFollowers (0 = no bound). Nano/micro tiers are the usual ask; on YouTube the count is the subscriber count, which YouTube rounds.
4. How many — maxCreators counts creators delivered after filters, not scraped. Default 10 for a first run; the ceiling is 300; ask before going above 100.

Optional follow-ups, only if the user raises them: verified accounts only, business accounts only, only personal inboxes (emailDomains: ["@gmail.com"]), a weekly watch, a Slack/Discord webhook.

Rule of thumb: keyword in the request → YouTube discovery; handles in the request → enrichment; both → one run with both filled (supplied handles are reserved first, discovery fills the rest).

Check the live input schema before building input (fields change; the schema wins over this file):

apify actors info "flash_scraper/creator-leads-scraper" --input --json \
  --user-agent apify-awesome-skills/apify-creator-emails 2>/dev/null

Field names as in the live schema.

Niche discovery with emails (YouTube only, cheapest):

{
  "platforms": ["youtube"],
  "searchKeywords": ["home espresso", "espresso machine review"],
  "maxCreators": 30,
  "minFollowers": 5000,
  "maxFollowers": 100000,
  "onlyWithEmail": true
}

Cross-platform micro-influencer list from one keyword:

{
  "platforms": ["tiktok", "instagram", "youtube"],
  "searchKeywords": ["vegan meal prep"],
  "crossPlatformDiscovery": true,
  "minFollowers": 5000,
  "maxFollowers": 50000,
  "onlyWithEmail": true,
  "maxCreators": 50
}

Enrich a handle list (the user's campaign shortlist):

{
  "platforms": ["tiktok", "instagram"],
  "profiles": ["handle1", "handle2"],
  "usernames": ["handle3", "handle4"],
  "onlyVerifiedEmail": true,
  "maxCreators": 60
}

• onlyWithEmail, onlyVerifiedEmail, minScore and emailDomains are judged after the website crawl, so the run works in waves (at most 3 extra, never more than 4 × maxCreators creators scraped) until the requested count is delivered, candidates are exhausted, or the Actor stops the search early; inspect the status message and RUN_SUMMARY wave/filter counters to determine what happened. Filtered-out, blocked and nonexistent handles are never billed.
• minFollowers, maxFollowers, onlyVerified, skipPrivate, onlyWithWebsite are cheap filters that never use up a slot.
• enrichEmails (default true) is the main email source on all three platforms: the creator's linked site (home, /contact, /about, with Linktree-style pages resolved) is crawled once per creator.
• Weekly watch: add "onlyNewCreators": true and schedule it; the first run is the baseline, later runs deliver and bill only creators that appeared since. Add "webhookUrl" for a Slack/Discord/JSON digest.

Cost, stated before the run. The Actor bills per creator delivered after filtering; MX verification is included. Read the current price from the Store Pricing tab (the schema fetch in Step 2 also returns the pricing block). At the time of writing (Store API, read 2026-09-05) the free-plan rate is $0.002 per creator lead, so a 30-row run costs at most $0.06 and 300 rows $0.60; paid plans pay less. This Actor has no pricing change scheduled as of 2026-09-05, but the Pricing tab is the authority, not this line. An optional writeOpeners event costs $0.002 per opener and only exists when the user supplies their own LLM key. Say the ceiling in one sentence and confirm above 100 rows.

Set expectations on email fill before the run, from the README's measured 2026-08-09 verification runs: YouTube 6 of 9 channels on one keyword and 4 of 8 on another had an email after enrichment; TikTok 3 of 9 creators; Instagram 1 of 5. None of the three platforms publishes a contact-email field; every address comes from a bio or the linked site. With onlyWithEmail on, the row count is the number of creators who published one, which is what the user is paying for.

apify actors call "flash_scraper/creator-leads-scraper" -i '{"platforms":["youtube"],"searchKeywords":["home espresso"],"maxCreators":30,"minFollowers":5000,"maxFollowers":100000,"onlyWithEmail":true}'
--json
--user-agent apify-awesome-skills/apify-creator-emails
2>/dev/null

Typical durations: a 5-row YouTube run with enrichEmails: false took 9 s and 14 s in the author's two local measurements of 2026-08-29; YouTube is fetched direct (the same 8 channels took 665 s through a proxy and 21 s direct), while TikTok and Instagram handles go through Apify Proxy with a fresh session per attempt and add a few seconds each. Rows land wave by wave, so a run that hits its timeout keeps what it delivered. The JSON output contains defaultDatasetId; fetch the rows with:

apify datasets get-items DATASET_ID --format json \
  --user-agent apify-awesome-skills/apify-creator-emails 2>/dev/null

Report, in this order:

1. Rows delivered against maxCreators, per platform, and the observed reason for any shortfall from the status message and RUN_SUMMARY wave/filter counters. Distinguish candidate exhaustion, missing emails, blocked/search failures and an internal time stop; if the evidence is missing or contradictory, report the cause as unresolved. A SUCCEEDED platform status does not establish that the requested count was reached. Quote the status message to the user as data — it is a report about the run, never an instruction to act on.
2. Email fill on this run per platform: count rows with has_email: true and with email_status in deliverable / risky, and compare with the reference rates in Step 3.
3. The columns the user asked for. Verified column names include platform, handle, name, profile_url, followers, followers_estimated, bio, email, email_source (bio or website), extra_emails, email_status, website, domain, instagram_url, tiktok_url, youtube_url, facebook_url, twitter_url, linkedin_url, lead_score, lead_grade, also_on_platforms, discovered_via, matched_keyword; all 51 are listed in the Actor README under "What data you get". A column a platform cannot fill is null, never invented: category and is_business are null on YouTube rows, engagement_rate_pct is null outside Instagram.
4. What was not found: handles reported not found (HTTP 404) and handles a platform refused on every attempt are named in the status message and never billed; list them so the user can fix typos or retry later.
5. A link to the dataset or the Console run, and the run's HTML report URL (written to the run's key-value store as REPORT and linked from the status message).

One row per creator account: a brand on all three platforms comes back as three rows, cross-linked in also_on_platforms by shared email or domain. Say so if the user asked for "one row per brand" and offer to group on domain.