# LinkedIn People Finder — by Title, Company, Location (No Login) (`inovaflow/linkedin-people-finder`) Actor

Find people on LinkedIn by job title, company, location or keyword and read their public profiles. One row per person: name, headline, current title and company, location, education, connections, profile link, plus experience and followers when the profile is public. No login, no cookies.

- **URL**: https://apify.com/inovaflow/linkedin-people-finder.md
- **Developed by:** [inovaflow](https://apify.com/inovaflow) (community)
- **Categories:** Lead generation, Social media, Business
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 people

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**Find people on LinkedIn by job title, company, location or keyword — name, headline, current role, company, location, education and profile link, plus the public profile when LinkedIn shows it. No login, no cookies, $1 per 1,000 people.**

If you prospect on LinkedIn, you know the two bad options: pay for a people-search tool that costs a few cents per profile, or hand your own LinkedIn cookies to a scraper and hope the account survives. Yet the facts you need to decide whom to contact — who holds which role at which company in which city — are already public: every profile has a public page, and the search engines index it with the headline, the current company, the location, the education and the connection count right in the result.

We built this for our own outbound and use it daily: describe who you are looking for, and the Actor runs the searches, keeps only people who really match, reads the public profile page where LinkedIn offers one to a logged-out visitor, and gives you one clean row per person. Nothing of yours is involved. Now we're sharing it.

### Who it's for

- **Sales and lead-gen teams** — *"CTOs of fintech companies in Prague"*, *"heads of growth in Berlin"*.
- **Recruiters and sourcers** — *"machine learning engineers at these 20 companies"*.
- **Founders and partnership teams** — *"who works at Stripe in developer relations?"*
- **Account-based marketing** — *"the people at our target accounts, with role and location, as a table"*.
- **AI agents and pipelines** — *"people matching a role × company × city grid, as flat JSON"*.

### What you can enter

| Input | Example | What happens |
|---|---|---|
| **Job titles × companies × locations** | `CTO` × `Prague`, `Head of Growth` × `Stripe` | Every combination becomes one search; add **keywords** that every search must include |
| **Free-text searches** | `"Head of Growth" Berlin SaaS` | Used as written; quotes keep a phrase |
| **Profile links** | `https://www.linkedin.com/in/jancurn/`, `jancurn` | The public profile page, or the person's public search snippet when LinkedIn does not show the page |

**Each row:** name (first / last), headline, current title and company (with the company's LinkedIn link when the page shows it), location and country code, education, connections, profile link, the search that found the person, and — when LinkedIn shows the profile to a logged-out visitor — about text, follower count, the full experience list (title, company, dates, duration, location), education history, websites and avatar. `profileVisibility` says what you got: `public` (full page), `limited` (page shown with parts masked), `not-public` (LinkedIn shows the page only to members — the search row stands), `not-read` (you switched page reads off).

### Options that matter

- **Maximum people per search** — Brave Search lists about 20 profiles per query form and the Actor tries up to three forms per search; for more people, split by city, seniority or sub-industry.
- **Read the public profile pages** — on by default; turn off for a fast search-only run.
- **Only people who match the search** — on by default: a person is kept only when the search words really appear in their name, headline, role, company, location, education or snippet (quoted phrases always, at least half of the loose words). Search engines pad thin queries; this keeps the padding out of your data and off your bill.
- **Headline / company / location contains** — plain filters on the delivered rows.
- **Also search Google** — off by default; the paid, slower second engine through Apify's Google SERP proxy.

### How to set it up

1. Enter job titles, companies, locations and keywords (or free-text searches), and/or profile links.
2. Set the maximum people per search.
3. Run. Rows land in the dataset as each search finishes; the status message and the `OUTPUT` record say what every search returned, how many profile pages were public, and why anything was unavailable.

### Pricing

Pay per result: **$0.001 per person** ($1 per 1,000), plus the platform's start fee ($0.005 per GB of memory, one unit at the default 512 MB). People removed by the relevance check or your filters, duplicates and empty runs are never charged.

### Notes

- **No account, no cookies.** Everything comes from public search results and LinkedIn's public profile pages.
- **Which profiles are public.** LinkedIn shows a full public page for some members (typically prominent ones), a page with masked parts for others, and nothing at all to logged-out visitors for many. The search row (name, headline, company, location, education, connections) is there in every case; `profileVisibility` tells you which.
- **No emails or phone numbers.** They are not public. Pair this Actor with an email finder on the name + company.
- **Proxies.** Searches and pages go through Apify's datacenter proxy; a rate-limited request switches to the residential proxy by itself.

# Actor input Schema

## `jobTitles` (type: `array`):

Roles to find (`CTO`, `Head of Growth`, `founder`). Combined with every company and location below into one search each.

## `companies` (type: `array`):

Company names to find people at (`Apify`, `Stripe`). Without titles you get people at these companies.

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

Cities, regions or countries (`Prague`, `Berlin`, `Germany`).

## `keywords` (type: `array`):

Extra words every search must include (`fintech`, `machine learning`).

## `searchQueries` (type: `array`):

Your own searches, one per line, used as written (`"Head of Growth" Berlin SaaS`). Quotes keep an exact phrase.

## `profileUrls` (type: `array`):

Specific profiles to read (`https://www.linkedin.com/in/jancurn/` or just `jancurn`). Profiles LinkedIn does not show to logged-out visitors are described from their public search snippet instead.

## `maxPeoplePerQuery` (type: `integer`):

Cap per search (each title × company × location combination is one search). Brave Search lists about 20 profiles per query form; the Actor tries up to three forms.

## `readProfiles` (type: `boolean`):

Open each person's public profile as a logged-out visitor to add the about text, follower count, experience and education history, websites and avatar. LinkedIn shows public profiles only for some people (`profileVisibility` tells you which); the search row is delivered either way. Turn off for a faster, search-only run.

## `mustMatchQuery` (type: `boolean`):

Search engines pad thin queries with loosely related profiles. Keep only people whose name, headline, company, location, education or snippet actually contains the search words (quoted phrases always, at least half of the loose words).

## `titleContains` (type: `array`):

Keep only people whose headline or current title contains one of these words (`founder`, `engineer`).

## `companyContains` (type: `array`):

Keep only people whose current company contains one of these words.

## `locationContains` (type: `array`):

Keep only people whose location contains one of these words (`Prague`, `Czechia`, `Berlin`).

## `useGoogleSearch` (type: `boolean`):

Continue on Google through Apify's Google SERP proxy when more people are wanted than Brave returned. Each result page is paid and Google often answers with a page that cannot be read.

## `maxConcurrency` (type: `integer`):

How many profile pages are read at the same time.

## `proxyConfiguration` (type: `object`):

Searches and public profiles open through Apify's datacenter proxy (the default); a rate-limited request switches to the residential proxy by itself. Nothing to change here normally.

## Actor input object example

```json
{
  "jobTitles": [
    "CTO"
  ],
  "companies": [],
  "locations": [
    "Berlin"
  ],
  "keywords": [],
  "searchQueries": [],
  "profileUrls": [],
  "maxPeoplePerQuery": 20,
  "readProfiles": true,
  "mustMatchQuery": true,
  "titleContains": [],
  "companyContains": [],
  "locationContains": [],
  "useGoogleSearch": false,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `people` (type: `string`):

One row per person: name, headline, current title and company, location, education, connections, profile link, and the public-profile fields when LinkedIn shows them.

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

People delivered and charged, the per-search report, filters applied, search-engine and proxy statistics.

# 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 = {
    "jobTitles": [
        "CTO"
    ],
    "companies": [],
    "locations": [
        "Berlin"
    ],
    "keywords": [],
    "searchQueries": [],
    "profileUrls": [],
    "maxPeoplePerQuery": 20,
    "titleContains": [],
    "companyContains": [],
    "locationContains": [],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("inovaflow/linkedin-people-finder").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 = {
    "jobTitles": ["CTO"],
    "companies": [],
    "locations": ["Berlin"],
    "keywords": [],
    "searchQueries": [],
    "profileUrls": [],
    "maxPeoplePerQuery": 20,
    "titleContains": [],
    "companyContains": [],
    "locationContains": [],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("inovaflow/linkedin-people-finder").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 '{
  "jobTitles": [
    "CTO"
  ],
  "companies": [],
  "locations": [
    "Berlin"
  ],
  "keywords": [],
  "searchQueries": [],
  "profileUrls": [],
  "maxPeoplePerQuery": 20,
  "titleContains": [],
  "companyContains": [],
  "locationContains": [],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call inovaflow/linkedin-people-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,inovaflow/linkedin-people-finder"
        }
    }
}
```

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/HunUPJbVxzk9T3MC1/builds/MCCpUr5BJYxSUb1Yn/openapi.json