Linkedin Search
Overview
The LinkedIn Search node looks up company or person data using LinkedIn-compatible enrichment. Use it to enrich workflows with firmographic or profile insights, helping you gather detailed information for sales, recruiting, or market research.
Description
Enrich data from LinkedIn.
Select a fetch type (company-fetch or person-fetch), then provide relevant fields (domain, company, first/last name, email, LinkedIn URL, etc.).
Company Fetch
Get details like employee count, revenue, and industry.
Person Fetch
Retrieve job titles, location, and contact info.
At least one search parameter must be provided for the selected fetch type.
Input Parameters
Provide the search criteria.
fetchTypestringRequired"company-fetch"domainstringOptionalcompanystringOptionalfirstNamestringOptionallastNamestringOptionalemailstringOptionallinkedinUrlstringOptionalOutput Parameters
The node returns detailed enrichment data.
name / fullNamestringOptionaldescription / profileSummarystringOptionalemployeesnumberOptionaljobTitlestringOptionallocationCitystringOptionallinkedinstringOptionalOutput Type
Output Type: JSON
The output is a JSON object containing all available enriched fields.
Example Usage
Example 1: Company Search
Find details about a company by domain.
{ "fetchType": "company-fetch", "domain": "google.com"}
{ "name": "Google", "domain": "google.com", "employees": 150000, "industry": "Internet", "founded": 1998}
Example 2: Person Search
Find a person by email.
{ "fetchType": "person-fetch", "email": "jane.doe@example.com"}
{ "fullName": "Jane Doe", "jobTitle": "Software Engineer", "company": "Example Inc.", "locationCity": "San Francisco"}
How to Use in a No-Code Workflow
Add the Node
Place the LinkedIn Search node in your enrichment flow.
Select Type
Choose company-fetch or person-fetch.
Map Inputs
Provide known details like domain or email from previous nodes (e.g., from a form submission).
Use Data
Map the output fields (like jobTitle or employees) to your CRM or database.
Best Practices
- Prefer exact domains for company lookups to avoid ambiguity.
- Combine multiple fields (Name + Company) for better person matches.
Do / Don’t
- ✔️ Use corporate emails for better person matching.
- ✔️ Check for
nullvalues in the output (data isn't always available).
- ❌ Don’t use personal emails (gmail, yahoo) if corporate ones are available.
- ❌ Don’t violate LinkedIn's terms of service or data privacy laws.
Common Errors
Insufficient parametersErrorOptionalNo resultsWarningOptionalExample Workflow Integration
Use Case: Lead Enrichment
Enrich new signup data with LinkedIn details.
- New Signup: User provides email and company name.
- LinkedIn Search: Fetch person details using email.
- Update CRM: Save job title and LinkedIn URL to CRM.
Workflow Data Flow:
{{signup.email}} → {{linkedinSearch.email}}
{{linkedinSearch.jobTitle}} → {{crm.update.title}}
