Scrape targeted leads from Google Maps & LinkedIn to Supabase using Apify
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs when someone submits an n8n form (“Targeted leads”). Along the way it connects Supabase and Apify (community).
How it runs
Trigger: When someone submits an n8n form (“Targeted leads”).
- Route source (Switch): routes items into 3 branches
- googlemaps_dataset (Apify): run actor and get dataset
- linkedin_dataset (Apify): run actor and get dataset
- set_google_maps_column (Edit Fields (Set)): sets 14 fields: title, categoryName, address…
- get_linkedin (Edit Fields (Set)): sets 13 fields: publicIdentifier, linkedinUrl, name…
- save_googlemaps (Supabase): uses Supabase
- save_linkedin (Supabase): uses Supabase
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in linkedin_dataset, googlemaps_dataset).
Nodes used (5)
- Supabase
n8n-nodes-base.supabase - Edit Fields (Set)
n8n-nodes-base.set - Apify
@apify/n8n-nodes-apify.apify - Switch
n8n-nodes-base.switch - n8n Form Trigger
n8n-nodes-base.formTrigger
From the author
Who's it for This template is perfect for sales teams, marketing professionals, recruiters, and business development specialists who need to efficiently collect targeted lead data from multiple sources. Whether you're building prospect lists, conducting…