Find LinkedIn From Work Email
Give it a work email address, get back that person’s LinkedIn profile URL.
- Tool
find_linkedin_from_work_email- Cost
- 2 credits
- Category
- Reverse Lookup
- Required input
email- Returns
- 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.
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
email | string | Yes | Work email address |
How to use it
Connect the MCP server
Follow the setup guide for your client. Browser sign-in, no API key.
Look up one address
Find the LinkedIn profile for jane@stripe.comBackfill a list
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.Enrich what you found
For every profile you resolved, pull the full LinkedIn profile —
work history, education and skills.Example prompts
| Ask your client | What you get back |
|---|---|
| ”LinkedIn URL for jane@stripe.com” | One profile URL |
| ”Resolve LinkedIn profiles for this list of work emails” | One URL per row, blanks where no match exists |
| ”Find LinkedIn for jane@stripe.com, then check if she changed jobs” | Chains check_job_change after the lookup |
| ”Find LinkedIn for jane@gmail.com” | Better served by find_linkedin_from_personal_email |
Best prompting practices
- Say “work email”. Naming the address type keeps your client on this tool rather than the personal-email variant.
- Forbid guessing. Add “do not guess a profile URL” to batch prompts. A fabricated
linkedin.com/in/jane-doelooks exactly like a result. - Cap the batch. “Stop after 50 and report credits used” keeps a long list from running away with your balance. At 2 credits a row, lists add up fast.
- Deduplicate first. Two rows with the same address cost 4 credits and return the same answer.
- 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.
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.
Shared inboxes — info@, sales@, support@ — belong to no single person and
will not resolve. Filter generic addresses out of your list before running the
batch so you are not paying 2 credits for a guaranteed blank.
Related tools
| Tool | Use it instead when |
|---|---|
find_linkedin_from_personal_email | The address is a personal one — 2 credits |
find_work_email | You have the LinkedIn URL and need the email — the reverse direction |
enrich_person | You want a full contact record from the email, not just the URL |
linkedin_profile_enrich | You already have the URL and want work history, education and skills |
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.