# Work Email Finder by Name & Domain — 📧 $25/1k, Pay per Found (`b2bsearch/work-email-finder`) Actor

Work email finder: find work email candidates from a name + company domain — ranked candidates with per-candidate deliverability evidence and an optional deliverability check. Works straight from a CSV. $25 per 1,000 names that produce candidates. Nothing found = nothing charged.

- **URL**: https://apify.com/b2bsearch/work-email-finder.md
- **Developed by:** [B2B Enrich Search](https://apify.com/b2bsearch) (community)
- **Categories:** Lead generation, AI, Agents
- **Stats:** 2 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $25.00 / 1,000 email candidates founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

> **$25 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:

```json
{
  "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 |

```json
{
  "_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.025 | 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](https://apify.com/b2bsearch/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:

```json
{
  "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.

### Which actor in this family?

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

| Actor | Input → output |
|---|---|
| [Profile Lookup](https://apify.com/b2bsearch/profile-lookup) | profile URL → full career profile |
| [Reverse Email Lookup](https://apify.com/b2bsearch/reverse-email-lookup) | email → person, profile URL and employer |
| [Name to Profile](https://apify.com/b2bsearch/name-to-profile) | name + company domain → profile |
| [Social Handle Lookup](https://apify.com/b2bsearch/social-handle-lookup) | GitHub, X/Twitter or Facebook handle → profile |
| [Bulk People Enrichment](https://apify.com/b2bsearch/bulk-people-enrichment) | CSV of emails, URLs, handles or names → profiles |
| [LinkedIn Email Finder](https://apify.com/b2bsearch/linkedin-email-finder) | profile URL → email addresses on record |
| **Work Email Finder** (this one) | name + company domain → work email candidates |
| [Company Employees](https://apify.com/b2bsearch/company-employees) | company domain → current staff |
| [People Database Search](https://apify.com/b2bsearch/people-database-search) | filters → people |
| [Company Database Search](https://apify.com/b2bsearch/company-database-search) | filters → companies |

### 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.

# Actor input Schema

## `lookups` (type: `array`):

One object per person: { "domain": "acme.com", "full\_name": "Jane Smith" } — or first\_name + last\_name instead of full\_name.

## `csvFile` (type: `string`):

Upload a CSV, or link to one. Needs a domain column (domain / company\_domain / website) and a name column (full\_name, or first\_name + last\_name). At most 1000 rows per run. A link to a file in your own Apify storage only works from this field — the platform grants the run access to the store it was uploaded to.

## `csv` (type: `string`):

Paste CSV rows, or link to a publicly downloadable CSV. Needs a domain column (domain / company\_domain / website) and a name column (full\_name, or first\_name + last\_name). At most 1000 rows per run. To use a file from your own Apify storage, use the upload field above instead.

## `verifyTopCandidate` (type: `boolean`):

Check the best candidate of each found person against its mail domain and our address records, and stamp the verdict (valid / invalid / catch-all / unknown) on the row. Billed separately per check.

## Actor input object example

```json
{
  "lookups": [
    {
      "domain": "microsoft.com",
      "full_name": "Satya Nadella"
    }
  ],
  "verifyTopCandidate": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "lookups": [
        {
            "domain": "microsoft.com",
            "full_name": "Satya Nadella"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("b2bsearch/work-email-finder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "lookups": [{
            "domain": "microsoft.com",
            "full_name": "Satya Nadella",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("b2bsearch/work-email-finder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "lookups": [
    {
      "domain": "microsoft.com",
      "full_name": "Satya Nadella"
    }
  ]
}' |
apify call b2bsearch/work-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,b2bsearch/work-email-finder"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FMMQhre381zsR66eM/builds/nNpjgm4E4MZZY54Hy/openapi.json