# LinkedIn Sales Navigator by Filters Scraper (`khadinakbar/linkedin-sales-navigator-filters-scraper`) Actor

Search public LinkedIn people using Sales Navigator-style filters: title, company, location, seniority, function, and exclude lists. Cookieless, no SN seat. MCP-ready.

- **URL**: https://apify.com/khadinakbar/linkedin-sales-navigator-filters-scraper.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** Lead generation, Social media, MCP servers
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 lead founds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn Sales Navigator by Filters Scraper

Turn Sales Navigator-style filters — job title, company, location, seniority, function, and exclude lists — into public LinkedIn lead rows. Paste `titleKeywords` such as `Head of Growth` and `locations` such as `San Francisco`, and get one dataset row per public `/in/` profile with name, headline, company, location, and profile URL. The default path is cookieless public search, so you can run it without a LinkedIn login or Sales Navigator seat. Filters that only exist inside logged-in Sales Navigator (headcount, posted-on-LinkedIn, SN geo codes) are listed on `droppedFilters` so you can see what public search honored.

This is the filter-first sibling of [LinkedIn Sales Navigator Scraper](https://apify.com/khadinakbar/linkedin-sales-navigator-scraper), which starts from an SN search URL. Use this Actor when an agent or operator has structured filters ready to paste.

### What you get

| Output | What it answers |
|---|---|
| `fullName`, `headline`, `currentCompany`, `location` | **Who** the public profile appears to be at work |
| `profileUrl`, `publicIdentifier` | **Where** to open the public LinkedIn page |
| `isEnriched`, `about`, `experience` | **Extra public fields** when enrichment is on |
| `searchQuery`, `discoverySource`, `droppedFilters` | **How** the public query was built and which SN-only filters were ignored |
| `OUTPUT` / `RUN_SUMMARY` outcomes | **Provenance** — complete, empty, invalid input, or upstream outage |

### Who it is for (and why it matters)

- **Sales development reps** — build a prospect list from title + location + company without buying a Sales Navigator seat.
- **Recruiters** — source public profiles that match seniority/function phrases, then export URLs to an ATS.
- **RevOps / growth teams** — keep include/exclude lists in the Actor input so the same ICP can rerun on a schedule.
- **AI agents** — call with `titleKeywords` and `locations`; inspect `outcome` and keep `profileUrl` values. There is no $0.50 search-init fee.

### When to use this Actor

- You have **filter criteria** (title, company names, location, seniority) and need public LinkedIn people rows.
- You want include **and** exclude lists in one MCP-friendly schema.
- You want an explicit `droppedFilters` field when an SN-only constraint stays outside public search.
- When you already have a Sales Navigator people-search URL, [LinkedIn Sales Navigator Scraper](https://apify.com/khadinakbar/linkedin-sales-navigator-scraper) is the URL-first decoder.
- When you already have `/in/` URLs, [LinkedIn Profile Details Scraper](https://apify.com/khadinakbar/linkedin-profile-details-scraper) enriches the public schema.org view.
- When the start is a work email, use [Email to LinkedIn Profile Scraper](https://apify.com/khadinakbar/email-to-linkedin-profile-scraper).

### Best fit for this Actor

- Strongest starting condition: a specific title phrase plus a city or company name that appears on public LinkedIn pages.
- Useful output: one billed row per unique public profile, cap 100 per run.
- Treat `maxResults` as a public-search cap (up to 100). Logged-in Sales Navigator exports can be larger; this Actor is sized for public `/in/` discovery.

### Practical scenario: SaaS SDRs in San Francisco

An SDR manager wants Heads of Growth at SaaS companies in San Francisco for a Q3 sequence. She sets `titleKeywords: ["Head of Growth"]`, `locations: ["San Francisco"]`, `keywords: "SaaS OR software"`, `titleKeywordsExclude: ["Intern"]`, and `maxResults: 25` with enrichment off. The Actor compiles a `site:linkedin.com/in` query, pages public search, and writes name, headline, company, location, and profile URL. She exports `profileUrl` into the CRM. Approximate event cost is 25 × $0.01. If she later needs about/experience, she reruns the same filters with `enrichProfiles: true`.

### Quick start input

```json
{
    "titleKeywords": ["Head of Growth"],
    "locations": ["San Francisco"],
    "maxResults": 5,
    "enrichProfiles": false
}
```

That input is the quality-test prefill: a real title + city pair that returns public `/in/` hits inside the five-minute window.

#### Example input — seniority plus exclude list

```json
{
    "titleKeywords": ["Director"],
    "currentCompanyNames": ["Stripe"],
    "locations": ["United States"],
    "seniorityLevels": ["Director", "Vice President"],
    "titleKeywordsExclude": ["Intern", "Student"],
    "maxResults": 25,
    "enrichProfiles": true
}
```

Seniority is approximated with public title phrases (Director, VP) and re-checked on the headline. Interns matching the exclude list are dropped and not billed.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `titleKeywords` | array | prefill Head of Growth | Current-title phrases to include |
| `currentCompanyNames` | array | empty | Employer names to include |
| `locations` | array | prefill San Francisco | City, region, or country names |
| `keywords` | string | empty | Extra boolean keywords |
| `schoolNames` | array | empty | Alumni school names |
| `firstName` / `lastName` | string | empty | Optional name filters |
| `titleKeywordsExclude` | array | empty | Title phrases to drop |
| `currentCompanyNamesExclude` | array | empty | Employers to drop |
| `locationsExclude` | array | empty | Locations to drop |
| `pastCompanyNames` / `pastJobTitles` | array | empty | Best-effort public-text extras |
| `seniorityLevels` | array | empty | Mapped to public title phrases |
| `functions` | array | empty | Mapped to public title phrases |
| `yearsOfExperience` / company / position | array | empty | Applied after enrichment |
| `changedJobsRecently` | boolean | false | Keep roles started in ~90 days (enrichment) |
| `salesNavigatorUrl` | string | empty | Optional SN people-search URL to decode |
| `maxResults` | integer | 25 | Cap 1–100 billed leads |
| `enrichProfiles` | boolean | false | Add public about/experience ($0.02/row) |
| `resultsRegion` | string | US | Google region code |
| `providerOrder` | enum | scrapecreators-first | Public-data provider priority |

At least one include filter or a valid SN people-search URL is required.

### What data you receive

One dataset item is one public LinkedIn person.

```json
{
    "fullName": "Jane Doe",
    "headline": "Head of Growth at Example",
    "currentCompany": "Example",
    "location": "San Francisco",
    "profileUrl": "https://www.linkedin.com/in/janedoe",
    "publicIdentifier": "janedoe",
    "isEnriched": false,
    "searchQuery": "site:linkedin.com/in \"Head of Growth\" \"San Francisco\"",
    "discoverySource": "scrapecreators",
    "scrapedAt": "2026-08-21T12:00:00.000Z"
}
```

Every terminal run also writes `OUTPUT` and `RUN_SUMMARY` with `outcome`, `itemsPushed`, `droppedFilters`, and billing counters.

### Use through the API

```bash
curl -X POST "https://api.apify.com/v2/acts/khadinakbar~linkedin-sales-navigator-filters-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "titleKeywords": ["Head of Growth"],
    "locations": ["San Francisco"],
    "maxResults": 5,
    "enrichProfiles": false
  }'
```

Results land in the run's default dataset: `https://api.apify.com/v2/datasets/{datasetId}/items?clean=true`. Paginate with `offset`/`limit`. The Actor is exposed through Apify MCP as `apify--linkedin-sales-navigator-filters-scraper`.

### Use with AI agents through Apify MCP

> Find public LinkedIn people who match Head of Growth in San Francisco. Return name, headline, company, location, and profile URL. Cap at 10 leads. Use structured filters rather than a Sales Navigator URL. Include droppedFilters in the summary when an SN-only constraint was skipped.

Inspect the terminal `outcome`, read the dataset, keep `profileUrl` as the source identifier, and treat `VALID_EMPTY` as a completed search with no public match. Connect through [Apify MCP](https://mcp.apify.com).

```json
{
    "titleKeywords": ["Head of Growth"],
    "locations": ["San Francisco"],
    "maxResults": 10,
    "enrichProfiles": false,
    "providerOrder": "scrapecreators-first"
}
```

Then keep `status=found` rows for outreach. For emails, pass `profileUrl` to [LinkedIn Profile Email Scraper](https://apify.com/khadinakbar/linkedin-profile-email-scraper) only when you already have the profile and need the reverse direction.

### Pricing

This Actor uses Pay per event plus Apify platform usage. Open the live Pricing tab for current event details, and use Apify's run cost controls to keep the workflow aligned with your budget.

| Event | Price | Charged when |
|---|---|---|
| Actor start | $0.00005 | Once per run (scaled by memory) |
| `lead-found` | $0.01 | One unique public lead saved |
| `lead-enriched` | $0.02 | Additional, only when enrichment succeeded |

Unqualified, excluded, and empty-search rows are not billed as `lead-found`. There is no per-search initiation fee.

| Run | Found rows | Enrichment | Event cost (approx.) |
|---|---|---|---|
| 5 Heads of Growth, search only | 5 | off | ~$0.05 |
| 25 Directors, search only | 25 | off | ~$0.25 |
| 25 Directors, enriched | 25 | on | ~$0.75 |

Platform usage is billed on top at Apify's rates. After you open this Actor, use the live [Pricing tab](https://apify.com/khadinakbar/linkedin-sales-navigator-filters-scraper/pricing) as the current event-price source of truth before you set a run budget.

### Best results

- Pair a **specific title** with a **city or company**. Title-only queries mix unrelated industries.
- Use exclude lists for Intern/Student instead of relying on seniority alone.
- Turn on `enrichProfiles` when you need about/experience or when tenure filters are set.
- After you have URLs, [LinkedIn Profile Details Scraper](https://apify.com/khadinakbar/linkedin-profile-details-scraper) is the next hop for the public about/experience view.
- For a saved SN URL rather than filters, use [LinkedIn Sales Navigator Scraper](https://apify.com/khadinakbar/linkedin-sales-navigator-scraper).

### Builder's note

Logged-in Sales Navigator people search stays outside ScrapeCreators and SociaVault — both vendors cover public LinkedIn profile, company, and post routes, plus Google search. The working public path is the same one used across this LinkedIn cluster: compile SN-style include/exclude fields into a `site:linkedin.com/in` dork, discover `/in/` URLs, optionally enrich the public profile, then keep only rows that pass exclude or tenure checks so billing stays aligned with useful leads. That is why this Actor is priced per lead, reports `droppedFilters`, and keeps headcount or “posted on LinkedIn” out of the advertised public contract.

### Responsible use

Use this Actor on public LinkedIn information you are authorized to process for legitimate sales, recruiting, or research. It reads **public web search results and public LinkedIn profile pages only**. The default path is cookieless public data. Follow GDPR, CCPA, CAN-SPAM, LinkedIn's terms, and any local law that applies to your outreach. Honor opt-out and do-not-contact requests.

This tool is provided for lawful public-data collection. You are responsible for how you use the output.

# Actor input Schema

## `titleKeywords` (type: `array`):

Current-title phrases to include, such as Head of Growth or VP Sales. Each value is quoted in the public search query. Up to 20 items. Combine with locations or currentCompanyNames to narrow. NOT a LinkedIn profile URL.

## `currentCompanyNames` (type: `array`):

Employer names to include, such as Stripe or Microsoft. Matched as public-profile text, not a private SN company ID. Up to 10 names. Leave empty for any company. NOT a company LinkedIn URL.

## `locations` (type: `array`):

City, region, or country names to include, such as San Francisco or United Kingdom. Matched against public location text. Up to 20 values. Leave empty for worldwide. NOT a Sales Navigator geo code.

## `keywords` (type: `string`):

Extra free-text added to the public search query. Supports Google-style operators such as fintech OR SaaS. Optional. Merged with decoded keywords from a Sales Navigator URL. NOT a profile URL.

## `schoolNames` (type: `array`):

University or school names to include, such as Stanford University. Quoted as phrases. Up to 10 values. Useful for alumni sourcing. NOT a degree name.

## `firstName` (type: `string`):

Optional first-name filter, such as Satya. Applied as a search token and re-checked on the parsed name. Leave empty to skip. NOT a full display name — use lastName for the family name.

## `lastName` (type: `string`):

Optional last-name filter, such as Nadella. Applied as a search token and re-checked on the parsed name. Leave empty to skip. NOT a company name.

## `titleKeywordsExclude` (type: `array`):

Title phrases to drop, such as Intern or Student. Applied as Google minus terms and as a post-filter on headline text. Up to 20 values. Leave empty to keep all titles. NOT an include list.

## `currentCompanyNamesExclude` (type: `array`):

Employers to drop, such as Staffing Agency. Applied as minus terms and a post-filter. Up to 10 names. Leave empty to keep all companies. NOT a company ID list.

## `locationsExclude` (type: `array`):

Locations to drop, such as Remote. Applied as minus terms and a post-filter. Up to 20 values. Leave empty to keep all locations. NOT a geo code.

## `pastCompanyNames` (type: `array`):

Former employers to search for as public text, such as Google. Public pages may not expose past roles, so this is a best-effort keyword. Up to 10 names. NOT a current-company include.

## `pastJobTitles` (type: `array`):

Former titles to search for as public text, such as CEO. Best-effort keyword only. Up to 20 values. NOT a current titleKeywords include.

## `seniorityLevels` (type: `array`):

Sales Navigator-style seniority buckets. Mapped to public title phrases (Director, VP, CEO) then re-checked on the headline. Multiple values are OR-ed. This is not LinkedIn's private seniority graph.

## `functions` (type: `array`):

Sales Navigator-style job-function buckets. Mapped to public title phrases such as Engineer or Account Executive, then re-checked on the headline. Multiple values are OR-ed. This is not LinkedIn's private function taxonomy.

## `yearsOfExperience` (type: `array`):

Tenure buckets applied after public-profile enrichment using experience dates. Forces enrichment on. Leads without dates are skipped and not billed. Multiple buckets are OR-ed. NOT a LinkedIn login filter.

## `yearsInCurrentCompany` (type: `array`):

Current-employer tenure buckets applied after enrichment. Forces enrichment on. Unenriched leads are skipped. Multiple buckets are OR-ed. Approximate from the current role start date.

## `yearsInCurrentPosition` (type: `array`):

Current-title tenure buckets applied after enrichment. Forces enrichment on. Unenriched leads are skipped. Multiple buckets are OR-ed. Approximate from the current role start date.

## `changedJobsRecently` (type: `boolean`):

When true, keep only leads whose current public role started within about 90 days. Forces enrichment on. Unenriched leads are skipped and not billed. Default false. This is not LinkedIn's private intent signal.

## `salesNavigatorUrl` (type: `string`):

Optional full URL from a LinkedIn Sales Navigator people search. Decoded title, company, location, school, and exclude labels are merged with the fields above. SN-only filters such as headcount are dropped with a warning. Prefer the filter fields when you do not have an SN URL. NOT a /in/ profile URL.

## `maxResults` (type: `integer`):

Maximum public leads to save and bill this run. Default 25, maximum 100. Public search depth is much smaller than a logged-in SN export. Prefill is 5 so quality tests finish quickly. NOT a page number.

## `enrichProfiles` (type: `boolean`):

When true, fetch public about, experience, education, skills, and follower counts. Adds $0.02 per successfully enriched lead on top of $0.01 found. Forced on when a tenure filter is set. Leave false for search-level name/headline/URL only.

## `resultsRegion` (type: `string`):

Two-letter country code for the Google search region, such as US or GB. Affects which localized public results surface. Defaults to US. NOT the person's location filter — use locations for that.

## `providerOrder` (type: `string`):

Which public-data provider to try first for Google discovery and optional profile enrichment. The other provider is the automatic fallback. Keep the default unless you specifically want SociaVault first.

## Actor input object example

```json
{
  "titleKeywords": [
    "Head of Growth"
  ],
  "locations": [
    "San Francisco"
  ],
  "changedJobsRecently": false,
  "maxResults": 5,
  "enrichProfiles": false,
  "resultsRegion": "US",
  "providerOrder": "scrapecreators-first"
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items containing name, headline, company, location, profile URL, and optional enrichment.

## `summary` (type: `string`):

Compact OUTPUT record with outcome, itemsPushed, chargedEventCounts, and droppedFilters.

## `runSummary` (type: `string`):

Detailed RUN\_SUMMARY diagnostics including discovery source, skipped filters, and billing counters.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "titleKeywords": [
        "Head of Growth"
    ],
    "locations": [
        "San Francisco"
    ],
    "maxResults": 5,
    "enrichProfiles": false,
    "resultsRegion": "US"
};

// Run the Actor and wait for it to finish
const run = await client.actor("khadinakbar/linkedin-sales-navigator-filters-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "titleKeywords": ["Head of Growth"],
    "locations": ["San Francisco"],
    "maxResults": 5,
    "enrichProfiles": False,
    "resultsRegion": "US",
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/linkedin-sales-navigator-filters-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "titleKeywords": [
    "Head of Growth"
  ],
  "locations": [
    "San Francisco"
  ],
  "maxResults": 5,
  "enrichProfiles": false,
  "resultsRegion": "US"
}' |
apify call khadinakbar/linkedin-sales-navigator-filters-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khadinakbar/linkedin-sales-navigator-filters-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/e0sB5zG7ztBXrk0hT/builds/2lWBlWOr2AsTSbf7i/openapi.json