LinkedIn Profile Finder - Email to LinkedIn URL Lookup

LinkedIn Profile Finder - Email to LinkedIn URL Lookup

Turn an email address into the person's public LinkedIn profile, with a confidence score on every match. Paste one email or a whole list and get back a clean table of LinkedIn URLs for your CRM, outreach or recruiting pipeline. No LinkedIn login, no cookies, nothing tied to your account.

Use it as a reverse email lookup, an email to LinkedIn API or a lead enrichment step from the Apify Console, the Apify API, Python, JavaScript, n8n, Make or an AI agent, and export the rows as JSON, CSV or Excel. Available as an Apify Actor. $0.005 per email checked plus $0.02 per confident match. Works with no API keys; free Brave Search and Groq keys widen coverage.

What does it do?

• Email in, best-match LinkedIn URL out, with a 0 to 100% confidence score on every row so you know which matches to trust.
• Bulk or one-off. A single address or thousands, one result row each.
• Pay for results. Half a cent per email checked; the match fee applies only when a URL clears your confidence gate.
• Public information only. GitHub commit authors, Gravatar, PGP keyservers and handle probes on 8 platforms. No data broker, no private database.
• Account-safe. It never logs into LinkedIn or touches your session, so there is nothing to get flagged.

How is it different from other email to LinkedIn finders?

• Every row shows its evidence. The confidence score comes with where the name came from (the address, a GitHub commit, Gravatar) and on how many platforms the handle was confirmed, so a match can be checked instead of taken on trust.
• A miss is a clean miss. Role mailboxes (info@, support@, sales@) are skipped, and an address with no candidate returns found: false rather than a confident guess.
• Possible matches are free. Rows between 50% and your gate come back with their score and no match fee, for you to verify.
• No data broker behind it. Results are rebuilt from public developer and social profiles on every run, so nothing comes from a purchased database.

When should I use it?

• Sales and growth: enrich inbound leads and sign-ups with the right LinkedIn profile before you reach out.
• Recruiting: turn a list of candidate emails into LinkedIn profiles.
• RevOps and CRM: clean, verify and backfill contact records at scale.
• Founders and operators: see who actually emailed you.

How much does it cost to find a LinkedIn profile from an email?

Pay per event. Platform compute is included in the prices.

On paid Apify plans the email and match fees are 10% less on Scale ($0.0045 and $0.018) and 20% less on Business and above ($0.004 and $0.016). The run start fee is the same on every plan.

A run stops at its spending limit: an email is looked up only while the limit can still pay for it and a confident match, and a limit that cannot pay for one email ends with nothing looked up or charged.

How does the price compare with other email to LinkedIn finders?

Actors on the Apify Store that turn an email into a LinkedIn profile, found by searching "email to linkedin", "linkedin profile finder email" and "reverse email lookup linkedin" on 2026-10-30, with 30 or more users in the last 30 days, ordered by users. Free-plan prices from each listing.

Where others are cheaper: oday's lookup costs less per email, and b2bsearch's two actors charge less per found profile and nothing for misses. This actor costs more per match because a match is charged only above your confidence gate and arrives with its evidence; compare on a sample of your own list.

Which inputs does it take?

Only the emails are needed; every other field has a working default.

Example input:

{

"emails": ["anshumanatrey@gmail.com", "satya.nadella@microsoft.com"], "aiMode": "balanced" }

What does the output look like?

This is the real dataset from a run on 2026-09-12 (build 0.1.5, no API keys, default settings): six emails in 25 seconds at 1 GB of memory. One row, a private person's personal address, is left out here.

Confident means the row cleared the 80% gate. Those are the only rows that carry the match fee. Rows between 50% and 79% are possible matches, returned free with their score, for you to verify before use.

One row as JSON (the signals block is what the scorer saw):

{

"email": "anshumanatrey@gmail.com", "found": true, "linkedin_url": "https://www.linkedin.com/in/anshumanatrey", "confidence": 0.97, "passes_gate": true, "gate_threshold": 0.8, "derived_name": "Anshuman Atrey", "name_source": "github_commit", "source": "handle_pivot", "evidence": "handle 'anshumanatrey' confirmed on 4 platform(s) -> likely LinkedIn slug", "signals": { "names": [{"value": "Anshuman Atrey", "source": "github_commit"}], "handles": ["anshumanatrey"], "confirmed_socials": ["GitHub: https://github.com/anshumanatrey", "YouTube: https://www.youtube.com/@anshumanatrey", "Telegram: https://t.me/anshumanatrey"] } }

How fast is it?

About 4 seconds per email at the 1 GB default, so a 100-email list finishes in about 7 minutes. The 6-email run above used 0.0069 compute units.

Common questions

How accurate are the matches?

Measured on the run above: 5 of 6 addresses resolved to a URL, 1 above the gate, and the role mailbox was correctly skipped.

• Work emails (first.last@company.com) give the name from the address itself. The handle probes then look for that name as a handle across GitHub, GitLab, dev.to, npm, Gravatar, Linktree, About.me, YouTube and Telegram. Three or more hits put the match at 78%.
• Personal addresses resolve when the person has a public developer or social footprint. A GitHub commit author name or a Gravatar display name is authoritative and lifts confidence to the high 90s.
• Over the gate. A confident match needs a name from an authoritative source plus a handle that is consistent across platforms. A free Brave Search key adds a web-search check on each candidate.

Does it log into LinkedIn?

No. It never logs in, uses no cookies and touches no session. LinkedIn login-walls its pages, so a URL is a strong lead confirmed by cross-platform evidence, not a fetched profile. Turn on Scrape the matched profile with a Bright Data key if you need the full profile.

How do I run it from Python or an AI agent?

Through the Apify API, with your Apify token:

from apify_client import ApifyClient

client = ApifyClient(" ") run = client.actor("anshumanatrey/linkedin-harvester").call(run_input={"emails": ["satya.nadella@microsoft.com"]}) for row in client.dataset(run["defaultDatasetId"]).iterate_items(): print(row["email"], row["linkedin_url"], row["confidence"])

AI agents can call it through the Apify MCP server at https://mcp.apify.com, and n8n and Make have Apify nodes.

Am I charged for emails that find nothing?

The $0.005 email fee covers the lookup, found or not. The $0.02 match fee applies only to a URL at or above your confidence gate, so misses and possible matches cost nothing more.

Is it legal to use?

It reads public information only. Use it for legitimate sales, recruiting, research and verification, follow the privacy laws that apply to you (GDPR, CCPA and local equivalents), and honor opt-out and do-not-contact requests.

Limitations

• A URL is resolved from public evidence, not read from LinkedIn, which login-walls its pages.
• Personal addresses with no public developer or social footprint usually stay unresolved.
• Without a Brave Search key, most work-email matches land at 78%, just under the default gate; lower the gate or add the free key.
• Role mailboxes (info@, support@, sales@) are skipped by design.

Who maintains it?

Built and maintained by Anshuman Atrey (@AnshumanAtrey), who publishes a portfolio of OSINT actors on Apify Store. For a feature request or a bug, message LinkedIn (fastest), open an issue on the GitHub repo, or write through atrey.dev.

Sibling actors

| domain-history-contact-osint | Domain -> previous owner, WHOIS history, archived contacts with source U