Find LinkedIn From Work Email

Give it a work email address, get back that person’s LinkedIn profile URL.

What it does

• Resolves a work email address to the matching LinkedIn profile URL.
• Runs waterfall enrichment — Apollo, RocketReach, Datagma, LeadMagic and Icypeas, tried in sequence.
• Stops at the first provider that returns a match. You are charged once per lookup, not once per provider tried.
• An empty result means no provider had that address on file — not that the person has no LinkedIn profile.

This is the reverse of find_work_email. Use it to turn a list of inbound signups, CRM contacts or event registrations into LinkedIn URLs you can enrich further.

If the address you hold is a personal one (gmail.com, outlook.com and similar), use find_linkedin_from_personal_email instead.

Use cases

• Turn inbound signups into workable leads. A form gives you an address; the profile gives you title, seniority and company to route on.
• Repair a thin CRM. Contacts imported as email-only become enrichable the moment they carry a LinkedIn URL.
• Prepare a social-touch sequence. Outreach that pairs an email with a connection request needs the profile first.
• Check whether a contact still holds the seat. Resolve the profile, then run check_job_change before you write.

How to use it

Find the LinkedIn profile for jane@stripe.com

Find LinkedIn URLs for these 40 work emails from our signup export.
Skip anything that returns nothing — do not guess a profile URL.
Report how many credits you used.

For every profile you resolved, pull the full LinkedIn profile —
work history, education and skills.

Example prompts

Best prompting practices

• Say “work email”. Naming the address type keeps your client on this tool rather than the personal-email variant, which is a separate tool with its own parameters.
• Strip the role addresses first. info@, sales@, support@ and hello@ belong to no one and are 2 credits for a guaranteed blank. “Drop every generic mailbox before running, and tell me how many you dropped.”
• Deduplicate first. Two rows with the same address cost 4 credits and return the same answer. Lowercase both sides before comparing.
• Forbid guessing. Add “do not guess a profile URL” to batch prompts. A fabricated linkedin.com/in/jane-doe looks exactly like a result.
• Ask for the pair back, blanks included. “Return a table: email, LinkedIn URL, not found where nothing resolved.” Hidden blanks make a 40% hit rate look like a full list.
• Chain deliberately. Resolving the URL is step one. Decide up front whether you also want a profile enrich or a job-change check, so the run happens once.
• Gate the spend. “Give me the deduped count and the credit total before you start” — at 2 credits a row, a backfill is worth one confirmation.
• Cap the batch. “Stop after 50 and report credits used” keeps a long list from running away with your balance.

Output

{
  "linkedin_url": "https://linkedin.com/in/janedoe",
  "email": "jane@stripe.com",
  "status": "found"
}

Credits and limits

2 credits per lookup, flat. Run check_credits (free) before a large backfill.

Parameters

Related tools

Next steps

• All MCP tools — the full catalogue with credit costs
• MCP use cases — CRM backfill workflows
• AI for Sales Reps — workflows that chain this tool into a list build

Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.