LinkedIn Decision Makers Scraper - CEOs, Founders & Executives avatar

LinkedIn Decision Makers Scraper - CEOs, Founders & Executives

Pricing

$2.00 / 1,000 results

Go to Apify Store
LinkedIn Decision Makers Scraper - CEOs, Founders & Executives

LinkedIn Decision Makers Scraper - CEOs, Founders & Executives

Find CEOs, founders, CTOs, recruiters, and other decision makers from public LinkedIn profiles using β€” no LinkedIn login or cookies required πŸš€

Pricing

$2.00 / 1,000 results

Rating

5.0

(1)

Developer

Hamza

Hamza

Maintained by Community

Actor stats

4

Bookmarked

175

Total users

20

Monthly active users

6.8 hours

Issues response

a day ago

Last modified

Share

What does LinkedIn Decision Makers Scraper do?

Discover public LinkedIn profile search results using job titles, company or industry keywords, and locations. The Actor searches Google SERPs through Decodo Fast Search and exports profile URLs, names, snippets, and available profile fields without LinkedIn login.

Search results follow Google's ranking and indexing. A profile appearing in a search does not establish that every requested criterion describes its current employment or residence. Search words can appear in past experience, education, or other profile text.

Why use it?

Use profile search results to research executives, discover founders, build an initial outreach research list, or find people associated with a company keyword. You can run the Actor manually, schedule searches, or use the API tab to connect it to your workflow.

The paid route searches pages concurrently, removes duplicate profile URLs, and retains available results when individual provider requests fail. The maximum result count is a limit, rather than a guaranteed number of profiles.

What data can it extract?

FieldDescription
fullName, firstName, lastNameName from the search title; first/last split is best effort.
headlineProfile headline visible in the search title.
currentRole, companyRole and employer inferred from visible search text.
locationProfile location supported by the search snippet.
linkedinUrlCanonical LinkedIn profile URL.
snippetOriginal search description for reviewing the evidence.
fieldSourcesText source used to infer each populated profile field.
jobTitleSearched, industryKeyword, locationKeywordRequested search terms, rather than verified profile attributes.

Role, company, and location values are best-effort extractions, not independently verified facts from live LinkedIn profiles. Unsupported values remain null. This Actor does not retrieve profile photos; profileImage is retained as null for export compatibility.

How to search LinkedIn profiles

  1. Enter one or more job titles, such as CEO or Founder.
  2. Optionally add industry/company keywords and cities, regions, or countries.
  3. Choose the maximum profile count and search language.
  4. Run the Actor and review the dataset's headlines and snippets before using the records.

See the Input tab for the full configuration options. For example:

{
"jobTitles": ["CEO"],
"searchKeywords": ["SaaS"],
"locations": ["Berlin"],
"maxResults": 200,
"language": "en",
"deduplicateResults": true
}

The corresponding query includes site:linkedin.com/in "CEO" "SaaS" "Berlin". There is one SERP discovery flow, with no additional matching modes.

Output

You can download the dataset as JSON, CSV, Excel, or HTML. This fictional example illustrates populated fields and an incomplete search hit:

[
{
"fullName": "Jane Example",
"headline": "CEO at Example Software",
"currentRole": "CEO",
"company": "Example Software",
"location": "Berlin",
"linkedinUrl": "https://www.linkedin.com/in/jane-example",
"snippet": "Location: Berlin Β· SaaS software",
"jobTitleSearched": "CEO",
"industryKeyword": "SaaS",
"locationKeyword": "Berlin"
},
{
"fullName": "Alex Example",
"headline": "Founder",
"currentRole": "Founder",
"company": null,
"location": null,
"linkedinUrl": "https://www.linkedin.com/in/alex-example",
"snippet": "Founder Β· SaaS products",
"jobTitleSearched": "CEO",
"industryKeyword": "SaaS",
"locationKeyword": "Berlin"
}
]

Speed, cost, and provider setup

The default paid engine is Decodo Fast Search. It uses five concurrent page requests, up to twenty pages per query, two attempts per page, and a shared sixty-second discovery budget. Google redirect recovery sends no Decodo credentials to Google and does not fetch LinkedIn pages. Provider availability and query relevance affect speed and yield.

Actor charges, compute, and proxy usage depend on the pricing displayed in Apify Console. Decodo requests also consume the provider account's allowance. The free Actor route is capped at ten profiles and uses the Apify Google SERP proxy; the paid route allows up to five hundred profiles per run.

Actor owners should follow APIFY-SETUP.md to configure the provider secret. Regular Decodo scraping is an explicit alternative using its separate endpoint and credentials; it is slower and is not the default.

FAQ and support

Why are some fields empty? Search snippets omit or truncate information. The Actor keeps the profile hit and leaves unsupported fields empty instead of filling them with requested search terms.

Why did I receive fewer profiles than requested? The provider may return fewer unique profiles within the search page/time limits. Failed pages are retried briefly; available records are retained. Invalid credentials or failure of every provider page fails the run clearly.

Does it verify current employment? It infers fields from public search text. Review the snippets and verify current details before outreach. Historical snippet fragments are not used to fill a current location.

Use the Issues tab to report a problem with the input, run log, and an example output row. Never include provider tokens in support messages.