# Email Finder: Name + Company to Work Email (`tindacloud/email-finder`) Actor

- **URL**: https://apify.com/tindacloud/email-finder.md
- **Developed by:** [Seungki Min](https://apify.com/tindacloud) (community)
- **Categories:** Lead generation, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 people

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

## Email Finder: Name + Company to Work Email

You have a name and a company. You need the email. This Actor works it out.

It builds the candidates the way companies actually assign addresses (`jane.doe@`, `jdoe@`, `janedoe@` …), **reads the company's own website to learn which format they use**, and checks that the domain accepts mail at all.

### How this finds work emails

Most tools hand you ten permutations and let you sort it out. This one:

1. Looks for addresses already published on the company site (contact, about, team pages)
2. Recognises the format from them — `hello@` is ignored, `sarah.kim@` is the signal
3. Puts the matching candidate first and marks it **high confidence**
4. Confirms the domain has a live mail server, and tells you who runs it

### How to find work emails

One object per person:

```json
[{ "fullName": "Jane Doe", "domain": "acme.com" },
 { "firstName": "Jan", "lastName": "Curn", "domain": "apify.com", "title": "CEO" }]
```

| Field | What it does |
|---|---|
| `findPatternFromWebsite` | Learn the format from the company site (on by default) |
| `patterns` | Limit to specific formats |

### What the work email output looks like

```json
{
  "fullName": "john smith",
  "firstName": "john",
  "lastName": "smith",
  "company": null,
  "domain": "gymshark.com",
  "title": null,
  "email": "john.smith@gymshark.com",
  "pattern": "first.last",
  "confidence": "medium",
  "patternSource": null,
  "patternExample": null,
  "domainHasMx": true,
  "mailProvider": "Proofpoint",
  "candidates": [
    "john.smith@gymshark.com",
    "jsmith@gymshark.com"
  ],
  "checkedAt": "2026-09-21T10:50:34.774Z",
  "reason": "most common pattern; the domain accepts mail"
}
```

`confidence` is **high** when the company's own site uses that format, **medium** when it is the most common format and the domain accepts mail, **none** when the domain takes no mail at all. Every candidate tried is listed, so you can fall back if the first bounces.

### Honest note

No tool can prove a specific mailbox exists without sending to it, and outbound SMTP is blocked on this platform. This gets you the right format and a live domain; your sending tool will confirm the rest.

### Ready-made examples

Open one, change the fields, press Start — nothing to configure:

- [Find work email from name and company](https://apify.com/tindacloud/email-finder/examples/find-work-email-from-name-and-company)
- [Email pattern finder for a company](https://apify.com/tindacloud/email-finder/examples/email-pattern-finder-for-a-company)
- [Find emails for a list of sales prospects](https://apify.com/tindacloud/email-finder/examples/find-emails-for-a-list-of-sales-prospects)

### Frequently asked questions

#### Do I need an API key or a login?

No. Paste your input, press Start. There is nothing to connect and no account on the target site to create.

#### How do I export the results?

Every run produces a dataset you can download as JSON, CSV, Excel, XML or HTML, or read through the Apify API from your own code. You can also connect it to Make, Zapier or n8n.

#### Can I run this on a schedule?

Yes. Apify schedules run it every hour, day or week without you being there. Each run is independent, so a schedule gives you a fresh snapshot every time.

#### Can I call it from Python or JavaScript?

Yes — the Apify API runs any Actor and returns the dataset, and the official Python and JavaScript clients wrap it in a few lines. AI agents can call it too, through Apify's MCP server.

#### What does it cost?

You pay per result, not per hour. Filters are applied before anything is charged, so narrowing the input directly lowers the bill. Pages that cannot be read are reported in the log and never charged.

#### Is this data public?

Everything collected here is what a company domain shows to anyone without logging in. Check the target site's terms and the rules that apply to you before using the data commercially.

### Related scrapers

- [Email Verifier & List Cleaner](https://apify.com/tindacloud/email-verifier) — check a whole list before sending
- [Lead Enrichment: Domain to Full Company Record](https://apify.com/tindacloud/lead-enrichment-pipeline) — everything about the company
- [LinkedIn Company Scraper](https://apify.com/tindacloud/linkedin-company-scraper) — size, industry, HQ

# Actor input Schema

## `people` (type: `array`):

One object per person: {"fullName": "Jane Doe", "domain": "acme.com"}. You can also use firstName/lastName, and add company or title to carry them through to the output.

## `findPatternFromWebsite` (type: `boolean`):

Looks for addresses already published on the company website and follows that format. This is what turns a guess into a confident answer.

## `patterns` (type: `array`):

Leave empty to try all of them, most common first.

## `maxResults` (type: `integer`):

Total limit.

## `proxy` (type: `object`):

Used when reading company websites.

## Actor input object example

```json
{
  "people": [
    {
      "fullName": "Patrick Collison",
      "domain": "stripe.com"
    },
    {
      "firstName": "Jan",
      "lastName": "Curn",
      "domain": "apify.com"
    }
  ],
  "findPatternFromWebsite": true,
  "maxResults": 1000,
  "proxy": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All results in a table view.

# 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 = {
    "people": [
        {
            "fullName": "Patrick Collison",
            "domain": "stripe.com"
        },
        {
            "firstName": "Jan",
            "lastName": "Curn",
            "domain": "apify.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tindacloud/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 = { "people": [
        {
            "fullName": "Patrick Collison",
            "domain": "stripe.com",
        },
        {
            "firstName": "Jan",
            "lastName": "Curn",
            "domain": "apify.com",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tindacloud/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 '{
  "people": [
    {
      "fullName": "Patrick Collison",
      "domain": "stripe.com"
    },
    {
      "firstName": "Jan",
      "lastName": "Curn",
      "domain": "apify.com"
    }
  ]
}' |
apify call tindacloud/email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tindacloud/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/ElrmABhYVIlZbG56V/builds/X3ukHBIXS79ND3Bty/openapi.json