LinkedIn Sales Navigator Scraper avatar

LinkedIn Sales Navigator Scraper

Pricing

from $10.00 / 1,000 lead founds

Go to Apify Store
LinkedIn Sales Navigator Scraper

LinkedIn Sales Navigator Scraper

Turn a LinkedIn Sales Navigator search URL into enriched public leads. Cookieless, no SN seat. Decodes SN filters + enriches profiles. MCP/API-ready.

Pricing

from $10.00 / 1,000 lead founds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

0

Bookmarked

28

Total users

25

Monthly active users

2 days ago

Last modified

Share

LinkedIn Sales Navigator Scraper turns a LinkedIn Sales Navigator people-search URL into enriched public leads. It is built for people who want a clean lead list from a Sales Navigator query, direct enrichment from LinkedIn profile URLs, or manual filters for public profile discovery. Each output record represents one public LinkedIn profile and can include name fields, headline, company, location, profile URL, public identifier, snippet, rank, about, experience, education, skills, connection and follower counts, enrichment status, and scrape timestamp. The result is a structured dataset of public leads that can be used in Apify runs, API workflows, and through Apify MCP.

Best fit and connected workflows

This Actor fits workflows where LinkedIn sourcing starts with a Sales Navigator people search and ends with structured public lead data.

Use it when you want to:

  • Convert a Sales Navigator search URL into public-profile leads with decoded filters.
  • Enrich a list of LinkedIn personal profile URLs into a consistent dataset.
  • Add public LinkedIn lead discovery to an Apify workflow, automation, or AI agent.
  • Use Combine upstream discovery from LinkedIn People Search Scraper or LinkedIn Company Search Scraper with this Actor for profile-level detail.

For connected workflows, the usual pattern is:

  1. Discover a company or people set in an upstream Actor.
  2. Pass verified public profile URLs into this Actor.
  3. Read the enriched dataset from Apify and hand it to CRM, research, or agent logic.

Practical scenario

Maya is building a prospect list for a growth team. She starts with a Sales Navigator people-search URL that targets a job title, region, and keyword set. After the run, she reviews fields such as fullName, headline, currentCompany, location, profileUrl, and isEnriched. She sees which profiles were enriched and which returned search-level public data only. Based on the headline, company, and profileUrl, she decides which leads belong in outreach and then sends the selected URLs to a follow-up enrichment or export step.

Input fields

Provide a Sales Navigator URL, direct profile URLs, or manual filters.

FieldTypePurpose
salesNavigatorUrlstringFull LinkedIn Sales Navigator people-search URL. The Actor decodes title, company, location, school, industry, and keyword filters from the URL.
jobTitlestringManual job-title filter used when no Sales Navigator URL is supplied.
locationstringManual city, region, or country filter.
currentCompanystringManual company filter for public profile matching.
schoolstringManual school or university filter for alumni sourcing.
keywordsstringFree-text keywords added to the Google query.
profileUrlsarray of stringsDirect LinkedIn personal profile URLs for enrichment.
enrichProfilesbooleanEnables deep public profile enrichment. Default: true.
maxResultsintegerMaximum leads to return, from 1 to 500. Default: 50.
resultsRegionstringGoogle region country code such as US, GB, or DE. Default: US.
preferProviderstringPrimary provider to try first: scrapecreators or sociavault. Default: scrapecreators.

Focused input example

{
"salesNavigatorUrl": "https://www.linkedin.com/sales/search/people?query=(filters:List((type:CURRENT_TITLE,values:List((text:Head%20of%20Growth,selectionType:INCLUDED))),(type:REGION,values:List((text:San%20Francisco%20Bay%20Area,selectionType:INCLUDED)))))",
"maxResults": 25,
"enrichProfiles": true,
"resultsRegion": "US",
"preferProvider": "scrapecreators"
}

Output fields

The dataset contains one record per public LinkedIn lead.

FieldTypeMeaning
fullNamestring or nullFull name from the public profile.
firstNamestring or nullFirst name.
lastNamestring or nullLast name.
headlinestring or nullPublic headline.
currentCompanystring or nullCurrent company when visible on the public profile.
locationstring or nullPublic location text.
profileUrlstring or nullCanonical LinkedIn personal profile URL.
publicIdentifierstring or nullLinkedIn profile slug.
snippetstring or nullSearch snippet captured during discovery.
rankinteger or nullResult rank in the search flow.
aboutstring or nullPublic About section from enrichment.
experiencearray or nullPublic experience entries from enrichment.
educationarray or nullPublic education entries from enrichment.
skillsarray or nullPublic skills from enrichment.
connectionsCountinteger or nullPublic connection count when available.
followerCountinteger or nullPublic follower count when available.
enrichmentSourcestring or nullProvider that returned the profile data.
isEnrichedboolean or nullWhether deep enrichment was applied.
scrapedAtstring or nullTimestamp recorded for the record.

Illustrative output record

