LinkedIn Email Finder | Name + Company to Work Email

🏆 Part of The Mine Works' 149-actor portfolio · 40,000+ runs · 200,000+ results delivered across our full distribution stack · 99.9%+ success rate

💰 From $1.50 / 1,000 results.

⚡ Eight work-email patterns generated per person, then probed against the company's own mail server in one SMTP connection. You get the pattern that answers, labelled for how sure it is.

💸 A domain with no mail servers at all is never charged.

Overview

Give it a person's name and their company, as a domain or a company name, and this actor builds the eight standard work-email patterns and tests them against the company's mail servers directly instead of handing you a list of guesses.

It never sends a request to linkedin.com. LinkedIn is the shape of the input, a person and the company they work at, not the data source. That means no login, no session cookie and no LinkedIn scraping. It works from a name and a domain you already have, out of a lead list, a profile you are looking at, or a CRM export.

✅ Eight patterns per person · ✅ SMTP probe, not a guess list · ✅ Catch-all domains labelled honestly · ✅ No API key · ✅ MCP ready for AI agents

How it works

1. Parse. The full name is split into first and last, and a domain is taken from the domain field, or guessed best-effort from companyName if that is all you have. An explicit domain is always better.
2. Generate. Eight patterns: first, first.last, firstlast, firstl, flast, first_last, last.first, last.
3. MX. The domain's mail servers are resolved once and cached across the run.
4. SMTP. One connection probes every candidate, plus a random address to detect a catch-all domain. A pattern the server accepts is a confirmed match. If the domain accepts everything, including the random probe, nothing can be confirmed, so the most common pattern comes back labelled as a guess rather than dressed up as certainty.

Input

{
  "people": [
    { "fullName": "Patrick Collison", "domain": "stripe.com" },
    { "fullName": "Tobi Lutke", "companyName": "Shopify" }
  ],
  "checkSmtp": true
}

Field	What it takes
people	Each entry needs a fullName plus either a domain (preferred) or a companyName, which is used as a best-effort domain guess.
checkSmtp	On by default. Turn it off and every person comes back as the single most common pattern, first.last@domain, unconfirmed. Faster, less reliable.

Output

Field	Description
fullName	The person's name, as given
domain	The domain the candidates were built from
domainGuessed	True when the domain was derived from a company name
email	The most likely work email
pattern	Which of the eight patterns it matched
status	confirmed, guessed or no_mx
candidatesChecked	How many patterns were probed for this person
scrapedAt	When the person was processed

status is the field to read before you send anything. confirmed means the mail server explicitly accepted that exact mailbox. guessed means mail is plausibly deliverable to the domain but the specific mailbox could not be confirmed, either because the domain is catch-all or because the SMTP probe was blocked or inconclusive. no_mx means the domain has no mail servers at all.

Use cases

Sales outreach. Turn a prospect list of names and companies into send-to addresses before a campaign, instead of guessing and taking bounce-rate damage on your sending domain.

Recruiting. Confirm a candidate's work email before a cold approach.

Lead enrichment. Append an email column to a CRM export that only carries names and companies.

Pricing

Event	Price (Free and Bronze plans)	You pay when
Email found	$0.002	A confirmed or guessed email is delivered
Actor start	$0.01 per GB of memory, once per run	The actor starts running

💎 On the GOLD tier and above: $1.50 per 1,000 results ($0.0015 each, 25% below the FREE-tier price of $0.002). Your tier is shown on your Apify billing page.

$2.00 per 1,000 emails on Free and Bronze, $1.80 on Silver, $1.50 on Gold and above. Your plan is shown on your Apify billing page.

Both confirmed and guessed rows are charged, because both give you a usable address. A no_mx row is written to the dataset for the audit trail and is never charged.

Run it on a schedule

This is usually a one-off enrichment step on a fresh batch of names rather than a recurring watch, so run it as your pipeline produces rows, or wire it into an n8n or Make flow triggered by new CRM records. If you do want it on a timer:

1. Run it once with the input you want repeated, then click Save as a task so that exact input is attached to every future run.
2. In the Apify Console go to Schedules and create a new one, either a preset (hourly / daily / weekly) or a cron expression.
3. Save. It then runs unattended, billed the same pay-per-result way. Nothing is charged for the schedule existing.

Use from Claude, ChatGPT & any MCP agent

Hosted MCP endpoint, no install, OAuth on first connect:

https://mcp.apify.com/?tools=themineworks/linkedin-email-finder

Claude Desktop / Cursor config (token auth):

{
  "mcpServers": {
    "linkedin-email-finder": {
      "url": "https://mcp.apify.com/?tools=themineworks/linkedin-email-finder",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Ask your agent: "Find the work email for Patrick Collison at stripe.com."

FAQ

How is this different from a pattern guesser? Most tools stop at generating the candidates and leave you to test them. This one opens a connection to the company's mail server and probes them, then tells you in the status field whether the answer was confirmed or is still a guess.

What if none of the eight patterns is real? If the domain has no mail servers, the row is never charged. If mail servers exist but no single mailbox can be confirmed, you get the most common pattern labelled guessed, and that row is charged.

Does this scrape LinkedIn? No. The actor never sends a request to linkedin.com. It works from a name and a company you already have, plus public email-pattern conventions and SMTP.

Why do some domains only ever come back as guessed? Because they are catch-all: the server accepts mail to any address, including a random one, so no individual mailbox can be verified. Saying so is more useful than reporting false certainty.

Part of the outbound prospecting toolkit

Start from a company name or a domain, find the work email here, then check their tech stack or skip-trace a phone number if you need a channel other than email.

Keywords: LinkedIn email finder, find work email, email pattern verifier, SMTP email verification, B2B email finder, cold email list building, verified work email API