Decision-Maker Public Email Finder avatar

Decision-Maker Public Email Finder

Pricing

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

Go to Apify Store
Decision-Maker Public Email Finder

Decision-Maker Public Email Finder

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

Pricing

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

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

0

Monthly active users

8 days ago

Last modified

Categories

Features

Full permissions

Share

Find publicly posted, person-bound decision-maker emails on company websites. This decision maker email finder returns names, titles, company domains and exact source pages so you can review the evidence before outreach or CRM import.

Use a company domain and a role category to build a small, auditable contact list. It never guesses email patterns or turns generic inboxes into named contacts.

Quick start

  1. Open the Actor's input form.
  2. Enter a public company domain and choose the role category you need.
  3. Run the Actor, then review the results and their source pages.

This small public staff-directory example is a useful starting point:

{
"domains": ["www.w3.org"],
"decisionMakerCategory": "director",
"maxLeadsPerDomain": 3,
"maxPagesPerDomain": 7
}

Available contacts depend on what the website publishes and which pages can be inspected.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

  • Named contacts: Public emails associated with a person's name and matching title, rather than guessed addresses or generic inboxes.
  • Company context: The requested domain and the company name when available from the page.
  • Reviewable evidence: The source URL and labels describing how the email and person were associated.

Use it as a public business email finder by domain when provenance matters more than a large unverified list.

Who is it for?

  • Sales and account teams researching named leaders before importing contacts into a CRM.
  • Recruiters looking for public department contacts with a visible title and source.
  • Researchers and operations teams building contact lists that can be checked against the original company pages.

Input settings

InputWhat it controls
domainsRequired list of 1–25 public company domains or URLs. Duplicate domains are removed and invalid targets are skipped.
decisionMakerCategoryexecutive, director or manager. Omitted API input defaults to executive.
maxLeadsPerDomainAccepted contacts per domain, from 1–50. Defaults to 5 when omitted.
maxPagesPerDomainContent pages per domain, from 1–20. Defaults to 7. Bounded discovery can add requests.

The input form's example values are not API defaults. Supply your own domains in API calls. If no valid public domain remains, the run stops without starting extraction.

Role categories: executive targets founders, owners, presidents and C-level titles. director targets directors, department heads and VPs. manager targets managers, leads and principals when the page makes the title and email association clear.

For an executive search, change decisionMakerCategory to executive. Run separate batches for different role categories rather than mixing categories in one request.

Use only public company sites you are authorized to research.

Output data

Each dataset row represents one accepted, person-bound public email. Some descriptive fields can be unavailable.

Field groupWhat it tells you
fullName, firstName, lastName, emailThe person and publicly presented address.
title, department, matchedRoleThe public title, role grouping and selected-category match.
companyName, companyDomainCompany context and requested domain.
sourceUrl, sourceTypeThe exact evidence page and public-website source.
emailEvidence, identityEvidence, scrapedAtEvidence labels and collection time.

Example from a public W3C staff page:

{
"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"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A valid run has a one-time start charge after at least one safe public target is accepted. That charge can apply even when no matching contact is found.

The result event charges for accepted decision-maker email results. There is no result charge for a domain that produces no accepted contact. Public email evidence is not a deliverability guarantee, and no paid mailbox-verification service is included.

See the live Pricing tab for current rates and discounts, including any announced future changes.

Tips for best results

  • Start with one domain. Check its source pages before increasing your batch size or page limit.
  • Choose the right role category. A page listing only managers may have no executive matches.
  • Retain the evidence. Keep sourceUrl with each CRM record so your team can review the original context.
  • Treat emails as public evidence, not delivery promises. Review addresses and outreach suitability in your own workflow.

Limits and caveats

  • A company may publish no named email, only generic inboxes, or no matching title. A successfully inspected site can therefore return fewer or no contacts.
  • Coverage depends on accessible public HTML. Login-only content, JavaScript-only pages and blocked requests may prevent a complete search.
  • A partial run preserves qualified results and reports incomplete work in RUN_SUMMARY in the default key-value store. A wholly blocked or failed search with no results fails rather than proving there are no contacts.
  • It does not infer addresses, verify mailbox deliverability or return home addresses, phone numbers or LinkedIn profile URLs.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could add accepted contacts and their source URLs to a spreadsheet or CRM. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Collect public contacts from your own app or automation using fetch_cat/decision-maker-email-finder. Review and approve the Actor's requested account permissions before running it with your account.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~decision-maker-email-finder/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"domains":["www.w3.org"],"decisionMakerCategory":"director","maxLeadsPerDomain":3,"maxPagesPerDomain":7}'

Node.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: ['www.w3.org'],
decisionMakerCategory: 'director',
maxLeadsPerDomain: 3,
maxPagesPerDomain: 7,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(token=os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/decision-maker-email-finder").call(run_input={
"domains": ["www.w3.org"],
"decisionMakerCategory": "director",
"maxLeadsPerDomain": 3,
"maxPagesPerDomain": 7,
})
print(list(client.dataset(run["defaultDatasetId"]).iterate_items()))

