# Decision-Maker Public Email Finder (`fetch_cat/decision-maker-email-finder`) Actor

Find publicly posted decision-maker email addresses on company websites with source-page evidence.

- **URL**: https://apify.com/fetch\_cat/decision-maker-email-finder.md
- **Developed by:** [Hanna Nosova](https://apify.com/fetch_cat) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.53 / 1,000 decision-maker email results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Decision-Maker Public Email Finder

This decision maker email finder finds publicly posted, person-bound decision-maker emails on company websites. Each result includes the exact source page so your team can review the context before outreach or CRM import.

Use it as a company decision maker finder or a public business email finder by domain when you need a small, auditable list of leadership contacts from domains you are permitted to research. It never guesses email patterns or turns generic inboxes into named contacts.

### Who is it for

- Sales and account teams researching named leaders at target companies.
- Recruiters looking for publicly listed department contacts.
- Researchers building source-backed company contact lists.
- Operations teams that need provenance before importing data into a CRM.

### Input recipe

Start with one public company domain and a narrow role category:

```json
{
  "domains": ["fsf.org"],
  "decisionMakerCategory": "executive",
  "maxLeadsPerDomain": 3,
  "maxPagesPerDomain": 12
}
```

Use a root domain or public company URL. Duplicate domains are removed, and malformed local addresses are skipped.

### What you get

| Field | Meaning |
|---|---|
| `fullName`, `firstName`, `lastName` | Name directly associated with the email on the public page |
| `email` | Publicly visible email address |
| `title`, `department`, `matchedRole` | Public title and selected role-category match |
| `companyName`, `companyDomain` | Company-page and requested-domain context |
| `sourceUrl`, `sourceType` | Exact evidence page and provenance type |
| `emailEvidence`, `identityEvidence` | Public email presentation and identity association labels |
| `scrapedAt` | ISO collection timestamp |

### Output example

```json
{
  "fullName": "François Daoust",
  "firstName": "François",
  "lastName": "Daoust",
  "email": "fd@w3.org",
  "title": "Director, Project & Process; Senior Principal Media & Gaming Specialist",
  "department": "director",
  "companyName": "W3C",
  "companyDomain": "w3.org",
  "sourceUrl": "https://www.w3.org/staff/",
  "sourceType": "public_website",
  "emailEvidence": "mailto",
  "identityEvidence": "same_page_context",
  "matchedRole": true,
  "scrapedAt": "2026-08-30T22:55:27.496Z"
}
```

### Input settings

| Input | Description |
|---|---|
| `domains` | One or more public company domains or URLs, up to 25 |
| `decisionMakerCategory` | `executive`, `director`, or `manager` |
| `maxLeadsPerDomain` | Accepted contacts per domain, from 1 to 50 |
| `maxPagesPerDomain` | Content pages to inspect per domain, from 1 to 20; bounded homepage, robots and sitemap discovery may add requests |

### Role categories

**Executive** finds founders, owners, presidents, and C-level titles.

**Director** finds directors, heads of department, VPs, and similar leaders.

**Manager** finds managers, leads, and principals when a page makes the title and email association clear.

### Input recipes

#### Executive contacts

```json
{"domains":["fsf.org"],"decisionMakerCategory":"executive","maxLeadsPerDomain":1,"maxPagesPerDomain":12}
```

#### Department leaders

```json
{"domains":["fsf.org","eff.org"],"decisionMakerCategory":"director","maxLeadsPerDomain":3,"maxPagesPerDomain":10}
```

Use only public company sites you are authorized to research.

### Pricing and limits

Each valid run has a small one-time start fee, then you pay for returned public decision-maker email results. View current plan-specific rates on the [Actor Pricing tab](https://apify.com/fetch_cat/decision-maker-email-finder/pricing).

No result charge applies when a domain has no public, person-bound email matching the requested role. A run accepts up to 25 domains, 20 pages per domain, and 50 results per domain.

### Source evidence

Every result keeps `sourceUrl`, `emailEvidence`, and `identityEvidence`. Use these fields to review whether a company page visibly presented the person, title, and email together.

### Limits

A company may publish no named email, publish only a generic inbox, or have no title that matches the selected category. Those cases can truthfully return fewer or no results.

This Actor reads public HTML and visible contact evidence. Sites that require JavaScript rendering or block anonymous requests may have incomplete coverage. A partial run preserves qualified results and reports incomplete work in the default key-value store's `RUN_SUMMARY`; a wholly blocked run with no results fails.

This Actor does not verify mailbox deliverability, infer addresses, access login-only pages, or return home addresses.

### API usage

#### Node.js

```js
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/decision-maker-email-finder').call({
  domains: ['fsf.org'], decisionMakerCategory: 'executive', maxLeadsPerDomain: 3, maxPagesPerDomain: 12,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
from apify_client import ApifyClient
client = ApifyClient(token="YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/decision-maker-email-finder").call(run_input={
    "domains": ["fsf.org"], "decisionMakerCategory": "executive",
    "maxLeadsPerDomain": 3, "maxPagesPerDomain": 12,
})
print(list(client.dataset(run["defaultDatasetId"]).iterate_items()))
```

#### cURL

```bash
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~decision-maker-email-finder/runs?token=YOUR_APIFY_TOKEN' \
  -H 'content-type: application/json' \
  -d '{"domains":["fsf.org"],"decisionMakerCategory":"executive","maxLeadsPerDomain":3,"maxPagesPerDomain":12}'
```

### MCP and AI agents

Add this Actor to Claude Code through Apify MCP:

```bash
claude mcp add apify -- npx -y @apify/mcp-server --tools fetch_cat/decision-maker-email-finder
```

For a JSON MCP client configuration:

```json
{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/mcp-server", "--tools", "fetch_cat/decision-maker-email-finder"]
    }
  }
}
```

Open [Apify MCP](https://mcp.apify.com?tools=fetch_cat/decision-maker-email-finder) to use the configured tool.

#### Example prompts

- “Find publicly posted executive emails for fsf.org and retain the source URL for every result.”
- “Run the decision-maker email finder for this domain list, use the director category, and return only results with public evidence.”
- “Export manager contacts from these public company domains and include the title, source URL, and identity evidence.”

### Workflow tips

Start with one domain and a low lead limit. Filter downstream records by `matchedRole`, then retain `sourceUrl` in your CRM for auditability.

Run separate batches for executive, director, and manager targeting rather than mixing role categories in a single request.

### FAQ

#### How can I find publicly listed decision-maker emails for a company domain?

Enter one or more company domains, choose an executive, director, or manager category, and run the Actor. Each exported email includes the public source URL used as evidence.

#### How can I export public company-contact emails with source URLs?

Run a domain batch and export the dataset as JSON, CSV, Excel, or another Apify-supported format. Keep the `sourceUrl` column to retain public provenance for every contact.

#### Why did a company return no results?

The company may not publish named emails, may only use generic inboxes, or may not have a title matching your selected category. Empty output is an expected outcome.

#### Does it create likely email addresses?

No. It exports only emails visibly present on a public company page and never guesses address patterns.

#### Are LinkedIn URLs, phone numbers, or home addresses included?

No. Those fields are not consistently available from the same person-bound public evidence and are out of scope.

### Related Actors

- [Website Contact Finder](https://apify.com/fetch_cat/website-contact-finder)
- [Email MX Deliverability Verifier](https://apify.com/fetch_cat/email-mx-deliverability-verifier)
- [Google Maps Lead Finder](https://apify.com/fetch_cat/google-maps-lead-finder)
- [LinkedIn Company Profiles Scraper](https://apify.com/fetch_cat/linkedin-company-profiles-scraper)
- [Google Search Results Scraper](https://apify.com/fetch_cat/google-search-results-scraper)

### Support

For input or result questions, use the Actor’s Apify page. Include the domain, role category, and source URL where possible; never include private credentials.

# Actor input Schema

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

Public company domains to inspect.

## `decisionMakerCategory` (type: `string`):

Select the seniority group to match on each public company page.

## `maxLeadsPerDomain` (type: `integer`):

Bound results returned for each domain.

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

Bound public pages checked for each domain.

## Actor input object example

```json
{
  "domains": [
    "eff.org"
  ],
  "decisionMakerCategory": "executive",
  "maxLeadsPerDomain": 3,
  "maxPagesPerDomain": 7
}
```

# Actor output Schema

## `overview` (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 = {
    "domains": [
        "eff.org"
    ],
    "decisionMakerCategory": "executive",
    "maxLeadsPerDomain": 3,
    "maxPagesPerDomain": 7
};

// Run the Actor and wait for it to finish
const run = await client.actor("fetch_cat/decision-maker-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": ["eff.org"],
    "decisionMakerCategory": "executive",
    "maxLeadsPerDomain": 3,
    "maxPagesPerDomain": 7,
}

# Run the Actor and wait for it to finish
run = client.actor("fetch_cat/decision-maker-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": [
    "eff.org"
  ],
  "decisionMakerCategory": "executive",
  "maxLeadsPerDomain": 3,
  "maxPagesPerDomain": 7
}' |
apify call fetch_cat/decision-maker-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/decision-maker-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/8zAxNmb4D3mhjHOb9/builds/f4IxiN9J5NY9tOBBY/openapi.json