{
"fullName": "Maya Chen",
"firstName": "Maya",
"lastName": "Chen",
"headline": "Head of Growth at ExampleCo",
"currentCompany": "ExampleCo",
"location": "San Francisco Bay Area",
"profileUrl": "https://www.linkedin.com/in/maya-chen/",
"publicIdentifier": "maya-chen",
"snippet": "Head of Growth at ExampleCo",
"rank": 1,
"about": "Growth leader focused on acquisition and lifecycle marketing.",
"experience": [
{
"title": "Head of Growth",
"company": "ExampleCo"
}
],
"education": [
{
"school": "Stanford University"
}
],
"skills": [
"Growth Strategy",
"Lifecycle Marketing"
],
"connectionsCount": 500,
"followerCount": 1200,
"enrichmentSource": "scrapecreators",
"isEnriched": true,
"scrapedAt": "2026-01-01T12:00:00.000Z"
}

How it works

This Actor uses public-data workflows and is cookieless.

  1. It reads your input in one of three modes:
    • Sales Navigator URL
    • direct LinkedIn profile URLs
    • manual filters
  2. When a Sales Navigator URL is provided, it decodes the visible people-search filters such as title, company, location, school, industry, and keywords.
  3. It finds matching public LinkedIn profiles through Google-based discovery.
  4. It enriches public profiles with full public data when enrichProfiles is enabled.
  5. It uses scrapecreators first by default, with sociavault available as the alternate provider.
  6. It writes one dataset item per lead and also exposes a dataset link in the run output.

The run output includes a leads dataset URL that points to the cleaned JSON items for the run.

Pricing

This Actor uses Apify Pay per event pricing plus Apify platform usage.

Charged events include:

  • Actor start
  • Lead found
  • Lead enriched

A run that finds several leads and enriches each one is billed by event count, so total cost depends on how many leads are discovered and how many are enriched. For example, a run that finds fifty leads and enriches each of them will include fifty Lead found events and fifty Lead enriched events, plus one Actor start event. For current pricing details, open the live Pricing tab on the Apify store page.

Use with AI agents (MCP)

This Actor is available through Apify MCP as a tool for sourcing public LinkedIn lead records from a Sales Navigator search URL, a profile-URL list, or manual filters.

Exact Actor identity: khadinakbar/linkedin-sales-navigator-scraper

A practical agent prompt:

Find public LinkedIn leads from this Sales Navigator people search URL, enrich the profiles, and return the dataset items with name, headline, company, location, profile URL, and enrichment status.

How to interpret the output:

  • fullName, headline, currentCompany, and location help an agent summarize each lead.
  • profileUrl provides the provenance link back to the public profile.
  • isEnriched shows whether the record includes deeper public profile data.
  • about, experience, education, skills, connectionsCount, and followerCount are the enriched fields when present.

Scope and provenance:

  • The Actor works from public LinkedIn profile data.
  • It does not rely on a LinkedIn login session.
  • If the Sales Navigator URL includes filters that live only inside Sales Navigator, the Actor decodes the public-search-relevant parts and continues from there.

Pagination and cost guidance:

  • Set maxResults to control how many leads the Actor returns.
  • Each additional discovered lead adds event-based cost.
  • Turning off enrichProfiles returns faster search-level records at the lower lead-found event rate.

Apify API example

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({
token: process.env.APIFY_TOKEN,
});
const run = await client.actor('khadinakbar/linkedin-sales-navigator-scraper').call({
jobTitle: 'Head of Growth',
location: 'San Francisco',
maxResults: 10,
enrichProfiles: true,
});
const datasetId = run.defaultDatasetId;
const { items } = await client.dataset(datasetId).listItems({ clean: true });
console.log(items);

Best results and outcome guidance

Use a Sales Navigator people-search URL when you already have a structured query in LinkedIn Sales Navigator. Use direct profileUrls when you already have a lead list and want enrichment. Use manual filters when you are building a public search from scratch.

A few practical guidelines:

  • Keep maxResults aligned with the size of the list you need.
  • Use resultsRegion to localize Google discovery.
  • Keep preferProvider on the default unless you have a reason to route through the alternate provider first.
  • Use enrichProfiles: false when you only need fast search-level records.
  • Use the enriched fields when you want profile context for research, routing, or qualification.

Design note

I found the output contract includes a single dataset link named leads, which makes the run result easy to hand off to another Apify step or an AI agent without guessing where the records live.

FAQ

When should I use the Sales Navigator URL field?

Use salesNavigatorUrl when you already have a LinkedIn Sales Navigator people search and want this Actor to decode that query into public lead discovery.

When should I use profileUrls?

Use profileUrls when you already have LinkedIn personal profile links and want direct enrichment instead of search.

How does this connect to other Apify Actors?

A common workflow is to discover leads with LinkedIn People Search Scraper or discover company records with LinkedIn Company Search Scraper, then pass verified public profile URLs into this Actor for enrichment.

What fields are most useful for routing leads?

fullName, headline, currentCompany, location, and profileUrl are the core routing fields. isEnriched helps you see whether deeper public profile details were added.

How does the pricing model work?

LinkedIn Sales Navigator Scraper uses Pay per event on Apify. Lead discovery and profile enrichment are billed as separate events, and platform usage is part of the Apify run. Check the live Pricing tab for the current billing details.

Responsible use

This Actor works with public LinkedIn profile data surfaced through public search and profile pages. Use the output in a way that respects applicable laws, platform terms, and privacy obligations. Review your internal policies for lawful basis, retention, access controls, and deletion handling before using lead data in downstream systems.