linkedin.com/in/ URL from known person data. Supply
an email address, or supply a name with company data. The selected Play can use
web search, provider data, and profile checks. Available providers depend on
your connections and billing mode.
How do I find LinkedIn profiles with Claude Code?
In Claude Code, type:What does the LinkedIn lookup do step by step?
The lookup can use several stages. The stages depend on your input and the available provider actions.1
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.2
Expand nicknames
If the name can have a common variant, the lookup can search that variant.
For example, it can search for “Mike” and “Michael”. Review each candidate
before you accept the result.
3
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.
4
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.
5
Return validated LinkedIn URL
Compare the returned company and title with the input data. Review an
ambiguous result before you use it in another enrichment.
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:CLI commands
CLI commands
How does nickname expansion work?
For some names, the lookup can search common variants. For example, a search for Mike can also search for Michael. Name variants increase the candidate set; they do not verify identity. Compare the company, title, and location for every returned candidate. Common examples: Bob/Robert, Dick/Richard, Liz/Elizabeth, Jim/James, Chuck/Charles, Peggy/Margaret, Bill/William, Ted/Theodore, Jack/John.A LinkedIn URL gives a later email or phone lookup a specific person
identifier. Verify the URL before you use it as input.
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. type/deepline-gtm 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?
An email address gives the provider a specific lookup key. A name-and-company search can return more than one candidate. Compare the company, title, and location before you accept a candidate.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 the LinkedIn-optimized provider chain (person-linkedin-to-email) that has higher hit rates than name-based lookups.