Find LinkedIn From Work Email
/find-linkedin-from-work-emailTurn a work email into that person's LinkedIn profile URL, waterfalled across five data providers and charged 2 credits per lookup.
Overview
find_linkedin_from_work_email is a SyncGTM MCP tool that takes one work email address and returns the matching LinkedIn profile URL. It waterfalls the lookup across Apollo, RocketReach, Datagma, LeadMagic and Icypeas, stopping at the first provider that has the address on file, and bills 2 credits per lookup whether or not a match comes back. Use it to turn signup exports, CRM contacts and event registrations into profile URLs you can enrich, monitor or personalize against.
What it does
- 1
Takes a single work email address in the `email` parameter. That is the only parameter the tool accepts, and there is no batch mode — one call per address.
- 2
Runs waterfall enrichment across Apollo, RocketReach, Datagma, LeadMagic and Icypeas in sequence, stopping at the first provider that returns a match.
- 3
Returns three fields: `linkedin_url`, the `email` you sent, and a `status` (`found` on a hit). An empty result means no provider had that address on file, not that the person has no LinkedIn profile.
- 4
Does not return a name, job title, company, phone number or a second email. For a contact record use `enrich_person` (1 credit); for work experience, education and skills use `linkedin_profile_enrich` (1 credit) once you hold the URL.
- 5
Does not resolve shared inboxes. `info@`, `sales@` and `support@` belong to no single person and return blanks you still pay for. Personal addresses such as gmail.com and outlook.com belong to `find_linkedin_from_personal_email` (2 credits).
- 6
Costs 2 credits per lookup, flat, charged once per call no matter how many providers were tried. A miss costs the same as a hit.
How to use it
- 1
Download the skill file — it saves as find-linkedin-from-work-email.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the find-linkedin-from-work-email/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server — browser sign-in, no API key — then run `check_credits` (free) to confirm your balance covers 2 credits per address.
- 4
Paste your address list or attach the export and type /find-linkedin-from-work-email. The skill drops role inboxes, moves personal domains to the sibling tool and deduplicates before it spends a credit.
- 5
Set the batch cap — the one setting worth tuning. Say "stop after 25 lookups and report credits used", because a 500-row export at 2 credits a row is 1,000 credits.
Use cases
Inbound signup routing
Resolve every self-serve signup's work email to a LinkedIn URL, then enrich those URLs so reps see seniority and employer before the first touch. Junior signups go to nurture, VPs go to the call block.
CRM LinkedIn backfill
Fill the empty LinkedIn URL field on contacts that entered the CRM through a form. Job-change checks and profile enrichment both need that URL as an anchor.
Webinar and event lists
Turn a registration export into profile URLs, then run a profile enrich on the resolved rows and rank attendees by title so the follow-up sequence goes to the people who can actually buy.
Unknown reply lookup
An inbound reply arrives from an address nobody recognizes. One lookup returns the profile URL so the rep can see who they are talking to before answering.
GTM workflow examples
Score last week's signups before Monday's call block
- 1Export last week's self-serve signups, drop `info@` and `support@` style inboxes plus any gmail.com or outlook.com addresses, deduplicate, then run `check_credits` to confirm the balance covers 2 credits per surviving row.
- 2Run `find_linkedin_from_work_email` on each address to produce a profile URL per signup.
- 3Run `linkedin_profile_enrich` (1 credit) on every URL that resolved to pull work experience, education and skills — read current title and time in role off the work-experience block.
- 4Run `enrich_organization` (2 credits) on the email domain of every signup at manager level or above to add industry, size, funding and technologies.
- 5Tier the rows: director-plus at 50+ employee companies to the call block, everyone else to nurture.
Outcome: A tiered signup sheet where every resolved row carries a LinkedIn URL, current title, time in role and company size, sorted so the rep's first ten calls are the ten best signups.
Find the champions who quietly left
- 1Pull CRM contacts that have a work email but an empty LinkedIn URL field, capped at the 50 highest-value accounts — 100 credits at 2 credits a row.
- 2Run `find_linkedin_from_work_email` on each address and write the resolved URL back to the contact record.
- 3Run `check_job_change` (2 credits) on every resolved URL to flag people whose current employer no longer matches the account on file.
- 4Run `find_work_email` (1 credit) on each mover's profile URL to get their address at the new company, then `verify_email` (0.3 credits) on it — find_work_email finds an address, it does not check deliverability.
- 5Run `find_people_within_company` (1.5 credits) on the accounts that lost their champion, passing the domain plus a `job_title` array of the departed champion's title and its variants, `max_profiles` up to 50.
Outcome: Two lists: champions to re-open at their new employer with a deliverability-checked work email, and the accounts that now need a named replacement contact.
Personalize webinar follow-up in one pass
- 1Deduplicate the registration export, drop role inboxes, and cap the run at 40 lookups — exactly 80 credits at 2 credits each.
- 2Run `find_linkedin_from_work_email` on the 40 addresses to get profile URLs, expecting blanks on the addresses no provider holds.
- 3Run `linkedin_profile_posts` (0.3 credits) on each resolved URL and keep the most recent post as the opening line source.
- 4Run `verify_email` (0.3 credits) on the original addresses so nothing bounces when the sequence sends.
Outcome: A follow-up sheet with one row per resolved attendee — up to 40 — each carrying a LinkedIn URL, a deliverability-checked address and one post-based personalization line, ready to import into the sequencer.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
Find the LinkedIn profile URL for jane@stripe.com. Do not guess a URL if there is no match.Here are 40 work emails from our signup export. Drop any info@, sales@ or support@ address and any gmail.com or outlook.com address, then look up the first 25 only. Return a table of Email | LinkedIn URL | Status and tell me how many credits you spent.Check my credit balance first, then resolve LinkedIn URLs for these 20 work emails. Stop at 20 lookups. For every URL you find, run linkedin_profile_enrich and read the current title, employer and time in role off the work-experience block.Resolve the LinkedIn URL for priya@datadoghq.com from her work email, then run check_job_change on that URL to see whether she has moved recently.Take the 30 work emails in this CSV, cap the run at 15 lookups, resolve LinkedIn URLs, and list separately the rows that came back with no match so I can route them elsewhere.Best practices
Filter role inboxes before you run. `info@`, `sales@` and `support@` belong to no single person, and each one still bills 2 credits to return a blank.
Say "work email" in the prompt. Naming the address type keeps the client on this tool instead of `find_linkedin_from_personal_email` (2 credits), which is the right one for gmail.com and outlook.com addresses.
Add "do not guess a profile URL" to every batch prompt. A fabricated linkedin.com/in/ slug is indistinguishable from a real result and corrupts every step downstream.
Deduplicate on the lowercased address first. Two identical rows cost 4 credits and return the same answer once.
Cap the batch and ask for a credit report. At 2 credits a row, a 500-line export is 1,000 credits before you have enriched anything.
If what you actually want is title and company rather than the URL, `enrich_person` (1 credit) takes the same email and returns a contact record for half the price. This tool is a reverse lookup, not an enricher.