Lead Finder — Named Contacts & Verified Emails
Crawl company websites for leads: named people with job titles, verified emails, phones and socials. Works out each company's email convention and labels every address by how it was obtained - found on the site, inferred, or constructed. Guesses are never presented as findings.
Lead Finder — Named Contacts & Verified Emails returns 14 documented output fields, including site, companyName, email, emailStatus and emailReason. Every field carries a declared type, a written description and an example value. 54 runs are recorded on Apify.
Run it on ApifyPay per result · no subscription
- 14
- Output fields
- 7
- Inputs
- 54
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| site | stringnull | Site as recorded for this row. | example.com |
| companyName | stringnull | Registered company name. | <companyName> |
| stringnull | Email address, as published by the source. | hello@example.com | |
| emailStatus | stringnull | Verification verdict for this address. | <emailStatus> |
| emailReason | stringnull | Why the address carries its verdict. | <emailReason> |
| isRoleAccount | booleannull | Whether the address is a shared role mailbox such as info@ or sales@. | true |
| phones | stringnull | Phone numbers found for this record. | <phones> |
| stringnull | LinkedIn profile or company URL. | <linkedin> | |
| foundOnPage | stringnull | Page number where this record was found. | <foundOnPage> |
| personName | stringnull | Person Name as recorded for this row. | <personName> |
| jobTitle | stringnull | Job title as posted. | <jobTitle> |
| personProfileUrl | stringnull | Person Profile Url as recorded for this row. | <personProfileUrl> |
| emailSource | stringnull | Where the address was found. | <emailSource> |
| emailPattern | stringnull | The address pattern the company appears to use. | <emailPattern> |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"site": "example.com",
"companyName": "<companyName>",
"email": "hello@example.com",
"emailStatus": "<emailStatus>",
"emailReason": "<emailReason>",
"isRoleAccount": true,
"phones": "<phones>",
"linkedin": "<linkedin>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| domains | arrayoptional | Company domains to scan, one per line (with or without https://). Invalid entries are reported and skipped, never silently dropped. |
| startUrls | arrayoptional | Full page URLs to start from instead of (or in addition to) the domains list. |
| maxPagesPerSite | integeroptional | Homepage plus up to this many contact-like pages (contact, about, team, impressum...). 5 finds nearly everything; raise it for very large sites. |
| maxLeads | integeroptional | Hard limit on output rows. Strictly enforced — you will never be charged for more than this. |
| includeSitesWithoutEmails | booleanoptional | On: sites with no published email still get one row saying so (with phones/socials if found) — you always know every site was actually scanned. Off: only rows with an email. |
| findPeople | booleanoptional | Extract people (name + role) from team/about pages, and work out the company's email convention from any address that belongs to one of them. A named contact with a title is worth far more than a generic info@ address. |
| guessMissingEmails | booleanoptional | For a person found without a published address, build one from the company's convention. These are clearly labelled (emailSource: pattern_inferred / guessed) and are NEVER presented as found. Off by default — a constructed address is a hypothesis, not a lead. |
04 — run
Run Lead Finder on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
14 of 14 fields described
- What does Lead Finder — Named Contacts & Verified Emails return?
- It returns 14 documented output fields: site, companyName, email, emailStatus, emailReason, isRoleAccount, phones, linkedin, foundOnPage, personName, jobTitle and personProfileUrl. Each field declares its type, a description of what it holds, and an example value. The remaining 2 are listed in the output schema below.
- What input does Lead Finder — Named Contacts & Verified Emails take?
- All 7 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does Lead Finder — Named Contacts & Verified Emails need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Lead Finder — Named Contacts & Verified Emails?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.