Find Work Email

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

What it does

• Resolves a LinkedIn profile URL to the person’s work email address.
• Runs waterfall enrichment — Datagma, LeadMagic, RocketReach, Apify, Forager, Findymail and LinkedIn, tried in sequence.
• Stops at the first provider that returns a result. You are charged once per lookup, not once per provider tried.
• Passing first_name, last_name and organization_name alongside the URL raises the hit rate on sparse profiles.
• An empty result means no provider had the address — not that the person has no email.

It finds an address. It does not check that the address is deliverable — chain verify_email for that.

Parameters

How to use it

Find the work email for linkedin.com/in/janedoe

Find work emails for these 20 LinkedIn URLs. Skip anyone where no email is
found — do not guess an email pattern. Report how many credits you used.

Now verify each email you found and drop anything that isn't deliverable.

Example prompts

Best prompting practices

• Say “work email”. Without it your client may reach for find_personal_email, which costs 3× as much.
• Pass the name and company alongside the URL whenever you have them — they are free and they lift the hit rate.
• Forbid guessing. Add “do not guess email patterns” to any batch prompt. A fabricated first.last@company.com looks exactly like a result and bounces like a fake.
• Cap the batch. “Stop after 50 and report credits used” keeps a long list from running away with your balance.
• Verify separately. Finding and verifying are two different tools with two different costs.

Output

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

Credits and limits

1 credit per lookup. Run check_credits (free) before a large batch.

Related tools

Next steps

• All MCP tools — the full catalogue with credit costs
• 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.