Decision-Maker Public Email Finder
Pricing
from $0.53 / 1,000 decision-maker email results
Decision-Maker Public Email Finder
Find publicly posted decision-maker email addresses on company websites with source-page evidence.
Pricing
from $0.53 / 1,000 decision-maker email results
Rating
0.0
(0)
Developer
Hanna Nosova
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
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:
{"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
{"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
{"domains":["fsf.org"],"decisionMakerCategory":"executive","maxLeadsPerDomain":1,"maxPagesPerDomain":12}
Department leaders
{"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.
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
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
from apify_client import ApifyClientclient = 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
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:
$claude mcp add apify -- npx -y @apify/mcp-server --tools fetch_cat/decision-maker-email-finder
For a JSON MCP client configuration:
{"mcpServers": {"apify": {"command": "npx","args": ["-y", "@apify/mcp-server", "--tools", "fetch_cat/decision-maker-email-finder"]}}}
Open Apify MCP 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
- Email MX Deliverability Verifier
- Google Maps Lead Finder
- LinkedIn Company Profiles Scraper
- 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.