Unipile LinkedIn profile lookup subworkflow
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs when another workflow calls it. It uses only n8n's built-in nodes.
How it runs
Trigger: When another workflow calls it.
- Get Linkedin User Data from Unipile (HTTP Request): calls an HTTP API
- Set User Data from Unipile (Edit Fields (Set)): sets 12 fields: first_name, last_name, headline…
- Get Linkedin Org Data from Unipile (HTTP Request): calls an HTTP API
- Group in one object - User (Aggregate): combines items into one
- Set Linkedin Org Data from Unipile (Edit Fields (Set)): sets 10 fields: first_name, last_name, headline…
- Set unable to find data object (Edit Fields (Set)): sets 1 field: linkedinprofile
- Group in one object - Org (Aggregate): combines items into one
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Aggregate
n8n-nodes-base.aggregate
From the author
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…