LinkedIn Sales Navigator to Google Sheets, leads ready
If you’ve ever tried to move LinkedIn Sales Navigator leads into a spreadsheet, you know the routine. Click, copy, paste, fix broken columns, realize you missed a name, then do it again 50 times.
This Sales Navigator Sheets setup hits sales ops hard, but a recruiter building pipelines and a founder doing their own outbound feel it too. The payoff is simple: leads land in Google Sheets as clean rows, so outreach keeps moving.
Below, you’ll see how the workflow pulls contacts from a Sales Navigator search, paginates safely, and appends the details to your Sheet with rate limiting baked in.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: LinkedIn Sales Navigator to Google Sheets, leads ready
flowchart LR
subgraph sg0["Start Workflow Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Scrape LinkedIn Contacts API"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract Contact Data Array"]
n2@{ icon: "mdi:database", form: "rounded", label: "Save Contacts to Google Sheets", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check If More Pages Available", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Increment Page Start Parameter", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Rate Limit Delay Between Req..", pos: "b", h: 48 }
n6@{ icon: "mdi:play-circle", form: "rounded", label: "Start Workflow", pos: "b", h: 48 }
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Search Parameters", pos: "b", h: 48 }
n6 --> n7
n7 --> n0
n1 --> n2
n0 --> n1
n3 --> n4
n4 --> n5
n2 --> n3
n5 --> n7
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n6 trigger
class n3 decision
class n2 database
class n0 api
class n1 code
classDef customIcon fill:none,stroke:none
class n0,n1 customIcon
Why This Matters: Clean lead lists without copy-paste
Sales Navigator is great at finding people. It’s not great at turning those people into a usable list you can actually work from. Manually transferring contacts into a CRM or spreadsheet sounds “quick” until you do it for a full search: names in one place, titles in another, companies abbreviated, locations inconsistent, profile links missing. Then someone asks for the latest version, and you’re not sure which tab is real. It’s not the work that kills you. It’s the constant context switching and cleanup.
It adds up fast. Here’s where it breaks down.
- Copying 100 contacts into a Sheet can burn a couple hours, mostly on formatting and fixing columns.
- Small errors sneak in easily, like pasting the wrong profile URL or losing the company name when the page reloads.
- Your list goes stale because updating it feels painful, so outreach starts from outdated data.
- Teams end up with “shadow spreadsheets” because no one trusts the current export process.
What You’ll Build: Sales Navigator leads to Google Sheets automatically
This workflow takes a Sales Navigator search URL, pulls the contacts behind that search through a scraping API, and writes each result into Google Sheets as a clean, consistent row. You set your search once, paste in your LinkedIn cookies (kept private), and choose how many pages to capture. From there, n8n requests the next page, extracts the fields you actually care about (name, title, company, location, profile URL), and appends them to your sheet. It also slows itself down with a randomized delay so you don’t get blocked for “robot behavior.” Honestly, that rate limiting is the difference between “it worked once” and “it works every week.”
The workflow starts with your Sales Navigator search parameters. Then it loops through pages in batches, merging the results into one stream. Finally, Google Sheets receives the contacts in the right columns, ready for dedupe, scoring, and outreach.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you scrape a modest Sales Navigator list: 4 pages at about 25 contacts per page, so around 100 leads. Manually, even a quick process takes maybe 1 minute per lead once you include cleanup and checking profile links, which is about 2 hours. With this workflow, you spend about 10 minutes updating the search URL and cookies, then the automation runs with built-in delays (often around 30–60 seconds between requests). You still wait a bit, but you’re not doing the work.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- LinkedIn Sales Navigator for the saved search and filters.
- Google Sheets to store and share the lead list.
- Scraping API key (request it from the workflow creator).
Skill level: Intermediate. You’ll paste cookies, set an API header credential, and map Sheet columns.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
You provide a Sales Navigator search URL and cookies. The workflow uses your exported Sales Navigator cookies (from EditThisCookie) plus the exact search URL you want to scrape.
n8n requests contact data and walks through pages. An HTTP request hits the scraping API, then a loop processes page 1, page 2, and so on up to your total_pages setting.
Rate limiting slows things down on purpose. A randomized delay (commonly 30–60 seconds) is inserted between requests to reduce the chances of throttling or blocks.
Google Sheets receives clean rows. The workflow extracts contact fields, merges them into a consistent structure, and appends them to your chosen spreadsheet tab.
You can easily modify total_pages to scrape smaller or larger lists based on your needs. See the full implementation guide below for customization options.
Troubleshooting Tips
- Google Sheets credentials can expire or need specific permissions. If things break, check the connected Google account and spreadsheet access in the “Save Contacts to Google Sheets” node first.
- If you’re using Wait nodes or external scraping, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default field mapping is rarely perfect. If your team cares about industry, headcount, or seniority, add the right columns early or you’ll be cleaning the sheet later.
Quick Answers
About 30 minutes once you have the API key and your Sheet ready.
No. You’ll paste values, connect Google Sheets, and adjust a few fields.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in the scraping API subscription from the creator (1 month free trial is available).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management. Important note for this specific Sales Navigator Sheets workflow: it requires self-hosting because of cookie requirements and third-party API usage.
Yes, and you should. Swap the Sales Navigator search URL in the “Set Search Parameters” node to target a new segment, and adjust total_pages to control list size. You can also change the fields you write by editing the mapping in “Save Contacts to Google Sheets,” which is handy if you want extra columns for campaign name, lead owner, or a quick status like “Not contacted.”
Usually it’s the Google account permissions or the spreadsheet selection changing. Reconnect the Google Sheets credential in n8n, then re-select the spreadsheet and sheet inside the “Save Contacts to Google Sheets” node. If the sheet has different headers than the template, writes can fail or land in the wrong columns. Also check that you didn’t hit Google’s sharing limits on a team-owned file.
Practically, it’s driven by how many pages you set and how conservative your delay is. A common starting point is 2–10 pages per run (around 50–250 contacts), then you scale up once you’re confident it’s stable. If you self-host n8n there’s no execution cap, but your server and the scraping API will still have throughput limits, and going too fast is how you get blocked.
Often, yes, because this is not a typical “connector to connector” task. You’re dealing with cookies, pagination, rate limiting, and data shaping, which is where n8n tends to be more flexible and cost-effective. Zapier and Make can be fine for simple forms and CRM syncs, but they’re not built for this kind of controlled scraping flow. If you need help deciding, Talk to an automation expert and we’ll sanity-check your use case. A quick warning, though: this workflow specifically requires self-hosting, so a pure SaaS stack may not fit.
Once this is running, your lead list becomes something you can refresh on demand instead of rebuilding from scratch. The workflow handles the repetitive stuff, and you get back to actual outreach.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
