# Company Email Finder: People, Titles & Email Pattern (`scrapemint/company-email-finder`) Actor

Find a company's people and emails from its own website: names and titles from team pages, every published email, the company's email pattern (first.last@, flast@...), an email for each person, the mail provider and decision-maker flags. Or look up a person by name + domain. $0.004 per contact.

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

## Pricing

$4.00 / 1,000 contacts

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

## Company Email Finder: People, Titles & Email Pattern

Give it company websites. It reads each company's own site and returns:

- **The people** on its team, about and leadership pages: **name, job title**, a **decision-maker** flag, and LinkedIn when the site links it
- **Every email published** on the site, marked personal or generic (info@, sales@, press@...)
- **The company's email pattern** (first.last@, flast@, first@...), worked out from published emails that match people on the site
- **An email for each person:** the published one when there is one; otherwise built from the company's pattern, with a **confidence level** (high, medium or low) and the reason
- **The mail provider** (Google Workspace, Microsoft 365, Mimecast, Proofpoint...) and whether the domain accepts mail at all

Or give it **"Jane Doe, acme.com"** and get that person's most likely email.

No account, no API key, no proxy. $0.004 per contact. Domain summaries are free.

### What you get

Person or lookup: `domain`, `company`, `name`, `title`, `isDecisionMaker`, `email`, `emailSource` (published on site / pattern), `confidence` (verified on site / high / medium / low), `alternatives`, `basis`, `linkedin`, `sourceUrl`, `mailProvider`

Email: `domain`, `company`, `email`, `emailType` (personal / generic), `onCompanyDomain`, `sourceUrl`, `mailProvider`

Domain summary (free): `domain`, `company`, `reachable`, `pagesRead`, `acceptsMail`, `mailProvider`, `mxHosts`, `emailPattern`, `patternEvidence`, `patternExamples`, `peopleFound`, `decisionMakersFound`, `emailsFound`, `genericEmails`

### Example input

Leadership and emails at a list of companies:

```json
{
  "domains": ["hubspot.com", "calendly.com", "sequoiacap.com"],
  "onlyDecisionMakers": true
}
```

One person's email:

```json
{
  "people": ["Roelof Botha, sequoiacap.com", "Wade Foster, zapier.com"]
}
```

### Example output

A person whose email the site publishes:

```json
{
  "type": "person",
  "domain": "sequoiacap.com",
  "name": "Liam Corrigan",
  "email": "lcorrigan@sequoiacap.com",
  "emailSource": "published on site",
  "confidence": "verified on site",
  "sourceUrl": "https://sequoiacap.com/our-team"
}
```

A lookup answered from the company's pattern:

```json
{
  "type": "lookup",
  "input": "Roelof Botha",
  "domain": "sequoiacap.com",
  "email": "rbotha@sequoiacap.com",
  "emailSource": "pattern",
  "confidence": "high",
  "basis": "Company pattern flast@ seen in 5 published email(s).",
  "mailProvider": "Mimecast"
}
```

The free summary per domain:

```json
{
  "type": "domain",
  "domain": "sequoiacap.com",
  "acceptsMail": true,
  "mailProvider": "Mimecast",
  "emailPattern": "flast@sequoiacap.com",
  "patternEvidence": 5,
  "patternExamples": ["lcorrigan@sequoiacap.com", "smaguire@sequoiacap.com", "dmeyer@sequoiacap.com"],
  "peopleFound": 11,
  "emailsFound": 13
}
```

### Uses

- **Outbound sales:** the founders and executives of your target accounts, with an email for each
- **Enrich a CRM:** fill in emails for contacts you already have by name and company
- **Recruiting and partnerships:** reach the right head of a team instead of info@
- **Account research:** who runs a company, and on what mail stack

### Pricing

- **$0.004** per contact: a person, a published email, or an answered lookup
- Domain summaries are free. Sites that don't load are free. Lookups at domains with no mail server are free.

### How confidence works

- **verified on site:** the email is published on the company's website
- **high:** built from a pattern that two or more published emails confirm
- **medium:** built from a pattern that one published email confirms
- **low:** the site published no personal emails to learn from. You get the most common B2B pattern (first.last@), plus the next four as `alternatives`.

### Notes

- Mailboxes are not checked over SMTP; datacenter servers can't reach mail servers on port 25. Use a verifier on low-confidence emails before a large send.
- Only the company's own website is read. People who aren't on the site are found through name lookups.
- Customer stories, testimonials and blog pages are skipped, and people whose title names another company are left out, so customers quoted on the site don't show up as staff.
- Sites that block bots or build their team page only in the browser can return few people. The free domain summary tells you how many pages were read.
- Respect the anti-spam and privacy laws that apply to you (CAN-SPAM, GDPR, CASL) when you contact anyone.

# Actor input Schema

## `domains` (type: `array`):

Domains or URLs, e.g. hubspot.com, https://www.calendly.com. Each returns the people on its team/about pages with titles and emails, and every email published on the site.

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

One per line: first and last name, then the company domain, e.g. "Jane Doe, acme.com". Returns that person's most likely email, with confidence.

## `onlyDecisionMakers` (type: `boolean`):

Keep only founders, C-level, presidents, VPs, heads of, directors, partners and owners. Published generic emails (info@, sales@...) are left out too.

## `includeGenericEmails` (type: `boolean`):

Also return role inboxes found on the site (info@, sales@, press@, support@...).

## `maxPagesPerDomain` (type: `integer`):

How many pages to read per site (homepage, team, about, leadership, contact...). More pages find more people on large sites.

## `maxResultsPerDomain` (type: `integer`):

Stop after this many people and emails per site. Decision-makers come first.

## Actor input object example

```json
{
  "domains": [
    "hubspot.com"
  ],
  "people": [],
  "onlyDecisionMakers": false,
  "includeGenericEmails": true,
  "maxPagesPerDomain": 8,
  "maxResultsPerDomain": 100
}
```

# Actor output Schema

## `rows` (type: `string`):

People with title and email (published or pattern-based, with confidence), published emails, name lookups and domain summaries.

## `summary` (type: `string`):

Per domain: rows, people, emails and the detected pattern.

# 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 = {
    "domains": [
        "hubspot.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/company-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 = { "domains": ["hubspot.com"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/company-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 '{
  "domains": [
    "hubspot.com"
  ]
}' |
apify call scrapemint/company-email-finder --silent --output-dataset

```

## MCP server setup

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