LinkedIn Email Finder — the addresses on record, not pattern guesses

$8 per 1,000 profiles that carry an address — 20% under the shelf's email mode, and there you pay per attempt whether an address turns up or not. A matched profile with no recorded address is a free row that still names the person.

Paste LinkedIn profile URLs and get back the email addresses actually on record for each person — work and personal — from a database of 1B+ professional profiles. Optional SMTP verification stamps a deliverability verdict on the best address.

This is a database lookup, not a live scrape and not a pattern generator. Most "email finder" tools guess first.last@company.com and let you find out the hard way. This actor returns only addresses that exist in the profile record — and when there are none, it says so for free.

Why this one

1. Recorded addresses, not guesses. Every address in the row comes from the person's data record. Rows carry the address type (work / personal) and the full list — often several addresses per person.
2. You pay only for delivered emails. A matched profile with no recorded address is a free no_email row that still names the person, the title and the employer — so you know the match worked and can route the lead to a name+domain finder. Unmatched URLs are free not_found rows.
3. Verification is its own event. verifyTopCandidate: true SMTP-checks the best address; you are billed for a verification only when the verifier actually answered.

Who is this for

• Outbound teams turning prospect lists of profile links into send-ready addresses.
• Recruiters contacting sourced candidates outside the platform inbox.
• RevOps enriching CRM contacts that carry a profile URL but no email.

Input

{
  "profileUrls": ["satyanadella"],
  "verifyTopCandidate": false
}

Links, bare handles, and mobile URLs all work; different spellings of the same profile are folded together and looked up once.

Output — a real found row

{
  "_status": "found",
  "_input": { "profile": "satyanadella" },
  "_freshness": "fresh_90d",
  "_fullData": "https://sputnik.io/from-apify?utm_source=apify…",
  "fullName": "Satya Nadella",
  "jobTitle": "Chairman and CEO",
  "companyName": "Microsoft",
  "email": "snadella@microsoft.com",
  "emailType": "work",
  "employerMatch": true,
  "workEmails": ["snadella@microsoft.com", "satya@microsoft.com", "satya.nadella@starbucks.com"],
  "personalEmails": ["satyan@microsoft.com"],
  "emailCount": 4,
  "linkedinUrl": "https://www.linkedin.com/in/satyanadella"
}

employerMatch tells you whether the best address belongs to the domain of the person's current employer. Records often carry addresses from board seats, alumni accounts and past jobs — those sort to the back of the list, and when nothing matches the current employer the flag says false instead of letting a stale address pass as a work address.

A profile that matched but has no recorded address:

{
  "_status": "no_email",
  "_input": { "profile": "some-handle" },
  "fullName": "Jane Smith",
  "jobTitle": "VP Engineering",
  "companyName": "Acme"
}

That row is free — and it hands you exactly what the name+domain route needs: feed it to our Work Email Finder actor to hunt the address by pattern + verification instead.

Pricing

Event	Price	When
Emails found	$0.008	a profile with ≥1 recorded work or personal address, full list included
SMTP verification	$0.006	verifyTopCandidate: true and the verifier answered
Matched, no address on record	$0	free row with name / title / employer
Not found / removed / invalid	$0	always free

Your free $5 Apify credit ≈ 625 found email rows (each often carrying several addresses).

FAQ

Where do the addresses come from? From the contact block of the person's database record — publicly available professional data. Nothing is generated or brute-forced.

What does no_email mean? The profile matched, the record has no recorded address. It is free, and the row names the person so you can continue with the Work Email Finder (name + company domain → ranked candidates with deliverability evidence).

How fresh is the data? Every row carries a _freshness bucket (fresh_90d, updated_1y, older) from the record's last re-confirmation.

Is there a rate limit? The actor paces itself; a 1,000-URL run finishes in minutes. For 10,000+ rows use our Bulk LinkedIn & Email Enrichment (CSV) actor.

Is this compliant? The database holds public professional profile data. We honor removal requests — contact us via the Issues tab.

The family

Same engine, other doors: Work Email Finder (name + domain → ranked candidates), Reverse Email Lookup (email → person), LinkedIn Profile Scraper (Database) (URL → full profile), LinkedIn Company Employees (domain → the whole roster), LinkedIn People Search (filters → lists), Bulk LinkedIn & Email Enrichment (CSV, 50k rows). One data core, one billing promise: misses are free.

Disclaimer

This Actor is an independent product and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. It does not access, crawl, or scrape LinkedIn at run time — answers come from our own database of publicly available professional data; "LinkedIn" is used only to describe the kind of public profile data the database covers. Removal requests are honored via the Issues tab.