Email Finder — Find Email by Name and Company Domain

An email finder for one job: find email by name and company domain — you know who to reach, it returns their most likely business address.

Give it a name and a company domain, get back the most likely public business email — inferred from the standard address patterns companies use, with the company domain checked for DNS MX records. You pay only for a person we resolve.

Output is a prospect list for your sales team, assembled from public web and business sources. Use it in line with applicable outreach and privacy law.

#> Company names and LinkedIn company URLs are accepted — "company": "Stripe" or a linkedin.com/company/... URL is resolved to the company's mail domain before the lookup (since 0.0.21). A name that cannot be resolved is skipped and not charged.

📊 Sample Output

full_name	company_domain	company_input	domain_resolved_from	best_email	email_provider
Patrick Collison	stripe.com	Stripe	company-name lookup	[email on record]	Google Workspace
Brian Chesky	airbnb.com	airbnb.com	input	[email on record]	Google Workspace

Real rows from run xcOSMlTDGTswbpZXe on build 0.0.22 (2026-09-24), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

⚙️ Sample inputs

This is the Store example input — the same input Apify's automated check runs — so it is proven to return rows on the current build. Paste it into the input form, or send it through the API, CLI or a schedule:

{
  "people": [
    {
      "fullName": "Patrick Collison",
      "companyDomain": "stripe.com"
    }
  ],
  "verify": true
}

🔧 Input reference

Field	Type	Default	What it does
people (required)	array	[{"fullName": "Patrick Collison", "company": "Stripe"}, {"f…	People to find business emails for. Each item is {"fullName": ..., "company": ...} where company can be a website domain (stripe.com), a company name (Stripe, Acme Inc) or a Linke…
verify	boolean	true	When enabled (default), each company domain is checked for valid DNS MX records and the email provider (Google Workspace, Microsoft 365, etc.) is detected. Disable to skip DNS loo…
notionConnector	string		Optional. Connect your Notion workspace and the resolved business emails are also written as a Notion page in the same run — the Actor never sees your Notion credentials. Authoriz…
notionParentId	string		Optional. The Notion page ID to create the page under. If blank, Notion creates a private page in your workspace.
supabaseConnector	string		Optional. Connect your own Supabase project and the results are also inserted into a table in the same run — the Actor never sees your Supabase credentials. Authorize a write-scop…
supabaseTable	string	"nexgendata_leads"	Target table in the public schema (created if missing, with id, a jsonb data column, and a scraped_at timestamp). Default: nexgendata_leads.
supabaseProjectId	string		Your Supabase project reference (e.g. abcdefghijklmnop). Required unless your connector URL is already project-scoped. Find it in your project URL: supabase.com/dashboard/project/…
deliveryDedup	boolean	true	When on (default), records already delivered in a previous run are not delivered again to the same destination — so scheduled runs only push new items. Turn off to deliver every r…

🧾 JSON sample record

One real record from run xcOSMlTDGTswbpZXe (emails/phones masked, long text shortened):

{
  "full_name": "Patrick Collison",
  "company_domain": "stripe.com",
  "company_input": "Stripe",
  "domain_resolved_from": "company-name lookup",
  "best_email": "[email on record]",
  "candidate_emails": [
    {
      "email": "[email on record]",
      "pattern": "first.last",
      "rank": 1
    },
    {
      "email": "[email on record]",
      "pattern": "firstlast",
      "rank": 2
    },
    {
      "email": "[email on record]",
      "pattern": "flast",
      "rank": 3
    },
    {
      "email": "[email on record]",
      "pattern": "first",
      "rank": 4
    },
    {
      "email": "[email on record]",
      "pattern": "first_last",
      "rank": 5
    },
    {
      "email": "[email on record]",
      "pattern": "f.last",
      "rank": 6
    },
    {
      "email": "[email on record]",
      "pattern": "firstl",
      "rank": 7
    },
    {
      "email": "[email on record]",
      "pattern": "last.first",
      "rank": 8
    },
    "…"
  ],
  "mx_verified": true,
  "email_provider": "Google Workspace",
  "confidence": "high",
  "is_free_provider": false,
  "mx_records": [
    {
      "priority": 10,
      "server": "aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt2.aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt1.aspmx.l.google.com"
    },
    {
      "priority": 30,
      "server": "aspmx2.googlemail.com"
    },
    {
      "priority": 30,
      "server": "aspmx3.googlemail.com"
    }
  ],
  "data_source": "Business email pattern inference + public DNS MX",
  "as_of_timestamp": "2026-09-24T23:58:22.415916+00:00"
}

💰 Pricing

Event	Price (USD)	When it is charged
Actor Start (apify-actor-start)	$0.005	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Business email found (result)	$0.02	Charged per person with a resolved business email.

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.02 = $2.00 plus the start fee.

🔗 Related Actors

More from the NexGenData Leads, contacts & enrichment family:

• Leads to Notion CRM — Verified Lead Delivery API
• Local Business Leads — Google Maps + Verified Emails API
• Website Tech & Contact Audit — Tech Stack + Emails API
• Person Enrichment API — Name & Company to Public Profile
• Phone Number Validation API — Format, Carrier & Line Type
• Restaurant & Food Business Leads — Local Prospect Lists API

30 more in this family on the NexGenData Store page.

✅ Pay only for a resolved result

Billed per person resolved, not per attempt. If the company domain publishes no MX records, or the name/domain can't be used, that row is skipped — no row, no charge. If public DNS can't be reached at all, the run fails rather than finishing green and empty.

🔎 How it works — and what "verified" does not mean

1. The name is normalised (accents, titles, initials) and expanded into the 13 common business-email patterns (first.last@, flast@, first@, …), ranked by real-world frequency.
2. The company domain is checked for DNS MX records on public DNS (3 attempts across the local, Cloudflare and Google resolvers). That tells us the domain can receive mail and which provider runs it (Google Workspace, Microsoft 365, Proofpoint, …).
3. No SMTP handshake, no mailbox probe, no list purchase. mx_verified: true means the domain accepts mail — it is not a claim that the specific mailbox exists. Treat best_email as a high-confidence inference and use a mailbox-level validator before a large send.

📊 What you get

Clean JSON, one record per resolved person:

• full_name — Full name as supplied
• company_domain — Normalised company domain
• best_email — Highest-ranked inferred address
• candidate_emails — All patterns, ranked
• mx_verified — Domain publishes MX records (not a mailbox check)
• email_provider — Mail provider detected from MX (e.g. Google Workspace)
• confidence — high / medium / low
• is_free_provider — Domain is a consumer mail provider
• mx_records — Top MX records observed
• data_source — "Business email pattern inference + public DNS MX"
• as_of_timestamp — When the lookup ran

Pricing: $0.005 per Actor start (per GB of memory) plus $0.020 per result delivered (Pay-Per-Event) — about 50 resolved people per $1. Rows and charges are 1:1; skipped and failed lookups are never charged.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and run prospecting on demand.

Agentic payments (x402): Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 Related lead-gen actors

The lead-gen workflow chain — found leads? verify → enrich → push to CRM:

1. Find: B2B Leads Finder · Company Email Finder · Website Contact Scraper · Yellow Pages
2. Enrich: Company Enrichment · B2B Contact Enricher · Lead List Enricher · Website Tech & Contact Audit
3. Validate & clean: Email Verification · Bulk Email Validator · Lead List Cleaner
4. Deliver: Leads to Notion CRM

Front door — Sales Intelligence MCP: the sales-intelligence agent that fronts this whole cluster → Sales Intelligence MCP

---

Public web & business-source data, assembled as sales-team prospect lists.