MCP and AI agents

This Actor is currently unavailable through hosted Apify MCP and Apify AI. It requests full account permissions, and those services exclude full-permission Actors. Use the account-authenticated API examples above after reviewing the permissions. An assistant can help you analyze results that you choose to share safely.

The official MCP guide explains eligibility and authentication. The Apify MCP server and configurator supports eligible Actors through focused setup or general-server discovery. These are Apify's shared services, not servers provided by this scraper.

Setup reference and current restriction

A focused configuration normally selects an Actor by identifier. The following reference shows the format, but it cannot expose or run this Actor while its full-permission requirement remains:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/decision-maker-email-finder"
}
}
}

The general server at https://mcp.apify.com lets assistants discover eligible tools. Searching there for fetch_cat/decision-maker-email-finder does not bypass this Actor's exclusion. Sign in with OAuth where supported, or follow your client's secure Bearer-token setup. Authentication does not override eligibility.

For supported tools, the official Apify plugin can help configure a coding assistant. Client setup references include:

Apify AI in Console is another way to find and run eligible Actors. It is in beta and asks for confirmation before charging for a run, but it cannot run this full-permission Actor.

Example requests

These requests suit an assistant working with your own approved API integration, not hosted MCP execution of this Actor:

  • “Find publicly listed directors at W3C and put their names, titles and source URLs in a contact table.”
  • “Collect public executive emails from the company domains I provide and keep the evidence page beside each address.”
  • “Retrieve public manager contacts from these company websites, then prepare a CSV with names, titles and sources.”

The scraper retrieves the contacts. Any comparison, summary or CSV preparation belongs to the assistant's workflow. Read results from the returned run and dataset, and follow an existing running operation rather than starting duplicates. Check the live Pricing tab before authorizing charges.

Pay with x402

Apify's prepaid-token route cannot currently run this Actor, because prepaid accounts cannot approve its full-permission requirement. Use a regular Apify account with reviewed permissions instead.

For eligible limited-permission Actors, Apify AGI exchanges an x402 payment for a prepaid, spend-capped API token. An agent can then use that token with the API or an authenticated MCP connection. This experimental platform flow does not add a payment server to this scraper.

See Apify's x402 guide for current eligibility, wallet setup and terms. Keep private keys and payment tokens out of prompts and public examples.

Apify also documents MPP prepaid access and separate per-request payment routes such as Skyfire. Their eligibility rules differ, and none should be assumed to bypass this Actor's permission restriction. See the agentic payment guide before choosing a route.

FAQ

How do I find decision-maker emails for a company domain?

Supply the company domain and choose an executive, director or manager category. Review each returned contact's source page before using the address.

How do I export contacts with their source URLs?

Export the run's dataset as JSON, CSV or Excel. Retain sourceUrl, emailEvidence and identityEvidence alongside the contact fields.

Why did a company return no contacts?

It may publish no person-bound addresses or no matching titles. Check the run status and any summary before interpreting empty output. A failed or blocked search does not prove the company has no contacts.

Does it create likely email addresses?

No. It exports public email evidence associated with a person and never guesses address patterns.

Can I use this Actor through hosted MCP or prepaid x402 tokens?

Not with its current full-permission requirement. Use the regular account-authenticated API after reviewing permissions. The MCP and payment sections explain the platform restrictions.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL or run ID, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. You can leave a review from the Actor page when the review option is available. Your feedback helps others choose the right tool and helps us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