Work Email Finder by Name & Domain — Pay per Found

$8 per 1,000 names that produce candidates. A dry lookup is a free row with an explanation.

Turn a person's name + company site domain into ranked work email candidates, with the evidence for each spelled out. An optional check of the best candidate is billed as its own event, only when the check answered.

Why this one

1. You pay for found people, not attempts. A charge fires only when a lookup produced candidates, after the row is in your dataset.
2. Evidence, not a verdict dressed up. Every candidate carries its own validity flag (valid only when confirmed, unknown otherwise) and the receiving mail gateway, so you can judge catch-all domains yourself.
3. The check is a choice. verifyTopCandidate: true checks the best candidate against its mail domain and our address records and stamps the verdict (valid / invalid / catch-all / unknown).

Who is this for

• Outbound teams turning "name + company" lists into addresses with known risk.
• CRM hygiene: re-find addresses for contacts who changed employers.
• Teams that will not burn sender reputation on guesses.

Input

Structured:

{
  "lookups": [
    { "domain": "microsoft.com", "full_name": "Satya Nadella" },
    { "domain": "acme.com", "first_name": "Jane", "last_name": "Smith" }
  ],
  "verifyTopCandidate": false
}

Or a CSV (paste rows or link a file) with a domain column (domain, company_domain or website) and a name column (full_name, or first_name + last_name). Up to 1,000 lookups per run.

What you get

Group	Fields
Best candidate	email, email_validity
Every candidate	ranked candidates — addresses on the domain you gave first, role mailboxes such as info@ or no-reply@ left out — each with validity and the receiving mail gateway
Count	candidate_count
Check (opt-in)	verification.status, verification.domain_catchall, verification.gateway
Meta	_status, _input, _error on refused rows

{
  "_status": "found",
  "_input": { "domain": "acme.example", "name": "Jane Smith" },
  "email": "jane.smith@acme.example",
  "email_validity": "valid",
  "candidate_count": 3,
  "candidates": [
    { "email": "jane.smith@acme.example", "validity": "valid", "gateway": "mx.acme.example" },
    { "email": "jsmith@acme.example", "validity": "unknown", "gateway": "mx.acme.example" }
  ],
  "verification": { "status": "valid", "domain_catchall": false, "gateway": "mx.acme.example" }
}

(made-up addresses; verification appears when verifyTopCandidate is on and the check answered)

The Output tab has two views: Overview and All candidates.

Pricing

Event	Price	When
Email candidates found	$0.008	ranked candidates delivered
Top candidate checked	$0.006	the check answered
Nothing found / invalid row	$0	always free
The same person twice in one run	$0	looked up once, charged once

Your free $5 Apify credit is about 200 found people.

FAQ

What about catch-all domains? The verdict says so; a catch-all valid is marked as such, not sold as a confirmed inbox.

A name was not found. Do I pay? No. Your bill equals your found count.

I have the profile URL, not the name. Use LinkedIn Email Finder: it returns the addresses on record rather than candidates.

Use Work Email Finder by Name & Domain with AI agents and MCP

This Actor works as a tool for AI agents. Add it to Claude, ChatGPT, Cursor or any other MCP client through the Apify MCP server:

https://mcp.apify.com?tools=b2bsearch/work-email-finder

• Fast enough for a tool call. A small request finishes in seconds, so the agent gets its answer inside one call.
• The agent pays only for results. Prices are per result (see the pricing section above) and every miss is a free row. Cap what one call may spend with maxTotalChargeUsd.
• Rows explain themselves. Each row has a _status; a row that is not a result says why in _error, so the agent can decide what to do next without guessing.

Input an agent can send as is:

{
  "lookups": [
    {
      "domain": "microsoft.com",
      "full_name": "Satya Nadella"
    }
  ]
}

The same Actor is available as a tool in LangChain, CrewAI and the OpenAI Agents SDK, and as a step in n8n, Make and Zapier through the Apify integrations.

No names yet? B2B Leads Finder starts from filters — job title, seniority, country, industry, company size — and returns people with an email on record, from $1.50 per 1,000 leads.

Which actor in this family?

One database, ten doors. Misses are free on every one of them.

Actor	Input → output
Profile Lookup	profile URL → full career profile
Reverse Email Lookup	email → person, profile URL and employer
Name to Profile	name + company domain → profile
Social Handle Lookup	GitHub, X/Twitter or Facebook handle → profile
Bulk People Enrichment	CSV of emails, URLs, handles or names → profiles
LinkedIn Email Finder	profile URL → email addresses on record
Work Email Finder (this one)	name + company domain → work email candidates
Company Employees	company domain → current staff
People Database Search	filters → people
B2B Leads Finder	filters → leads with a work or personal email, from $1.50/1k
Company Database Search	filters → companies

Free Apify plan

Free accounts get the same rows as paid ones, with three limits. A run delivers at most 100 results; an account gets 500 dataset rows per calendar month on this Actor, found rows and misses alike; and a row that finds nothing carries only its status. Previews and counts, where this Actor offers them, stay free and outside the monthly allowance. When a limit stops a run, the status line and the last dataset row say which limit it was, what is left and when it resets. Any paid Apify plan removes all of this: Starter is $19/month and includes $19 of usage.

Feedback and reviews

How did it go? A rating on this Actor's Reviews page tells the next buyer what to expect; we read every word, good or bad. Got a wrong or stale row? Open the Issues tab with the run ID. Issues are public, so leave out emails, phones and names; the run ID is enough for us to find the row. We check every report, fix what is ours to fix and answer in the thread.

Disclaimer

This Actor is an independent product. It is not affiliated with, endorsed by or sponsored by LinkedIn. It does not access, crawl or scrape any of them at run time: answers come from our own database of publicly available professional data, and the network names only describe the kind of data it covers. To have a person's data removed, open an issue on this Actor with only the profile link — nothing else is needed, and it is removed from every listing.