LinkedIn Scraper · Recruiters & Sourcers
LinkedIn Scraper for Recruiters
Turn a candidate search into a spreadsheet you can actually work from. Paste the URL of a LinkedIn, Recruiter or Sales Navigator search and get every profile in the result set — name, current title, company, time in role, location and profile URL — with verified work emails and direct phone numbers added where they exist.
For: agency recruiters, in-house talent teams, sourcers and headhunters who run the same search again every time a role opens.
Works on a free LinkedIn account, Recruiter Lite, Recruiter or Sales Navigator. No card to start.
Quick answer
A LinkedIn scraper for recruiters exports the profiles in a candidate search into a structured file instead of making you open and copy them one at a time. Scrupp is a Chrome extension: you open a LinkedIn, Recruiter or Sales Navigator search, click Export, and it pages through the whole result set — LinkedIn itself stops a search at 2,500 rows, Scrupp keeps going — then looks up a work email and direct phone for each row and verifies the email against the receiving mail server before writing it out. Measured across all exports, a work email comes back for 36% of rows; rows where no address is found are not charged. Output is CSV, XLSX or a push to Google Sheets, Airtable, Notion or your CRM.
One at a time is the slow way. Export the whole LinkedIn, Recruiter or Sales Navigator search at once.
Sales Navigator stops a search at 2,500 rows. Scrupp keeps going and returns the whole list — name, title, company, verified email and phone in one CSV. A work email comes back for about 36% of rows, each one checked against the mailbox server before it reaches your file. Rows where no address is found are not charged.
What lands in the file
One row per candidate. The fields a sourcer actually screens on are read from the LinkedIn profile itself, so they are as current as that profile was at the moment of export.
From the profile
- Full name and headline
- Current title, company and company size
- Time in current role and at the company
- Location and country
- Profile URL, so you can reopen it in one click
- Whether the profile is open to InMail without a credit
Added by enrichment
- Work email, checked against the mail server at export
- A status on every address: valid, risky or not found
- Direct phone number where one exists
- Company domain, for your ATS to dedupe on
Five things recruiters use it for
These are the shapes of work we see most often in paying accounts doing recruiting.
A talent pool you can re-run, not rebuild
Save the search once. When the role reopens six months later, run it again and diff the new export against the old one — the arrivals are the people who moved into the title since. This is the case where exporting the whole result set instead of the first 2,500 rows changes the answer.
Shortlist screening in a spreadsheet
Sorting 900 profiles by time-in-role in a spreadsheet takes a minute. Doing the same by scrolling LinkedIn takes an afternoon, and you cannot share your place in it with a colleague.
Reaching candidates outside InMail
InMail credits run out and InMails go unread. With a verified work email and a direct number on the row you can pick the channel per candidate. A work address is the right channel for a passive candidate who never opens LinkedIn.
Mapping the team at a rival employer
Export everyone at a rival employer with a given title, and you have the org map for the role you are hiring against — who reports where, how long they have been there, who joined recently.
Working your own network first
Export your 1st-degree connections and filter them by title before you go looking at strangers. Cheapest candidates to reach are the ones who already accepted your request.
How the export runs
-
1
Build the search where you already build it
LinkedIn search, Recruiter, Recruiter Lite or Sales Navigator — whichever seat you have. Scrupp reads the search you are looking at; it does not ask you to rebuild your filters somewhere else.
-
2
Click Export
The extension pages through the results in your own browser session, at browsing speed rather than as fast as the network allows.
-
3
Enrichment runs on the rows
Each row is sent through a sequence of data providers for a work email and a phone. Every candidate address is then checked against the receiving mail server, and the verdict — valid, risky or not found — is written into the row.
-
4
Take the file
CSV or XLSX, or push to Google Sheets, Airtable, Notion, HubSpot or Pipedrive. If your ATS is not on that list, route the export through Zapier, Make or n8n, or call the REST API directly.
What the email side actually delivers
Worth knowing before you plan a campaign around it, so here it is without the rounding up. These are our own measured figures across all exports, not a segment estimate.
of exported rows come back with a work email
A work address exists to be found for some people and not others. Rows where nothing is found are not charged, so a thin search costs you less, not more.
confirmed by an accepted delivery
The gap between the two is addresses that pass a server check but have not yet been sent to. We publish both numbers rather than only the flattering one.
Two consequences for sourcing specifically. Candidates at large employers with predictable address patterns come back at a higher rate than candidates at small firms and consultancies. And a work address reaches someone at their current employer, which is fine for a passive approach and wrong for anything confidential — for those, the phone number on the row is the better field.
What you get out, and what this is not
The extracted profile data leaves as a comma-separated CSV, an Excel-ready XLSX, or JSON if you are calling the REST API and want to handle the search results in your own code. Every field you screen on is a column, so the same file works whether you open it in Excel, hand it to a colleague, or load it into an ATS.
What it is not is a LinkedIn automation tool. Scrupp does not send connection requests, does not drip InMails and does not run outreach sequences on your behalf — it does the data extraction and stops there. If you want to automate the outreach that follows, the export is designed to hand off cleanly: push it to your CRM, or route it through Zapier, Make or n8n into whatever sequencer or ATS you already run. Keeping scraping and sending in separate tools is also the safer arrangement for the LinkedIn account doing the searching.
Against the other ways to do this
| Approach | Whole result set | Email & phone | Where it hurts |
|---|---|---|---|
| Copying profiles by hand | In theory | No | The work scales with the list and cannot be handed over |
| LinkedIn Recruiter's own export | No — capped, and limited to saved projects | No personal or work email | You stay inside LinkedIn's messaging and its credit limits |
| LinkedIn automation tools PhantomBuster, Apify, Dux-Soup, Linked Helper, Waalaxy |
Usually, with setup | A separate email-finding tool, chained on | Built for connection requests and sequences; profile data extraction is the side job, and enrichment is a second subscription |
| Sales Navigator export tools Evaboot, Wiza |
Yes | Yes | Written for sales prospecting; nothing about them is wrong for sourcing, they just do not speak about it |
| A contact database | Its own index, not your search | Stored, not re-checked | A candidate who changed jobs is still listed at the old one |
| Scrupp | Yes, past LinkedIn's 2,500-row cap | In the same export, verified at export | A work email is found for about a third of rows, not all |
Not what you were after?
- Prospecting buyers rather than sourcing candidates → LinkedIn scraper for sales teams
- The scraper itself, without the role framing → LinkedIn scraper
- Exporting a Sales Navigator search specifically → Sales Navigator email finder
- Which LinkedIn seat you actually need → Sales Navigator vs Recruiter
- Pulling a list of open roles instead of people → LinkedIn job postings scraper
- Working a list you already have → CSV enrichment
Questions recruiters ask
Do I need LinkedIn Recruiter? ▾
No. Scrupp reads whatever search you can already see, so a free LinkedIn account works, as do Recruiter Lite, Recruiter and Sales Navigator. A paid seat gives you better filters, which makes a better list — but the export itself does not depend on it.
Does it get me personal email addresses? ▾
No. Enrichment looks for a work address at the company the person currently works for. There is no personal-inbox lookup, which also means a work address reaches a candidate where their employer can see it — use the phone number on the row when that matters.
What happens past 2,500 results? ▾
LinkedIn stops paging a search at 2,500 rows. Scrupp continues past that point and returns the rest of the result set, which is the difference that matters on a broad candidate search.
Will this get my LinkedIn account restricted? ▾
Scrupp runs in your own browser session and paces requests at human browsing speed rather than as fast as the connection allows. It is still your account taking the actions, so treat a brand-new account carefully and build volume up rather than starting at the top.
Can I push candidates straight into my ATS? ▾
Native integrations cover Google Sheets, Airtable, Notion, HubSpot and Pipedrive. For an ATS such as Greenhouse, Lever or Workable, export CSV or XLSX, or route the data through Zapier, Make or n8n, or call the REST API from your own code.
How is this different from the sales version of the page? ▾
The tool is the same; the job is not. Sourcing means re-running one search as roles reopen and screening on tenure and title. Outbound sales means one pass over a buyer list and pushing it to a sequencer. If you are prospecting buyers, the sales-teams page describes the workflow you want.
What does a row cost when no email is found? ▾
Nothing for the email. A row where no address is returned is not charged for enrichment, so a search in a segment with poor coverage costs you less rather than more.
Is exporting public LinkedIn data allowed? ▾
Scraping and how you then use personal data are two different questions, and the second one is the one that bites. If you are sourcing candidates in the EU or the UK, you need a lawful basis for contacting them and you must handle deletion requests — our GDPR page sets out how Scrupp handles data as a processor.
Run one search and see the file
Take a search you already use for an open role and export it. The free plan is enough to see what comes back before you decide anything.