Finding creators to work with is not really a search problem. Search returns channels easily. The work is everything after: whether the channel is the right size, whether it is in the right country, and whether there is any way to reach the person behind it that does not involve guessing an address.
This Actor takes a niche, or a list of channels you already have, and returns creators with their profile, subscriber count, social links and public contact email where one exists. Emails found this way are validated before they are returned, so each one arrives with a verification status and a plain-English send recommendation rather than a raw string.
That verification is built in rather than called out to, so the Actor is self-contained and depends on nothing else to run. The rules it applies are tuned for creators rather than for companies: an info@ address on a creator's own domain is a normal way for one person to be reached, and is judged differently from the same prefix at a corporate domain.
Subscriber ranges and a maximum creator count are inputs rather than filters applied afterwards, which means the size of the run and its cost are decided before it starts.
What the data says
1 in 7
mid-sized YouTube creators publish a contact email a visitor can actually read
Measured across creators in the 5,000 to 500,000 subscriber band. The rest are reachable only through a login-gated form, a social profile, or not at all. This is the number that decides how large a search has to be before an outreach list is worth building, and it is the reason this Actor returns creators with no contact details rather than hiding them.
Inputs
- searchKeywordsarray
- Niche descriptions to search. One run can cover several.
- channelUrlsarray
- Handles, URLs or UC IDs, for enriching a list of channels you already hold.
- minSubscribers / maxSubscribersinteger
- Size band. Applied during collection, not after.
- maxCreatorsinteger
- Hard ceiling on the run, and therefore on its cost.
- scanCreatorWebsitesboolean
- Follow a creator's linked site and read its contact page.
- validateEmailsboolean
- Check found addresses before returning them.
Outputs
- creators
- One row per creator: profile, subscriber count, country, social links, and contact email with its verification status and send recommendation.
- creatorsCsv
- The same data in a spreadsheet-ready shape.
Delivered as Apify dataset, CSV.
What it does not do
It does not retrieve the business email that YouTube keeps behind a login and a CAPTCHA. Only addresses a visitor could read are returned.
It does not guess or construct addresses from a name and a domain, and it does not confirm that a mailbox exists.
Creators who publish no contact route are still returned, with the contact fields empty. An empty field is a finding, not a failure, and filling it with a guess would make the whole output untrustworthy.
Search depth per keyword is capped by input, so a run is a sample of a niche rather than a census of it.
Where it is used
- Building a shortlist for a creator or influencer campaign in a specific niche and size band.
- Enriching a list of channels that a team already agreed on, to find out which are actually reachable.
- Sizing a niche before committing to it, by measuring how many creators exist in a subscriber band and how many can be contacted at all.
- Feeding qualified contacts into an outreach pipeline without a manual copy-and-paste step in the middle.
Can be composed with
- Its email addresses can be passed into Bulk Email Validator.
These are separate programs. Neither calls the other, and this one works on its own. A composition is something you or an agent wire up, not something that happens behind the scenes.
From an agent
It runs as an Apify Actor, so any MCP client can call it through Apify's hosted server at mcp.apify.com. Nothing extra was built for this. It is not loaded by default, so an agent either finds it through Apify's search tool or is given the name:
salomon-dot-labs--youtube-creator-finder
The description a model reads before deciding to call it is the same sentence that heads this page. Every input listed above is optional, so a model can start it with far less than a full configuration.
Worth knowing when you wire it up: the call returns a pointer rather than the rows. An agent gets the dataset id, the item count and the available field names, then fetches the results in a second step. That is how Apify exposes every Actor, not something particular to this one, and it means budgeting two round trips per answer.
It runs on Apify. Inputs, output schema and pricing are all on the listing, and a run can be started from the browser without writing any code.
Open on Apify