n8n LinkedIn Scraper
n8n cannot scrape LinkedIn on its own — it has no scraping node, and its official LinkedIn node uses LinkedIn's API for posting, not for reading profiles. The working shape is a split: the scrape happens in your browser session, and n8n gets the finished rows. Two ways to wire it, both below.
Quick answer
How Scrupp pushes LinkedIn leads into n8n
To scrape LinkedIn with n8n, do not look for a scraper node — there isn't one, and anything that paged through LinkedIn from your server would put the account at risk anyway. Split the job instead. Route 1, push: Scrupp reads the LinkedIn or Sales Navigator search inside your own browser session, finds a work email and phone for each row, and POSTs every enriched lead to an n8n Webhook trigger. Route 2, pull: an n8n HTTP Request node calls the Scrupp REST API to enrich a contact, verify an email or start an export, so the workflow drives the run on a schedule. Either way the limit to plan around is LinkedIn's own: one search pages to 2,500 rows. Across all exports a work email comes back for 36.3% of rows and 10.0% are confirmed by an accepted delivery, so size the downstream nodes for roughly a third of the rows carrying an address — not all of them.
3-step setup
From install to first n8n record in 2 minutes
One-time connection, then every export is a single click.
In n8n, add the Webhook node, set the method to POST and copy the Production URL (webhook/<id>). This is the endpoint that will receive each scraped LinkedIn row.
In Scrupp settings → Webhooks, paste the n8n URL; Scrupp sends a ping to verify it. Then run your LinkedIn or Sales Navigator search and export it — every enriched row fires the workflow as it lands, rather than at the end.
If the workflow should drive the run, skip the webhook: point an HTTP Request node at the Scrupp REST API to enrich a row or start an export on a schedule. Useful for nightly CRM top-ups where nobody is at the browser.
Add an IF node on the email field. Rows with a verified address go to the sequencer; rows without go to a list for a different play. Skipping this step is what makes a sequence look like it is bouncing when it is really sending to empty rows.
Use cases
What teams do with Scrupp + n8n
Common workflows that plug Scrupp into n8n without custom code.
Export the search once, let n8n route each row: enrich, dedupe against the CRM, create the record, notify the owner in Slack. The part no node can do — reading the search — happens in the browser; everything after it is a workflow.
Self-hosted n8n means the rows never pass through a third-party automation cloud. That is usually the deciding factor for EU teams and regulated industries, and it is the one thing Zapier and Make cannot offer.
Self-hosted n8n has no per-execution charge, so a workflow that fires once per exported row costs the same at a thousand rows as at ten. Agencies running continuous outbound are the usual case.
Chain the export into your own scoring endpoint, then into the CRM, then into Slack — and drop into a Function node with JavaScript wherever the visual nodes run out.
FAQ
n8n integration FAQ
Does n8n have a LinkedIn scraper node?
No. n8n ships an official LinkedIn node, but it works through LinkedIn's API and is built for posting, not for reading profiles or search results. There is no node that pages through a Sales Navigator search, which is why the scrape has to happen in a browser session and reach n8n as data.
Can n8n scrape LinkedIn directly with an HTTP Request node?
Technically it can fetch a URL, and practically it is a bad idea: requests from a server have no logged-in session, hit the authentication wall, and the pattern is exactly what gets accounts restricted. The split — scrape in the browser, process in n8n — exists because of that, not because of a missing feature.
Is there an n8n LinkedIn scraper template?
The reusable part is the receiving half: a Webhook trigger, an IF node on the email field, and whatever CRM or sequencer node you use. Build it once and every export feeds it, because the payload shape is the same each run.
How do I get Sales Navigator leads into n8n?
Run the Sales Navigator search, export it with Scrupp, and have the webhook deliver each enriched row to the workflow. One search pages to 2,500 rows — LinkedIn's own cap — so audiences larger than that need splitting by function or location before the export, not after.
Push or pull — which should I use?
Push (webhook) when a person is running searches and the workflow should react. Pull (HTTP Request on a schedule) when nobody is at the browser and the job is a recurring top-up of records you already hold. Both can run against the same account.
What does a row look like when it arrives?
JSON with the profile fields — name, title, company, profile URL — plus the email and phone where they were found, each with a verification status. Rows where nothing was found still arrive, with the contact fields empty and a status saying so, and those rows are not charged.
Do I need n8n Cloud, or is self-hosted enough?
Self-hosted is enough and is what most teams use: unlimited executions at fixed cost and the data never leaves your infrastructure. n8n Cloud is a managed convenience for teams without ops capacity.
Related integrations
Keep exploring: Google Sheets · HubSpot · Zapier · Webhook
Wire one search into n8n and watch the rows arrive
The scrape runs in your browser, the workflow does the rest. Free plan, and rows with no address found are not charged.
Free Chrome extension · No credit card · Works with any n8n tier