Find Work Email
/find-work-emailTurns a LinkedIn profile URL into that person's business email address in one call, with waterfall enrichment across seven providers.
Overview
find-work-email is a SyncGTM MCP skill that takes a LinkedIn profile URL and returns that person's business email address. It drives the `find_work_email` tool, which runs a waterfall across Datagma, LeadMagic, RocketReach, Apify, Forager, Findymail and LinkedIn, stopping at the first provider that has the address. The skill adds the parts the raw tool call leaves to you: deduplication, a batch cap, a hard no-guessing rule, and an optional `verify_email` pass so nothing fabricated reaches your sequencer.
What it does
- 1
Takes one input: `linkedin_url`, a full LinkedIn profile URL. No company pages, no search URLs, one person per call.
- 2
Accepts three optional parameters that cost nothing extra — `first_name`, `last_name` and `organization_name`. They raise the hit rate on sparse profiles and stop a common name matching the wrong person.
- 3
Returns three fields: the `email` address, a `status`, and the `linkedin_url` you sent. Nothing else.
- 4
Runs waterfall enrichment across Datagma, LeadMagic, RocketReach, Apify, Forager, Findymail and LinkedIn, stopping at the first provider that returns a result.
- 5
Does not check deliverability, and does not return personal addresses, phone numbers, job titles or work history — chain `verify_email` (0.3 credits), `find_personal_email` (3 credits), `find_mobile_number` (12 credits) or `enrich_person` (1 credit) for those.
- 6
Costs 1 credit per lookup, charged once no matter how many providers the waterfall walks through.
How to use it
- 1
Download the skill file — it saves as find-work-email.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the find-work-email/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server using the setup guide for your client. It is a browser sign-in, no API key.
- 4
Type /find-work-email and paste a LinkedIn profile URL, or a list of them. Include first name, last name and company wherever your list already has them — they are free and they lift the hit rate.
- 5
Tune one setting: the batch cap. Say 'cap at 50 lookups and report credits used' so a long list cannot run away with your balance.
Use cases
Sequencer-ready lead lists
Turn a sourcing run that produced LinkedIn URLs into addresses you can load into Instantly, Smartlead or Outreach. One credit per person, no scraping setup.
CRM contact backfill
Fill the empty email column on Salesforce or HubSpot records that only carry a LinkedIn URL. Run it over an export and push the found addresses back.
Job-change re-intros
A champion moved companies and the CRM address is dead. Get the business address at their new employer so the re-intro lands in the right inbox.
Post engager follow-up
People who reacted to a competitor's launch post are already in-market. Convert those profile URLs into contactable addresses the same day.
GTM workflow examples
Fill the buying committee at 40 target accounts
- 1Run `check_credits` (free) and budget the run: 40 calls to `find_people_within_company` at a flat 1.5 credits each is 60 credits, plus 1 credit for every email lookup that follows.
- 2Call `find_people_within_company` on each of the 40 domains with job_title ["VP Sales", "Head of Revenue Operations"] and max_profiles 3, which returns name, title, company and LinkedIn URL per profile.
- 3Deduplicate the profile URLs, then run `find_work_email` at 1 credit on each one, passing first_name, last_name and organization_name carried over from the previous step.
- 4Run `verify_email` (0.3 credits) on every address returned and drop anything that does not come back deliverable.
Outcome: Around 35 verified sales-leader addresses across 40 named accounts for roughly 130 credits, ready to import into Instantly or Outreach.
Re-intro to champions who changed jobs
- 1Run `check_job_change` (2 credits per profile, capped at 50 profiles) on closed-won contacts that already have a LinkedIn URL, and keep the rows where job_change is true — the response carries new_company and new_title, so no extra enrichment call is needed for those fields.
- 2Run `find_work_email` (1 credit) on the same profile URL for each mover, passing new_company as organization_name so the waterfall targets the new employer's domain instead of the dead one in your CRM.
- 3Run `verify_email` (0.3 credits) on each new address and hold anything that does not come back deliverable rather than sending to it.
- 4Run `check_promotions` (2 credits) over the non-movers from the same sweep to catch champions who stayed at the company but changed seats.
Outcome: A 'they moved' list carrying new company, new title and one fresh verified address per champion, plus a promotions list from the same sweep, ready for a re-intro that names their new employer in the first line.
Work a competitor's launch post into a sequence
- 1Run `linkedin_post_engagers` on the competitor's launch post URL for page_number 1, 2 and 3 — one page per call at 0.3 credits, ten pages maximum — collecting name, headline, profile URL and reaction type.
- 2Run `linkedin_post_commenters` (0.3 credits) on the same post and merge both lists deduplicated by profile URL, ranking commenters above reactors.
- 3Run `find_work_email` on the top 50 profiles by ICP fit, capped at 50 lookups and 1 credit each, passing first_name, last_name and the employer parsed from the headline as organization_name.
- 4Run `verify_email` (0.3 credits) on every address returned to strip dead mailboxes before anything is loaded.
Outcome: Around 30 verified addresses off a single competitor post for about 60 credits, each row carrying the person's headline and reaction type as the personalization hook.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
Find the work email for https://www.linkedin.com/in/janedoe — pass first_name Jane, last_name Doe and organization_name Stripe to improve the match.Find work emails for these 25 LinkedIn URLs. Cap the run at 25 lookups, do not guess email patterns, skip anyone with no result, and report credits used.Run find_people_within_company on stripe.com for the titles VP Sales and Head of Revenue Operations with max_profiles 10, then find the work email for each profile returned and verify every address you get back.Check my credit balance, then find work emails for the first 50 rows in this CSV that have a LinkedIn URL. Verify each address, mark anything undeliverable, and report credits spent.Find the work email for https://www.linkedin.com/in/janedoe. If nothing comes back, scrape emails from stripe.com instead and tell me which source each address came from.Best practices
Say "work email" in the prompt. Without it your client may reach for `find_personal_email`, which costs 3 credits instead of 1.
Pass `first_name`, `last_name` and `organization_name` alongside the URL whenever your list has them. They add no cost and they lift the hit rate on sparse profiles.
Add "do not guess email patterns" to every batch prompt. A fabricated first.last@company.com looks exactly like a real result and bounces like a fake.
Cap the batch and run `check_credits` (free) first. "Stop after 50 and report credits used" is the difference between a 50-credit run and a 400-credit one.
An empty result means no provider had the address, not that the person has no email. Misses cluster on profiles with no company set and in regions with thin coverage — retry once at most, then fall back to `scrape_emails_from_website` (0.5 credits) for a company inbox or `find_personal_email` (3 credits) if a personal address is acceptable.
Finding and verifying are two tools with two costs. This tool never checks deliverability, so run `verify_email` (0.3 credits) before anything enters a sequence.