# Executive Email Finder - Work Emails by Company Domain (`b2bdata/executive-email-finder-by-domain`) Actor

Domain in, CEO, CFO, VP and Director work emails out. No login, no cookies, no LinkedIn account or URLs needed: only addresses on that domain, no guesses. Pay per contact, per-run spend cap. JSON/CSV, HubSpot, Clay, n8n, Make, Zapier. Free plan: 100 results per run.

- **URL**: https://apify.com/b2bdata/executive-email-finder-by-domain.md
- **Developed by:** [Open Enrich](https://apify.com/b2bdata) (community)
- **Categories:** Lead generation, Automation, Marketing
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.30 / 1,000 executive contacts

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Executive Email Finder - Work Emails by Company Domain

Domain in, executives and their work emails out, in one call. Type one company domain, pick the levels you want, and get C-suite, VP and Director contacts with a work email that sits on that exact domain. No LinkedIn URL to collect first, no second tool to find the email, no guessed patterns, no personal addresses.

**Domain to executive + email in one call | Domain-matched work emails | C-suite, VP, Director | Up to 50 contacts per domain | JSON/CSV export**

> **No login, no cookies, no LinkedIn account.** You send one company domain; nothing else is needed from you.
>
> **Strict by design.** A row is written only when a work email is on record AND it ends in your domain (or a subdomain of it). No match, no row, no charge. Not affiliated with LinkedIn.

[See all 10 actors by b2bdata](https://apify.com/b2bdata)

***

### 💳 Pricing and plans

Pay per result, see the Pricing tab. Free Apify plan: up to 100 results per run, as many runs as your Apify credit covers. Paid plans have no per-run limit. Normal Apify platform usage applies.

#### What do I pay, and how many contacts do I get?

You pay per delivered contact, nothing else from us: **$3.096 per 1,000 contacts** on a free Apify account, less on paid Apify plans.

An Apify plan is prepaid credit, not an extra fee. A $999 plan means you pay $999 and receive $999 of credit to spend on any Actors. This Actor then uses that credit at your plan's price. Example: with the $999 plan, 1,000 contacts use $2.30 of your credit, leaving $996.70.

| Apify plan | You pay Apify | Credit you receive | Price per 1,000 contacts | Contacts the credit covers |
|---|---|---|---|---|
| Free | $0 | $5 | $3.096 | about 1,600 |
| Starter | $19 / month | $19 | $2.796 | about 6,800 |
| Scale | $199 / month | $199 | $2.596 | about 76,600 |
| Business | $999 / month | $999 | $2.296 | about 435,000 |

You do not need a paid plan. A bigger plan only lowers the price per contact (about 26% less on Business). When your credit is used up you keep paying per contact at the same price. Counts are approximate: Apify platform usage also comes from the credit and is a fraction of a cent per contact. Free Apify plans get up to 100 results per run.

A result is one delivered row. Executives without a matching work email never become rows, so they are not charged.

#### Success-only billing

You pay for delivered rows only. A failed lookup, an empty search or a notice row is free: failed lookups are free. Each delivered contact is one `executive` event, charged right after the row is saved. Higher Apify plans pay less per result: Bronze 5% off, Silver 10% off, Gold and above 15% off. Exact numbers are on the Pricing tab.

#### Add-ons (charged extra)

Add-ons are opt-in inputs, off by default, each charged as its own event and only when it returns data for that row. The primary event is the only charge on a default run.

#### Lead score and `minLeadScore`

Every row gets a `leadScore` from 0 to 100, built only from signals that are really on the row: email domain matching the input domain, seniority match, and a domain-matched work email being present. The formula is written out in AGENTS.md. Set `minLeadScore` (default 0) and rows below it are not pushed and not charged.

#### Compatible output

Set `outputFormat` to `compatible` to get common LinkedIn scraper field names instead of ours, so existing pipelines keep working. The default is `default`, unchanged. The mapping table is in AGENTS.md.

***

### ⚖️ This vs. the alternatives

| | **This actor** | LinkedIn URL scrapers | Email-pattern guessers | Contact-database subscriptions |
|---|---|---|---|---|
| You start with | **One company domain** | A profile URL per person | A name + domain | Seat login and filters |
| Finds who the executives are | **Yes, by level** | No, you supply the people | No, you supply the name | Filters |
| Returns the email in the same call | **Yes** | Varies by tool | Yes (guessed) | Database record |
| Email must match your domain | **Yes, enforced** | Varies | By construction | Varies |
| Personal emails returned | **Never** | Sometimes | Never | Sometimes |
| Rows with no email | **Never written** | Written anyway | Written anyway | Written anyway |
| Email on your domain | **Always, or no row** | Varies | Sometimes | Sometimes |
| Cost per result | **Pay per result, see Pricing tab** | Per profile | Credit-based | Per-seat plan |

Every email returned ends in the domain you asked for. We also guarantee the address belongs to the domain you asked for and to a person with an executive title there.

***

### ⚡ Why this actor?

- **One domain, three levels.** Ask for `c_suite`, `vp`, `director` or any mix in a single run.
- **Skips people who cannot match.** Roster rows with no work email on record are dropped before any lookup, so you do not wait on dead ends.
- **Over-fetches for you.** It looks at about three candidates per contact you want (up to 50 rows), because many executives have no matching email.
- **Spam profiles are filtered.** Low-signal rows, profiles with under 10 connections, and assistant, office-of, executive-operations and chief-of-staff titles are skipped.
- **Retries built in.** Lookups retry up to 3 times with backoff on rate limits and server errors. A failed profile is counted and the run continues.

***

### 🎯 Use cases

- **Account-based sales.** Get the VP of Sales and the CRO at a target account from its domain.
- **Buying-committee mapping.** Pull C-suite, VPs and Directors for one account, then rank by title.
- **Partnership outreach.** Find the Director who owns partnerships at a target company.
- **Recruiter and agency prospecting.** Reach the VP of Engineering or Head of People at companies that are growing.
- **CRM enrichment.** Fill missing senior contacts on accounts you already own.
- **Founders only?** Use [ceo-founder-email-finder-by-domain](https://apify.com/b2bdata/ceo-founder-email-finder-by-domain) for CEO, founder, President and Chair.

***

### 🔗 Pipeline guide: from keyword to contact

This actor is step 3 (decision-makers at a domain). Chain four b2bdata actors and you go from a keyword to a contact:

```
  keyword: "fintech", countries: "uk, de"
        |
        v
 [1] linkedin-company-search        -> company page URL, name
        |
        v
 [2] company-firmographics-by-domain  -> company domain + firmographics
        |
        v
 [3] executive-email-finder-by-domain  <-- you are here
     (or ceo-founder-email-finder-by-domain for CEO / founder)
        |            -> name, title, seniority, work email
        v
 [4] email-phone-finder             -> phone for the chosen person
```

All of them are on the publisher page: [See all 10 actors by b2bdata](https://apify.com/b2bdata). Each step reads the previous step's dataset, so a Make or n8n scenario chains them without code. This actor takes one domain per run, so loop over your domain list from the scenario.

***

### 🚀 Quick start

Open the actor, type a domain, press Start. Or send JSON. Three examples:

#### 1. Everyone senior at one company

```json
{
  "domain": "openai.com"
}
```

#### 2. VPs only, capped

```json
{
  "domain": "stripe.com",
  "executiveLevels": ["vp"],
  "maxExecutives": 20
}
```

#### 3. C-suite and Directors, cheap test

```json
{
  "domain": "https://www.notion.so/",
  "executiveLevels": ["c_suite", "director"],
  "maxExecutives": 5
}
```

***

### ⚙️ Inputs

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `domain` | string | Yes | none (prefill `openai.com`) | One company domain. A URL is accepted and reduced to its host (scheme, `www.` and path are stripped). |
| `executiveLevels` | array of strings | No | `["c_suite", "vp", "director"]` | Any of `c_suite`, `vp`, `director`. An empty list means all three. Any other value is rejected. |
| `maxExecutives` | integer | No | `50` | Maximum contacts to return, 1 to 50. The run stops once this many matched rows are delivered. Values outside 1 to 50 are rejected. |

Tip: ask only for the levels you need, and keep `maxExecutives` low while testing.

***

#### Advanced inputs (API users)

These fields are hidden in the Console form and meant for API and automation use.

| Field | Type | Default | What it does |
|---|---|---|---|
| `maxChargeUsd` | number | `0` (off) | Stops the run when this run's charges reach the amount. The run ends SUCCEEDED with the rows already delivered and one free explanation row (`max_charge_reached`). The check runs after each charge, so a run can exceed the amount by one result. |
| `sourceTag` | string, up to 100 characters | empty | Copied onto every result row as `sourceTag` and into the `OUTPUT` record, so a CRM or Clay table can match results to the request that produced them. Explanation rows never carry it. |

#### Match fields

Every result row carries `matchMethod` (how the row was matched) and `confidence` (`high`, `medium` or `low`). The exact rule for this actor is written out in AGENTS.md. Confidence is derived only from evidence the actor really has; where it has none, the row says `medium` or `low` instead of guessing.

### 📤 Output

One dataset row per executive with a matching work email.

```json
{
  "inputDomain": "openai.com",
  "fullName": "Jane Doe",
  "title": "VP, Partnerships",
  "seniority": "vp",
  "country": "US",
  "location": "San Francisco",
  "linkedinUrl": "https://www.linkedin.com/in/example",
  "workEmail": "jane.doe[at]openai.com",
  "workEmailStatus": "current_company_matched",
  "emailAvailabilityFlag": true,
  "retrievedAt": "2026-10-11T08:30:00.000Z"
}
```

The sample is illustrative. Real rows carry a normal email address (shown with `[at]` here). `seniority` is `c_suite`, `vp` or `director`. `workEmailStatus` is always `current_company_matched` on a delivered row. `emailAvailabilityFlag` is the roster's own hint that a work email exists; it is a hint, not a promise.

Export as JSON, CSV, Excel, XML or HTML from the Output tab, or read the dataset over the API.

#### Run summary

Each run also writes an `OUTPUT` record to the key-value store: `candidatesFound`, `duplicatesRemoved`, `profilesEnriched`, `matchedWorkEmailRecords`, `skippedWithoutMatchedWorkEmail`, `skippedLowSignalProfile`, `failedProfileEnrichments`, the requested and effective limits, and a `status` (`completed`, `max_charge_reached` or `free_plan_limit`). Empty or unresolved domains write no dataset row; the counts are here.

#### Timestamp

Every row carries `retrievedAt` (ISO 8601). There is no `scrapedAt` field; `retrievedAt` is the same idea.

#### What is NOT returned

- ❌ Personal email addresses
- ❌ Work emails on a different company's domain
- ❌ Executives with no matching work email (no placeholder rows)
- ❌ Phone numbers (use [email-phone-finder](https://apify.com/b2bdata/email-phone-finder))
- ❌ Employees below Director level (use [linkedin-employee-search](https://apify.com/b2bdata/linkedin-employee-search))

Optional fields (`country`, `location`, `linkedinUrl`, `fullName`) come through as `null` when the record has no value.

***

### 🛡️ Reliable results

**Our data promise.** We work to keep every contact current, and we stand behind it. If a record is outdated, an email bounces or a person has moved on, open the Issues tab with your run link. We review every report and sort it out with you, case by case.

- **Retry with backoff.** Up to 3 attempts per lookup on HTTP 429 and 5xx, with a 30 second timeout per request. Client errors such as a removed profile are not retried.
- **One bad profile does not stop the run.** It is counted in `failedProfileEnrichments` and the next candidate is processed.
- **Paced lookups.** About 1.5 seconds between profile lookups, so a full 50 takes a couple of minutes or more.
- **Free plan.** Free Apify accounts get up to 100 results per run, as many runs as their Apify credit covers. Results are charged as usual. A run inspects at most 50 executives, so in practice free and paid runs return the same rows.
- **Bad input fails fast.** An invalid domain, an unknown level, or `maxExecutives` outside 1 to 50 stops the run with a plain message before any lookup.

***

### 🤖 For AI agents

This section is written for an LLM agent that calls this actor as a tool, through the Apify MCP server or the API. Humans: it doubles as a one-screen contract.

#### When to use this actor, and when to use a sister actor

- **Use `b2bdata/executive-email-finder-by-domain`** when you have ONE company domain and want C-suite, VP or Director work emails.
- [ceo-founder-email-finder-by-domain](https://apify.com/b2bdata/ceo-founder-email-finder-by-domain): same input, but CEO, founder, President, Managing Partner and Chair only.
- [company-firmographics-by-domain](https://apify.com/b2bdata/company-firmographics-by-domain): you need to confirm what the company is, or get firmographics for up to 100 domains.
- [linkedin-company-search](https://apify.com/b2bdata/linkedin-company-search): you have a company name, not a domain.
- [email-phone-finder](https://apify.com/b2bdata/email-phone-finder): you already have a person and need a phone or more contact details.
- [linkedin-people-search](https://apify.com/b2bdata/linkedin-people-search): you want people by role and keyword, with no email requirement.
- [linkedin-employee-search](https://apify.com/b2bdata/linkedin-employee-search): you want employees of a company at any level.
- [linkedin-leads-verified-work-emails](https://apify.com/b2bdata/linkedin-leads-verified-work-emails): you want a lead list built by title and seniority across companies.

#### Input contract

| Field | Type | Default | Notes |
|-------|------|---------|-------|
| `domain` | string | required | One domain or URL. Not a list. Not a company name. |
| `executiveLevels` | array of `"c_suite"`, `"vp"`, `"director"` | all three | Pass strings exactly as written, lowercase with underscore. |
| `maxExecutives` | integer 1-50 | `50` | Matched rows wanted. Out of range is rejected. |

Required: `domain` only. Send only the fields you need.

#### Output contract

Each item: `inputDomain` (string), `fullName` (string or null), `title` (string or null), `seniority` (`"c_suite"`, `"vp"`, `"director"` or `"unknown"`), `country` (string or null), `location` (string or null), `linkedinUrl` (string or null), `workEmail` (string, always on the input domain or a subdomain), `workEmailStatus` (`"current_company_matched"`), `emailAvailabilityFlag` (boolean or null), `retrievedAt` (ISO string). Nothing else is returned. Every dataset item is a real contact: there are no status rows, an empty dataset means no match. The `OUTPUT` record in the key-value store holds the counts.

#### Cost per call

You pay per row delivered, plus Apify platform usage. A domain with no matching work email costs no result charge. Free Apify plans get up to 100 results per run; paid plans have no per-run limit. Test with `maxExecutives` 5 first.

#### Idempotency and rate advice

Same input, similar run, but results can change as the underlying records change, so two runs may differ. Deduplicate on `workEmail`. One domain per run: for a list, launch a separate run for each domain from your scenario, a few at a time. Do not re-run a domain that returned an empty dataset more than once.

#### Chaining

Take `workEmail`, `fullName` and `linkedinUrl` from each row. For a phone or more detail on a person, pass the email to `email-phone-finder`. For the CEO or founder of the same domain, call `ceo-founder-email-finder-by-domain`.

#### Error cases and what to do

| Situation | What you see | What to do |
|-----------|--------------|------------|
| No executive has a matching work email | Run SUCCEEDED, empty dataset, `OUTPUT.matchedWorkEmailRecords` is 0 | Read `OUTPUT` for the reason. Try another level or the sister actor. Do not retry the same input more than once. |
| Invalid domain | Run fails with "domain must be a valid company domain." | Pass a real domain such as `openai.com`. A company name is not a domain. |
| Unknown level | Run fails with "executiveLevels contains an unsupported level." | Use only `c_suite`, `vp`, `director`. |
| `maxExecutives` out of range | Run fails with "maxExecutives must be between 1 and 50." | Use 1 to 50. |
| Free Apify plan, 100 results per run reached | Run SUCCEEDED with the first 100 results plus one free explanation row (`free_plan_limit`) | Run again for more; a paid Apify plan removes the limit. |
| Upstream busy or slow | Warnings in the log, run still finishes | Rows already delivered are kept. Retry later if the dataset is short. |

#### Minimal call

```json
{
  "domain": "openai.com",
  "executiveLevels": ["c_suite"],
  "maxExecutives": 10
}
```

***

### 🔌 Integrations: send results anywhere

Every run writes to an Apify dataset. Dataset items from Executive Email Finder by Domain carry `inputDomain`, `fullName`, `title`, `seniority`, `country`, `location`, `linkedinUrl`, `workEmail`, `workEmailStatus`, `emailAvailabilityFlag`, `retrievedAt`. Actor id for all recipes: `b2bdata/executive-email-finder-by-domain` (in API URLs, write it as `b2bdata~executive-email-finder-by-domain`). Everything below uses the public Apify API and your own Apify token. Native means an Apify integration exists; CSV and automation routes are marked as such.

#### 1. Fetch results over the API (native)

Send the token in a header, never in the URL. Latest successful run, as JSON, CSV or Excel:

`curl -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~executive-email-finder-by-domain/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED"`

Swap `format=json` for `format=csv` or `format=xlsx` (`jsonl` also works). `clean=true` drops empty items and hidden fields. Pick fields with jq:

`curl -s -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~executive-email-finder-by-domain/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED" | jq '.[] | {name, url}'`

Replace `name` and `url` with any field names from the output list above. For a specific run, use `https://api.apify.com/v2/datasets/<datasetId>/items?format=json`.

One-shot call (start a run and wait for its items, limited to 300 seconds): `POST https://api.apify.com/v2/acts/b2bdata~executive-email-finder-by-domain/run-sync-get-dataset-items?format=json&clean=true` with the Actor input as the JSON body and the same `Authorization` header. For longer runs, start the run normally and fetch the dataset afterwards.

#### 2. Webhook on run success (native)

In the Actor's Integrations tab (or via the API) add a webhook with event type `ACTOR.RUN.SUCCEEDED` and your own endpoint as the request URL. Apify sends a POST with the default payload, which contains the run under `resource`. Your endpoint reads `resource.defaultDatasetId` and calls the dataset items URL from recipe 1 with it. To send a smaller body, set a custom payload template: a JSON object whose values are Apify variables in double curly braces (`resource`, `eventType`, `userId`, `createdAt`, `eventData`), with nested values by dot, for example the run id as `resource.id` and the dataset id as `resource.defaultDatasetId`. Switch on "Interpolate variables in string fields" in Apify Console when you quote them.

#### 3. n8n (native node)

Apify node, operation "Run an Actor and get dataset" (or "Run an Actor", then "Get dataset items" from the Datasets resource). Select `b2bdata/executive-email-finder-by-domain`, paste the Actor input as JSON, and connect your Apify token as a credential. Each dataset item becomes one n8n item, so map `inputDomain`, `fullName`, `title`, `seniority`, `country`, `location`, `linkedinUrl`, `workEmail`, `workEmailStatus`, `emailAvailabilityFlag`, `retrievedAt` straight into the next node. The Apify node also has an "On new Apify event" trigger for run-finished events.

#### 4. Make (native app)

Apify app: module "Run an Actor" with `b2bdata/executive-email-finder-by-domain` (or the trigger "Watch Actor Runs" for scheduled or manual runs), then the search module "Get Dataset Items" using the run's default dataset id. Each returned bundle is one row, so map `inputDomain`, `fullName`, `title`, `seniority`, `country`, `location`, `linkedinUrl`, `workEmail`, `workEmailStatus`, `emailAvailabilityFlag`, `retrievedAt` into your destination module.

#### 5. Zapier (native app)

Apify app: trigger "Finished Actor run" (or action "Run Actor" with `b2bdata/executive-email-finder-by-domain`), then the search "Fetch dataset items" with the run's default dataset id. Map `inputDomain`, `fullName`, `title`, `seniority`, `country`, `location`, `linkedinUrl`, `workEmail`, `workEmailStatus`, `emailAvailabilityFlag`, `retrievedAt` into your destination step. Add a Looping or similar step if your Zap needs one action per item.

#### 6. Google Sheets

Apify's Store has a "Google Sheets Import & Export" Actor that you add on this Actor's Integrations tab, then choose append or replace mode and paste your spreadsheet URL. This needs a one-time Google login. Alternative with no extra Actor: Make or Zapier recipes above with their own Google Sheets module.

#### 7. Clay (HTTP API)

In Clay, create an HTTP API request with method GET, URL `https://api.apify.com/v2/acts/b2bdata~executive-email-finder-by-domain/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED`, and a header `Authorization: Bearer <your Apify token>`. Treat each returned item as a row and chain your enrichment columns after it.

#### 8. Airtable, HubSpot, Salesforce

No native Apify connector is used here. Two routes:

- CSV: download with `format=csv` (recipe 1) or from the dataset's Export button, then use the tool's own import (Airtable CSV import, HubSpot Import, Salesforce Data Import Wizard or Data Loader). Use a unique field such as the URL as the dedupe key.
- Automation: use the n8n, Make or Zapier recipe above and the CRM's module there. Their setup and field limits are theirs to define.

#### 9. Map the fields

Executive Email Finder by Domain returns `inputDomain`, `fullName`, `title`, `seniority`, `country`, `location`, `linkedinUrl`, `workEmail`, `workEmailStatus`, `emailAvailabilityFlag`, `retrievedAt`. Typical placement in a CRM (create custom properties where your CRM has no match):

| Output field type | Typical CRM placement |
|---|---|
| Person name | Contact name (first and last) |
| Job title or role | Contact job title |
| Company name | Company or account name |
| Website or domain | Company website or domain |
| Profile or page URL | Custom text field, also your dedupe key |
| Location (city, country) | Contact or company location fields |
| Email, phone (if returned) | Contact email, phone |
| Industry, size (if returned) | Company industry, employee count |
| Run date | Custom date field ("Sourced on") |

All recipes use the public Apify API; nothing is stored by the publisher.

***

### 🕐 Schedule examples

Use Apify Schedules (cron) on a saved task, one task per domain.

- **Weekly watch on a key account:** `0 6 * * 1`, domain of the account, all three levels, `maxExecutives` 20. Compare `workEmail` against last week's dataset to spot new executives.
- **Monthly refresh of a priority list:** `0 6 1 * *`, one task per domain, results sent to your CRM through a webhook.
- **Pre-campaign sweep:** the day before an outbound push, run the target domains you have not touched in 90 days.

Keep scheduled runs small. A schedule you forget is still billed.

***

### 🔗 Related actors

More from the publisher: [See all 10 actors by b2bdata](https://apify.com/b2bdata)

- [ceo-founder-email-finder-by-domain](https://apify.com/b2bdata/ceo-founder-email-finder-by-domain): CEO, founder and leadership emails by domain.
- [company-firmographics-by-domain](https://apify.com/b2bdata/company-firmographics-by-domain): firmographics for a domain.
- [linkedin-company-search](https://apify.com/b2bdata/linkedin-company-search): find company pages by name.
- [linkedin-employee-search](https://apify.com/b2bdata/linkedin-employee-search): employees of a company.
- [linkedin-person-search](https://apify.com/b2bdata/linkedin-person-search): find a named person.
- [linkedin-people-search](https://apify.com/b2bdata/linkedin-people-search): people by role and keyword.
- [linkedin-leads-verified-work-emails](https://apify.com/b2bdata/linkedin-leads-verified-work-emails): lead lists.
- [email-phone-finder](https://apify.com/b2bdata/email-phone-finder): phone and details for a person.

***

### ❓ FAQ

#### Data & coverage

**Q: How do I find a VP's email from a company domain?**
A: Put the domain in `domain`, set `executiveLevels` to `["vp"]` and press Start. Each VP with a work email on that domain becomes a row.

**Q: Why did I get fewer rows than `maxExecutives`?**
A: `maxExecutives` is the most you can get, not a promise. Many executives have no work email on record, and those are skipped. Read the `OUTPUT` record for the counts.

**Q: Why not guess first.last at the domain?**
A: Guesses bounce. This actor only returns an address that is on record for the person and ends in your domain. Every email returned ends in your domain.

**Q: What is `emailAvailabilityFlag`?**
A: A hint from the roster that a work email might exist. A delivered row always has a matched `workEmail`; the flag itself is not a guarantee about other people.

**Q: Does it return personal emails?**
A: No. Only work emails on the domain you passed or one of its subdomains.

**Q: Can I pass a list of domains?**
A: One domain per run. Start one run per domain from Make, n8n or the API.

**Q: What if the executive left the company?**
A: Titles come from records that can be out of date. Emails are returned only when they end in your domain; confirm the person's current role before a high-stakes send.

**Q: Am I charged for failed lookups?**
A: No. Failed lookups are free. You pay one `executive` event per delivered contact; empty results and notice rows cost nothing.

**Q: What are add-ons and are they on by default?**
A: Add-ons are opt-in inputs, off by default. Each is its own billed event, charged only when it returns data for that row.

**Q: What is the lead score and can I filter on it?**
A: `leadScore` is 0 to 100, built from signals really on the row. Set `minLeadScore` and lower-scoring rows are not pushed and not charged.

**Q: Can I keep my existing field names?**
A: Yes. Set `outputFormat` to `compatible` for common LinkedIn scraper field names. Default output is unchanged.

#### Legality & compliance

**Q: Is this legal?**
A: We cannot give legal advice. The contacts returned are built only from publicly available professional information, with no login to any platform. A named person with a work email is still personal data in many places, so you are responsible for a lawful basis and for honouring opt-outs. Takedown requests, legal claims and data-subject requests all go through Apify support (https://apify.com/contact).

**Q: Is the output personal data?**
A: Yes. A named person with a work email is personal data under GDPR and similar laws. If you hold it, you are the data controller.

**Q: Is it GDPR and CCPA compliant?**
A: The duties sit with you as controller: lawful basis, notices, opt-outs, deletion. The Master Terms below explain who does what.

**Q: Can I use the emails for cold outreach?**
A: Cold email is regulated differently in each country. B2B outreach is allowed in some places and needs consent in others. Follow the anti-spam and privacy rules of every country you contact, and honour opt-outs.

**Q: Do you store my results?**
A: No. We keep no copy of your result data. It lives in your Apify account.

**Q: Does it break LinkedIn's terms of service?**
A: LinkedIn is never logged into. Profile URLs in the output simply point to public pages. Checking that your use fits the laws and terms that cover you is your responsibility.

**Q: Can my account be blocked?**
A: Your Apify account can be limited if you break the Terms below. Nothing of yours is used on any third-party site.

***

### 🛟 Support

Use the **Issues** tab on this actor's Apify page for bugs, questions and feature requests. We answer within 24 hours on working days. Please include the run ID and the domain you used.

***

### 📜 Legal

**Use for B2B prospecting only. Comply with all applicable laws including GDPR, CCPA, and CAN-SPAM.**

Not affiliated with LinkedIn. The LinkedIn name belongs to its respective owner. This actor returns work contact records for executives at the company domain you provide. It does not log in, use cookies, access private pages or bypass authentication. Published on Apify by b2bdata as proprietary software.

## 📜 Master Terms of Service

**Publisher:** `b2bdata` (the "Publisher"), an independent developer publishing on the Apify platform. **Applies to:** Executive Email Finder by Domain (the "Actor"). **Version:** 1.0.

### Acceptance by use

By running the Actor, calling it through the Apify API, the Apify MCP server or any integration, or letting a schedule or an AI agent run it for you, you accept these Terms. This is acceptance by use. No signature is needed.

If you run the Actor on behalf of a company, you confirm you may bind that company. If you do not accept these Terms, do not run the Actor. Continued use after we update the Terms is acceptance of the update. Anonymous or automated use does not remove your responsibility: the Apify account that starts the run is the accountable party.

### Preamble: how the Actor is built

The Actor is a thin wrapper over an independent search index. It does not log in to anything, does not use cookies or accounts, and does not fetch pages from the source platform. We are a software vendor. We ship code that turns a query into a structured result. We do not own, host or curate the underlying data.

```
You / your agent
      |  input (query, filters)
      v
  The Actor (the Publisher's code, runs on Apify)
      |  search request
      v
  An independent search index of publicly indexed data
      |  public result rows
      v
  The Actor (normalises, deduplicates, saves to your dataset)
      |
      v
  Your Apify dataset (you control it)
```

Each party has one job. The index holds publicly indexed data. The Actor reshapes it. You decide what to search for, what to keep and what to do with it. We keep no copy of your queries or your results once the run ends, beyond what Apify itself stores in your account and what we need for billing and abuse prevention.

### 1. Nature of the service

#### 1.1 What the Actor is

A software tool that searches publicly indexed data and returns structured rows to your Apify dataset. It is a data-discovery utility, nothing more.

#### 1.2 What the Actor is not

It is not a scraper of the source platform, not an official integration, not a credit bureau, not a background-check service, not an employment or tenant screening tool, and not a source of legal, financial or compliance advice. Results are leads and pointers. They are not verified facts.

#### 1.3 The publisher's limited role

We write and maintain the code. We do not review individual runs, individual results or individual users. We do not guarantee that a result is accurate, current, complete or lawful to use for your purpose.

#### 1.4 Third-party infrastructure

The Actor depends on the Apify platform and on an independent search index. We do not control either. Their availability, rules and changes can affect the Actor at any time.

### 2. Who may use the Actor

#### 2.1 Eligibility

You must be at least 18, have the legal capacity to contract, and not be barred from using the Apify platform or from receiving services under applicable sanctions or export laws.

#### 2.2 Your representations

By running the Actor you represent that you have a lawful purpose, that you will follow the laws that apply to you and to the people whose data you handle, and that the information on your Apify account is accurate.

### 3. Permitted uses

Lawful business uses, including market research, account and lead discovery, competitive analysis, recruiting research done in line with local law, investment research, data enrichment of records you are entitled to hold, and building your own internal tools. Any use must comply with Section 4 and Section 6.

### 4. Prohibited uses

#### 4.1 Illegal activity

Any use that violates a law or regulation that applies to you, to us or to the people in the data.

#### 4.2 Harassment, stalking and personal targeting

Locating, monitoring, intimidating or pressuring a private individual.

#### 4.3 Discrimination

Using results to exclude or disadvantage people on a protected characteristic, including in hiring, lending, housing or insurance decisions.

#### 4.4 Spam and unsolicited commercial communication

Sending bulk messages in breach of anti-spam, e-privacy or telemarketing rules (for example CAN-SPAM, PECR, CASL, GDPR consent rules).

#### 4.5 Fraud and deception

Phishing, impersonation, social engineering, fake profiles or any scheme to mislead.

#### 4.6 Source platform abuse

Using the Actor to evade a block, rate limit or enforcement action by the source platform, or to build a service that competes with the source platform by copying its data wholesale.

#### 4.7 Reselling the Actor's service

Reselling or sub-licensing access to the Actor, or republishing raw output as a competing data product, without our written permission.

#### 4.8 AI training without authorization

Using raw output to train a model that identifies or profiles individuals, without a lawful basis and without checking the source platform's terms.

#### 4.9 Sensitive targeting

Building lists based on health, religion, ethnicity, political opinion, sexual orientation, union membership, immigration status, criminal history or any other special category of data.

#### 4.10 Privacy law violations

Any processing of personal data without a lawful basis, without required notices, or in breach of a data subject's rights.

### 5. Source platform terms: your responsibility

#### 5.1 Acknowledgment

The source platform named in the Addendum has its own terms. We have no contract with you about them and we do not interpret them for you.

#### 5.2 Your sole responsibility

You alone are responsible for checking whether your use of results is allowed under the source platform's terms and under the law of your jurisdiction. Running the Actor is not a statement by us that your use is allowed.

#### 5.3 Cease-and-desist compliance

If the source platform, a rights holder or a regulator sends us a valid cease-and-desist or takedown notice about specific use of the Actor, we will act on it. If we forward such a notice to you, you must stop the named use within 48 hours of receipt and confirm in writing. We may suspend your access immediately while we assess the notice.

### 6. Data protection

#### 6.1 Roles under privacy law

For the data you collect with the Actor, you are the data controller (or business, under CCPA). Apify and its infrastructure act for you as processor or service provider under their own terms. We, as the publisher of the code, do not decide the purposes or means of your processing and do not receive your result data.

#### 6.2 No data retention by the publisher

We do not retain your result data. We do not build a database from your runs. We keep only what is needed for billing, security and abuse prevention, such as run metadata and support correspondence.

#### 6.3 Your obligations as data controller

You must have a lawful basis (GDPR, UK GDPR), give required notices, honour access, deletion and objection requests, respect opt-outs and "do not sell or share" rights (CCPA/CPRA), keep records, protect the data, and delete it when you no longer need it.

#### 6.4 Sensitive data targeting

You must not use the Actor to target special-category data (see 4.9). If sensitive data appears in results, you must delete it or handle it under the stricter rules that apply.

#### 6.5 Data subject requests

If a person contacts us about data you collected, we will refer them to you and may ask you to confirm you have handled the request.

### 7. Intellectual property

#### 7.1 Actor code

The Actor, its code, schemas, documentation and branding belong to the Publisher. This is proprietary software. No licence is granted except the right to run the Actor under these Terms.

#### 7.2 Output data

We claim no ownership of the output. Rights in underlying data belong to their owners. You are responsible for how you use it.

#### 7.3 Restrictions

No reverse engineering, copying of the Actor, or removal of notices, except where the law gives you that right regardless.

#### 7.4 Feedback

If you send feedback or bug reports, we may use them freely to improve the Actor, without payment, and without crediting you.

### 8. Pricing and payment

#### 8.1 Apify platform billing

Charges are set on the Actor's Pricing tab and billed by Apify. Platform usage costs may also apply, as shown by Apify. We do not handle your payment details.

#### 8.2 Pricing changes

We may change prices. For any increase we give at least 14 days' notice through the Apify platform's change-notification process before it takes effect.

#### 8.3 No refunds for misuse

Results delivered as described are billable. Charges for runs you configured wrongly, repeated by a schedule you forgot, or started by an agent you control are your responsibility. Refund requests for platform or Actor faults go through Apify support or to us.

### 9. Service availability and changes

#### 9.1 No uptime guarantee

We give no uptime, latency, volume or coverage guarantee. Runs can return fewer results than you asked for, or none, because the underlying index changes.

#### 9.2 Service discontinuation

We may change, limit or stop the Actor at any time. We will try to give notice on the Actor page when practical.

### 10. Disclaimers

#### 10.1 "As is" service

The Actor is provided "as is" and "as available", without warranties of any kind, including merchantability, fitness for a particular purpose, accuracy and non-infringement.

#### 10.2 No representation of lawfulness

We do not represent that your intended use is lawful.

#### 10.3 No endorsement of source content

Results are not endorsed, verified or vouched for by us. Names can be wrong, profiles can be outdated and similarly named entities can be mixed up.

### 11. Limitation of liability

#### 11.1 Aggregate cap

To the maximum extent the law allows, our total liability for all claims relating to the Actor is limited to the greater of USD 100 or the fees you paid for the Actor in the 3 months before the event that gave rise to the claim.

#### 11.2 Excluded damages

We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profit, lost revenue, lost data or lost goodwill, even if advised of the possibility.

#### 11.3 Time limit

Any claim must be brought within 1 year after it arose.

### 12. Indemnification

#### 12.1 Your indemnification of the publisher

You will indemnify and hold harmless the Publisher, its owners and contractors from claims, losses and reasonable legal costs arising from your use of the Actor or its output, your breach of these Terms, or your violation of any law or third-party right.

#### 12.2 Defense

We will tell you promptly about a claim. You may control the defense, but you may not settle in a way that admits fault for us without our written consent.

#### 12.3 Scope

This applies whatever the legal theory, and survives termination.

### 13. Suspension and termination

#### 13.1 Termination by the publisher

We may suspend or end your access at any time, with or without notice, especially for a breach of Section 4 or a valid notice under 5.3.

#### 13.2 Effects of termination

Rights to run the Actor stop. Sections that by nature survive (IP, disclaimers, liability, indemnification, disputes) continue.

#### 13.3 Termination by you

Stop running the Actor and delete your schedules and integrations.

### 14. Dispute resolution

#### 14.1 Informal resolution first

Before any formal action, raise the dispute through Apify support or the Actor's issue tab on Apify, and allow 60 days for a good-faith resolution. The Issues tab is for product questions only and is not a channel for legal notices.

#### 14.2 Apify's process next

If the informal step fails, raise the matter through Apify's dispute and support channels. Your contractual relationship for payment, refunds and platform access is with Apify, under Apify's Terms of Service.

#### 14.3 No chosen court

These Terms do not select a governing law or a court. Any claim that survives 14.1 and 14.2 is subject to the law and forum that apply by default to a dispute between you and an individual software developer reached through Apify.

#### 14.4 No class actions

Claims may be brought only on an individual basis, not as a plaintiff or class member in a class, collective or representative action.

#### 14.5 Attorneys' fees

The prevailing party may recover reasonable attorneys' fees where the law allows.

### 15. Miscellaneous

#### 15.1 Entire agreement

These Terms, with the Addendum, are the whole agreement about the Actor. Apify's own terms continue to apply to the platform.

#### 15.2 Severability

If a provision is unenforceable, the rest stays in force.

#### 15.3 Assignment

You may not assign these Terms. We may assign them in a merger, sale or reorganisation.

#### 15.4 Force majeure

Neither party is liable for delay caused by events beyond reasonable control, including outages of the platform or of upstream infrastructure.

#### 15.5 Third-party beneficiaries

There are none, except that the Publisher's owners, contractors and affiliates may enforce the protections in Sections 10 to 12.

#### 15.6 Survival

Sections 5, 6, 7, 10, 11, 12 and 14 survive termination.

#### 15.7 Language

The English text controls.

#### 15.8 Publisher identification for legal process

All legal notices, takedown requests, cease-and-desist letters, regulator enquiries and data-subject requests must be directed to Apify (https://apify.com/contact), which forwards them to the Publisher. The Publisher operates on Apify under the username `b2bdata`. The Publisher's identity is held by Apify for billing and is provided to courts and authorities through valid legal process directed via Apify's official channels. We do not publish personal details on the Actor page.

### 16. Acknowledgment

By running the Actor you confirm you have read these Terms, that you understand you act as the data controller of what you collect, and that you are responsible for lawful use.

***

## 🛡️ Actor-Specific ToS Addendum: Executive Email Finder by Domain

#### A. Architectural disclosure

The actor sends your domain to a licensed professional-data service and reads back executive candidates and their contact records. It keeps a row only when a work email on record matches your domain. For this actor, the "independent index" described in the Master Terms is that service. It does not call LinkedIn, does not log in and does not use cookies.

#### B. Source platform

Profile URLs in the output point to LinkedIn. LinkedIn is not affiliated with, and has not endorsed, this actor. Your use of LinkedIn data is governed by LinkedIn's terms and by the law that applies to you (Section 5 of the Master Terms).

#### C. Output and accuracy

Titles can be out of date. Every email returned ends in your domain.

#### D. Personal contact data

Rows contain names and work emails of identifiable people. You act as the data controller of them (Section 6 of the Master Terms). Do not use the output for the prohibited uses in Section 4, in particular spam and sensitive targeting.

#### E. Limits

Up to 50 contacts per run, one domain per run. Free Apify plans get up to 100 results per run; paid plans have no per-run limit.

#### F. Feedback

Share issues for any b2bdata actor via b2bdata/supporter-feedback (free, no rewards), or use this actor's Issues tab.

#### G. Takedown

If a person or company asks that their record be removed, or a platform or regulator asks that specific use of this actor stop, send the request through Apify (https://apify.com/contact) or the actor's issue tab. Section 5.3 of the Master Terms (48 hours) applies.

# Changelog

This Actor's version history is a separate document: https://apify.com/b2bdata/executive-email-finder-by-domain/changelog.md

# Actor input Schema

## `domain` (type: `string`):

Website domain of the company, for example openai.com. A full URL such as https://www.openai.com/team?ref=x is reduced to its host. A company name like 'OpenAI' returns an input error instead of results, so use the domain.

## `executiveLevels` (type: `array`):

Seniority levels to look for: c_suite, vp, director. Values are lowercase with an underscore; 'C-Suite' or 'CEO' is rejected instead of searched, so type c_suite. Leave all three for the widest search.

## `maxExecutives` (type: `integer`):

How many executive profiles to inspect, from 1 to 50; 0 means all (50). Values above 50 are rejected with a message.

## `minLeadScore` (type: `integer`):

Rows scoring below this leadScore are not returned and not charged. 0 keeps every row. Example: 60 keeps only strong matches. A whole number from 0 to 100; values outside that range are rejected with a message.

## `outputFormat` (type: `string`):

default returns our field names. compatible keeps them and also adds the field names common LinkedIn scrapers use, so existing mappings keep working. Example: compatible adds email, jobTitle and firstName next to workEmail, title and fullName.

## `targetPersonas` (type: `array`):

Optional. Pick 1-5 roles and get one contact per role that has a reachable work email, in this order. Each role is matched on title keywords (see README). Leave empty to keep the normal executive search. Example: \["sales_leader", "finance_cfo", "it_security"]. Each returned contact is charged as one contact; roles with no match return no row and cost nothing.

## `executiveFallback` (type: `boolean`):

Used only with personas. When a role has no reachable contact, return the most senior leader with a reachable work email instead; the row's title is their real role and fellBackFrom names the role you asked for. Fallback rows are charged like any contact. Turn off to get only exact role matches.

## `maxChargeUsd` (type: `number`):

Stop when this run's charges reach this amount. The run ends SUCCEEDED with the data so far and one free explanation row (status max_charge_reached). 0 means no extra cap.

## `sourceTag` (type: `string`):

Optional label copied to every result row as sourceTag and into OUTPUT, to tell runs apart in your pipeline.

## Actor input object example

```json
{
  "domain": "openai.com",
  "executiveLevels": [
    "c_suite",
    "vp",
    "director"
  ],
  "maxExecutives": 50,
  "minLeadScore": 0,
  "outputFormat": "default",
  "targetPersonas": [],
  "executiveFallback": true,
  "maxChargeUsd": 0,
  "sourceTag": ""
}
```

# Actor output Schema

## `executiveContacts` (type: `string`):

Domain-matched executive work-email records.

# 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 = {
    "domain": "openai.com",
    "executiveLevels": [
        "c_suite",
        "vp",
        "director"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("b2bdata/executive-email-finder-by-domain").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 = {
    "domain": "openai.com",
    "executiveLevels": [
        "c_suite",
        "vp",
        "director",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("b2bdata/executive-email-finder-by-domain").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 '{
  "domain": "openai.com",
  "executiveLevels": [
    "c_suite",
    "vp",
    "director"
  ]
}' |
apify call b2bdata/executive-email-finder-by-domain --silent --output-dataset

```

## MCP server setup

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

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/zODH87ymtKU6NUZ2G/builds/S8IJ1K1FpE5HrH5YB/openapi.json