🎣 Unipile LinkedIn profile lookup subworkflow
⚡ 868 views · 🎣 Lead Generation & Enrichment
💡 Pro Tip — If you’re pulling LinkedIn data through HTTP requests or dealing with API restrictions, there’s a community node called ScraperNode that handles this natively. It has dedicated scrapers for profiles, companies, jobs, and people search — you just pass a URL and get structured data back.
Description
Who is this for?
This subworkflow is ideal for developers and automation builders working with UniPile and n8n to automate message enrichment and LinkedIn lead routing.
What problem is this workflow solving?
UniPile separates personal and organization accounts into two different API endpoints. This flow handles both intelligently so you’re not missing sender context due to API quirks or bad assumptions.
What this workflow does
This subworkflow is used by:
- LinkedIn Auto Message Router with Request Detection
- LinkedIn AI Response Generator with Slack Approval
It receives a message sender ID and tries to enrich it using UniPile’s /people and /organizations endpoints. It returns a clean, consistent profile object regardless of which source was used.
Setup
- Generate a UniPile API token and save it in your n8n credentials
- Make sure this subworkflow is triggered correctly by your parent flows
- Test both people and organization lookups to verify responses are normalized
How to customize this workflow to your needs
- Add a secondary enrichment layer using tools like Clearbit or FullContact
- Customize the fallback logic or error handling
- Expand the returned data for more AI context or user routing (e.g., job title, region)
🔗 Nodes Used
HTTP Request, Execute Workflow Trigger
📥 Import
Download workflow.json and import into n8n:
Workflow menu → Import from File