Enrich LinkedIn leads in Google Sheets with PhantomBuster, Hunter and Dropcontact
Ready for 3.0What this workflow does
This workflow has 32 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Sheets, Phantombuster, Hunter and Dropcontact.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- ⚙️ Pipeline Configuration (Edit Fields (Set)): sets 7 fields: GOOGLE_SHEET_ID, PHANTOMBUSTER_PROFILE_AGENT_ID, PHANTOMBUSTER_COMPANY_AGENT_ID…
- 📋 Read Leads from Google Sheets (Google Sheets): uses Google Sheets
- 🔍 Filter Unprocessed Leads (Code): runs custom JavaScript code
- ⚡ Process in Batches (5 at a time) (Loop Over Items (Split in Batches)): loops over the items in batches
- 🔔 Notify Slack on Batch Complete (HTTP Request): calls an HTTP API (POST)
- ✅ Validate LinkedIn URL Format (Code): runs custom JavaScript code
- 🔀 Route: Valid URL? (If): checks a condition and branches into true / false
- 🚀 Launch: LinkedIn Profile Scraper (Phantombuster): uses Phantombuster
- ⚠️ Mark: Invalid URL (Edit Fields (Set)): sets 3 fields: enrichment_status, error_message, processed_at
- Wait: waits 60 seconds
…plus 20 more steps. See the full node list below.
Services it uses
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 (12)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Phantombuster
n8n-nodes-base.phantombuster - Wait
n8n-nodes-base.wait - Hunter
n8n-nodes-base.hunter - Dropcontact
n8n-nodes-base.dropcontact
From the author
Quick Overview This workflow reads LinkedIn profile URLs from Google Sheets, enriches each lead using PhantomBuster profile and company scrapers, finds a work email via Hunter.io with a Dropcontact fallback, writes results back to Google Sheets, and posts…