Website Contact Finder — Every Email Verified

Give it company websites (or domains from a Google Maps export) and get contact emails, phones and social profiles — with every email verified against live DNS before it reaches your dataset. No stale database rows.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
site	Site
companyName	Company Name
email	Email
emailStatus	Email Status
emailReason	Email Reason
isRoleAccount	Is Role Account
phones	Phones
linkedin	Linkedin
foundOnPage	Found On Page

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "domains": [
    "apify.com"
  ],
  "startUrls": [],
  "maxPagesPerSite": 5,
  "maxLeads": 500,
  "includeSitesWithoutEmails": true
}

Sample output

[
{
  "site": "example",
  "companyName": "Example companyName",
  "email": "name@example.com",
  "emailStatus": "name@example.com",
  "emailReason": "name@example.com",
  "isRoleAccount": 1284,
  "phones": "example",
  "linkedin": "https://example.com/item/1",
  "foundOnPage": 42
}
]

Typical uses

• Google Maps → outreach pipeline: Maps scraper → this Actor → your CRM, fully on Apify.
• List cleaning at the source: instead of buying 10K stale rows and verifying them, collect 500 fresh ones already verified.
• Local lead gen agencies: one scheduled run per niche+city list, deduped, graded, CSV-ready.

Pricing

$1.60 / 1,000 results ($0.0016 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Email Verifier
• Lead List Deduplicator
• Website Contact Finder

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Lead Finder — Named Contacts & Verified Emails declares all 14 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Lead Finder include site, companyName, email, emailStatus, emailReason and isRoleAccount.
• Lead Finder needs no API key, login or account of any kind before its first run.
• Every one of Lead Finder's 7 inputs is optional, so it runs with no configuration at all.
• Lead Finder documents email as: Email address, as published by the source.
• Every number published about Lead Finder is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Lead Finder is filed under lead generation and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• Lead Finder reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.