Find LinkedIn Profile
Deepline resolveslinkedin.com/in/ URLs from work emails, personal emails, names, or company information. The lookup combines web search (Google, Exa), provider databases (Crustdata, Apollo, PeopleDataLabs), and Apify LinkedIn scraping for identity verification. Just describe who you’re looking for in natural language — no UI configuration or template selection required.
Getting the LinkedIn URL first typically improves downstream email hit rates by 15-25%. B2B data decays at roughly 22.5% per year (HubSpot via Cognism), so resolving LinkedIn early means you’re enriching the right person at their current company, not a stale record.
How do I find LinkedIn profiles with Claude Code?
Tell Claude Code what identifiers you have. Deepline picks the right lookup method based on your data.“Find LinkedIn profiles for everyone in contacts.csv”
“I have work emails — find their LinkedIn URLs”
“Find the LinkedIn profile for the CTO at stripe.com”With Codex:
What does the LinkedIn lookup do step by step?
The lookup runs a multi-stage pipeline: web search for candidates, nickname expansion for fuzzy matching, provider enrichment, and Apify verification for ambiguous matches. Waterfall enrichment gets 20-40% higher coverage than any single provider (Instantly).Search for LinkedIn URL candidates
Deepline searches Google (
google_search_google_search) and Exa (exa_search) with the person’s name, company, and title to find candidate LinkedIn profile URLs. This catches profiles that provider databases might miss.Expand nicknames
If the name could be a nickname (e.g., “Mike” for “Michael”, “Bill” for “William”), Deepline expands it using a 2,600+ entry nickname group database and searches for all variants. This prevents missed matches when someone’s LinkedIn uses their full name but your CRM has a short form.
Query enrichment providers
For email-based lookups, Crustdata, Apollo, and PeopleDataLabs do reverse email search. For name-based lookups, Crustdata people-search and Apollo search-people-with-match do fuzzy matching against their databases.
Verify identity with Apify
For ambiguous matches (common names, multiple candidates), Deepline runs the Apify LinkedIn profile scraper to pull the candidate’s actual job history, current company, and title. It then validates the scraped profile against your input data to confirm the match.
Which providers and methods does the LinkedIn lookup use?
The lookup chain depends on your input data. Email-based lookups use reverse search (higher precision). Name-based lookups combine web search with provider databases and nickname expansion:| You have | Method | What runs |
|---|---|---|
| Work email | Reverse lookup | Crustdata enrich-contact, Apollo people-match, PeopleDataLabs |
| Name + company | Web search + provider search | Google/Exa search for LinkedIn URLs, Crustdata people-search, Apollo search-people-with-match, nickname expansion |
| Name + company (ambiguous) | Web search + Apify verification | Same as above, plus Apify LinkedIn profile scraper to verify job history matches |
| Personal email | Reverse lookup variant | Same as work email chain |
CLI commands
CLI commands
How does nickname expansion work?
Deepline maintains a database of 2,600+ nickname groups (e.g., “Mike” maps to “Michael”, “Miguel”; “Bill” maps to “William”, “Billy”, “Will”). When searching for a person by name, Deepline checks if the first name has known variants and searches for all of them. This matters because your CRM might say “Mike Johnson” but his LinkedIn says “Michael Johnson.” Without nickname expansion, the search misses. With it, Deepline queries both “Mike Johnson” and “Michael Johnson” and deduplicates the results. Common examples: Bob/Robert, Dick/Richard, Liz/Elizabeth, Jim/James, Chuck/Charles, Peggy/Margaret, Bill/William, Ted/Theodore, Jack/John.Once you have a LinkedIn URL, email and phone lookups become significantly more accurate. If you have no LinkedIn URLs yet, find them first.
Related tasks: Find Work Email | Find Decision Makers | Enrich Company
Frequently Asked Questions
What data do I need to find a LinkedIn profile?
At minimum, a work email or a first name + company name. Work email gives the highest match rate via reverse lookup. Name + company triggers a broader search: Google/Exa web search for LinkedIn URLs, provider people-search, and nickname expansion. Having both email and name improves validation.Can I find LinkedIn profiles in bulk from a CSV?
Yes. Tell Claude Code “find LinkedIn profiles for contacts.csv” and Deepline reads your column headers, selects the right lookup method per row (reverse email, name-based web search, or both), and enriches every row. Always pilot with--rows 0:1 first to verify match quality before running the full batch.
How does Deepline handle common names like “John Smith”?
For common names, Deepline runs multiple searches (Google, Exa, provider databases) to find candidate LinkedIn profiles, then uses the Apify LinkedIn profile scraper to pull actual job history from each candidate. It validates current company and title against your input data. If no candidate matches confidently, it flags the row for manual review rather than returning a wrong profile.How accurate is LinkedIn profile resolution?
Email-based reverse lookups have the highest precision because email-to-LinkedIn is a 1:1 mapping in most provider databases. Name + company lookups combine web search, provider databases, nickname expansion, and Apify verification to prevent false positives. Unique names at well-known companies resolve most reliably. Common names at small companies are the hardest case — that’s where Apify job history verification matters most.Why should I find LinkedIn profiles before other enrichment?
A LinkedIn URL is the strongest person-level identifier. With it, email and phone waterfalls use LinkedIn-optimized provider chains (person_linkedin_to_email_waterfall or person_linkedin_only_to_email_waterfall) that have higher hit rates than name-based lookups.