LinkedIn Lead Finder — Sales Navigator-Style Filters

What is LinkedIn Lead Finder — Sales Navigator-Style Filters?

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, 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 per-search initiation 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 is the URL-first decoder.
• When you already have /in/ URLs, LinkedIn Profile Details Scraper enriches the public schema.org view.
• When the start is a work email, use 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. That run is charged 25 lead-found events. If she later needs about/experience, she reruns the same filters with enrichProfiles: true.

Quick start input

{
    "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

{
    "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; for URL-first work use LinkedIn Sales Navigator Scraper
maxResults	integer	25	Cap 1–100 billed leads
enrichProfiles	boolean	false	Add public about/experience (one extra lead-enriched event per enriched row)
resultsRegion	string	US	Google region code

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.

{
    "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\"",
    "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

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.

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

Then keep status=found rows for outreach. For emails, pass profileUrl to LinkedIn Profile Email Scraper only when you already have the profile and need the reverse direction.

Pricing

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

Event	Charged when
apify-actor-start	Once per run (scaled by memory)
lead-found	One unique public lead saved
lead-enriched	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	Events charged
5 Heads of Growth, search only	5	off	1 start + 5 lead-found
25 Directors, search only	25	off	1 start + 25 lead-found
25 Directors, enriched	25	on	1 start + 25 lead-found + up to 25 lead-enriched

Apify platform usage is included in the event price. Check the Pricing tab for current prices 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 is the next hop for the public about/experience view.
• For a saved SN URL rather than filters, use LinkedIn Sales Navigator Scraper.

Builder's note

I built this on the public path because logged-in Sales Navigator people search sits outside the public-data providers, which 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.