Person Email Finder — Name + Company to Email API

📧 Find likely business emails from a name and company site

Sales, recruiting, and research teams can turn a named person plus a known company domain or website into one pattern-inferred business email, ranked alternatives, confidence, and public MX evidence. Use the candidates for prospect research while keeping the difference between inference and mailbox verification clear.

• Business Email Finder — infer the highest-ranked business email candidate for a named person at a known company.
• Email Finder by Name and Company — combine a full name with a company domain or public website URL.
• Multiple Person Email Finder — process several named people and company sites independently in one run.
• Company Domain Email Finder — normalize a supplied company domain before generating candidates.
• Business Email Pattern Generator — compare ranked corporate email-pattern alternatives.
• MX Record Email Check — inspect whether the company domain has public mail-routing records.

📦 Returned data

Each successful row contains:

• the supplied fullName, optional companyName, and domainInput
• normalizedName and the normalized domain
• the highest-ranked email candidate and applied pattern
• confidence and the explicit patternInferred email status
• ranked alternatives with their patterns
• domainMail evidence: MX status, provider when recognizable, consumer-provider flag, and MX records
• provenance and observedAt for audit context

MX evidence describes the domain. It does not show whether a generated mailbox exists, belongs to the named person, or can receive a message.

▶️ Running the Actor

1. Add one or more people with a full name and company domain or website.
2. Run the Actor.
3. Open the default dataset to review or export the successful inferences.

A person needs a usable first and last name plus a valid bare domain or HTTP(S) website URL.

🧾 Input

people is required. Each entry requires fullName and companyDomainOrWebsite; companyName is optional context retained in the output.

{
  "people": [
    {
      "fullName": "Ada Lovelace",
      "companyDomainOrWebsite": "https://example.com/about",
      "companyName": "Example"
    }
  ]
}

📤 Output

The default dataset contains one row for each person whose input can produce a pattern-inferred business email. Download rows in supported dataset formats or retrieve them through the Apify API.

{
  "fullName": "Ada Lovelace",
  "normalizedName": "Ada Lovelace",
  "companyName": "Example",
  "domainInput": "https://example.com/about",
  "domain": "example.com",
  "email": "ada.lovelace@example.com",
  "pattern": "first.last",
  "confidence": "high",
  "emailStatus": "patternInferred",
  "alternatives": [
    {
      "rank": 2,
      "email": "adalovelace@example.com",
      "pattern": "firstlast"
    }
  ],
  "domainMail": {
    "mxStatus": "configured",
    "provider": "Google Workspace",
    "consumerProvider": false,
    "mxRecords": [
      {
        "preference": 10,
        "exchange": "aspmx.l.google.com"
      }
    ]
  },
  "provenance": "Pattern inference from submitted name and company site; public DNS MX observation",
  "observedAt": "2026-07-18T12:00:00.000Z"
}

💳 Pricing

This Actor uses pay-per-event pricing. The Actor-owned event applies only when one pattern-inferred business email is saved to the default dataset. Invalid inputs and runs with no saved email do not create that paid outcome; Apify platform usage may still apply.

🔌 Integrations

Use Apify datasets, API calls, schedules, webhooks, and platform integrations to send output to spreadsheets, CRMs, databases, or automation workflows.

❓ FAQ

Does MX status verify the generated mailbox?

No. MX records show whether the domain advertises mail routing. They do not confirm mailbox existence, ownership, or deliverability.

Can I provide a company name without its domain?

No. The Actor does not discover company websites from company names. Supply a known domain or public HTTP(S) company website URL.

What input should I use for several people at the same company?

Add one people entry per named person and repeat the known company domain for each entry.

Why are several alternative addresses returned?

The supplied inputs do not reveal a company's actual naming convention. Ranked alternatives show common fallback patterns while keeping that uncertainty visible.

Does this replace an SMTP email verifier?

No. This email finder tool generates pattern-based candidates and inspects public domain MX records. Use a separate verifier when you need mailbox-level SMTP evidence.

Are third-party data-provider credentials required?

No. Pattern inference and public MX checks use the submitted context and public DNS, without access to private mailboxes or a contact database.

How does this differ from contact-database email finder tools?

This Actor applies deterministic corporate email patterns to the name and company site you submit, then adds public DNS evidence. It does not query a third-party contact database or present inferred candidates as verified personal records.

📝 Changelog

• 0.1: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Related Actors

• LinkedIn Company People Scraper — collect visible names and roles from a known company's People page before email inference.
• SMTP Email Verifier — check generated candidates with SMTP-level evidence before outreach.
• Email MX Verifier — assess syntax, MX, provider, and risk signals for email addresses you already have.
• YouTube Lead Scraper — find source-backed public creator emails when you do not already know a person's company domain.

Made with ❤️ by Maxime Dupré