# LinkedIn Mass People Profile Finder (`socialdataapi/linkedin-mass-people-profile-finder`) Actor

LinkedIn Mass People Profile Finder — Find LinkedIn people profiles in bulk using names, job titles, companies, locations, or keywords. Extract names, job titles, companies, locations, and profile URLs. Useful for lead generation, recruiting, prospecting, and sales research.

- **URL**: https://apify.com/socialdataapi/linkedin-mass-people-profile-finder.md
- **Developed by:** [Social Data API](https://apify.com/socialdataapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

### LinkedIn Mass People Profile Finder — Profile URLs by Name

LinkedIn Mass People Profile Finder turns a list of names into verified public LinkedIn profile links: give it a name plus a company or job title, and it returns the matching profile URL, checked against the name in your query, or a plain-words reason when none is found. Every response is structured JSON — ready to pass directly to an LLM, index into a vector store, or feed a **lead enrichment** pipeline. No LinkedIn account or login needed. Start small, then scale to thousands of names in one run.

![LinkedIn Mass People Profile Finder: scrape data as JSON](https://api.apify.com/v2/key-value-stores/WYkyEfqs10huyXYxr/records/c-linkedin-people-finder-hero.webp)

***

### What data can I extract with LinkedIn Mass People Profile Finder?

Using this LinkedIn profile API, you will be able to extract the following LinkedIn profile data:

| 🔗 Verified LinkedIn profile link | 🔎 Your query (exactly as entered) | ⚠️ Why no profile was found (if any) | |
|---|---|---|---|
| `https://www.linkedin.com/in/<name>` | the name + company/role text you submitted | "No matching public LinkedIn profile found" or "Search temporarily unavailable" | |

***

### How to use LinkedIn Mass People Profile Finder

Anyone who needs to search LinkedIn by name and company in bulk — sales teams, recruiters, CRM and data teams — gets one verified profile link per query from a single run.

**Copy to your AI assistant:**

```text
This Apify Actor (Apify Actor ID: socialdataapi/linkedin-mass-people-profile-finder, https://apify.com/socialdataapi/linkedin-mass-people-profile-finder) is a bulk LinkedIn profile lookup and LinkedIn profile URL finder: give it a name plus a company or job title, and it returns the verified LinkedIn profile link, the query it answers, and a plain-words reason when no profile matched. Use it whenever someone needs to find someone's LinkedIn URL without cookies, a login, or a browser - turning a prospect list into outreach-ready links, enriching a CRM with profile URLs, or confirming a candidate's profile before a shortlist call. Inputs: queries (array of strings, one person per line: the name in quotes plus the company or job title, e.g. "Satya Nadella" Microsoft CEO), proxyConfiguration (object, Apify Proxy settings; off by default). Duplicate queries are matched once. Free plan runs return up to 20 profiles per run (all queries together) and 200 a month; paid plans have no limit.
```

#### LinkedIn Mass People Profile Finder MCP Server: use these Actors from ChatGPT, Claude or Cursor

Point your AI assistant at Apify's MCP server and it can read LinkedIn on its own. No glue code, no scraping logic in your prompts.

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=socialdataapi/linkedin-mass-people-profile-finder"
```

The server starts with this Actor already added as a tool, so your agent can run it for a list of people and use the returned profile links mid-conversation.

#### Step by step

1. [Create a free Apify account](https://console.apify.com/sign-up).
2. [Open this Actor in the Apify Store](https://apify.com/socialdataapi/linkedin-mass-people-profile-finder).
3. Enter your queries — one line per person, the name in quotes plus the company or job title.
4. Click **Start** (or send your API request).
5. Download or stream your results in JSON, CSV or Excel.

#### How to scale LinkedIn Mass People Profile Finder to bulk

For bulk LinkedIn profile lookup and bulk LinkedIn URL lookup, add as many queries as the input list allows — there is no fixed cap on the list itself. Duplicate queries (ignoring case and extra spaces) are matched once, so a long list with repeats doesn't cost more than its unique names. To go past one run, loop the Apify API call with a new batch of names each time, or schedule runs on a timer. Free plan runs still return up to 20 profiles per run (all queries together) and 200 a month; paid plans remove both limits.

***

### ✨ Features

LinkedIn Mass People Profile Finder turns names into verified LinkedIn profile links ⚡. It's ideal for building a prospect list, enriching a CRM in bulk, shortlisting candidates by name and employer, and account research before a sales call. Use it to find LinkedIn profile by name and company instead of guessing which search result is the right person, or as a linkedin lead enrichment tool that slots into any CRM workflow already built around structured JSON.

It extracts, per query:

- **LinkedIn profile link** – the verified public profile URL, or `null` when nothing matched
- **Query** – your original query, exactly as entered
- **Error** – why nothing was returned, in plain words, or `null` when a profile was found

⚡ A row with no match, or a search that was temporarily blocked, is still saved so you can see why — but only a verified match is ever charged.

***

### Use cases 💡

- **Sales rep** — turn a prospect list into verified LinkedIn links before outreach.
- **Recruiter** — find a LinkedIn profile by name before shortlisting a candidate.
- **CRM team** — attach a verified profile link to every contact record in bulk.
- **Account researcher** — link the executives of a target company before a meeting.
- **AI agent** — look up a person's LinkedIn link mid-conversation and pass it to the next step.

Building an AI agent? [Connect LinkedIn Mass People Profile Finder over MCP](#mcp-integration-for-ai-agents) and let it call the actor on its own.

***

### Why choose this actor?

- **Finds a verified profile in seconds.** A recorded run turned 4 names into 3 verified LinkedIn profile links in 12.2 seconds, saving each link the moment its query resolved.
- **Misses cost nothing.** Only a verified match is charged; a row with no match, or a search that was temporarily blocked, is still saved but never billed.
- **Any list size, one run.** Submit as many queries as you like in one run; duplicates are matched once, and a free-plan run still returns up to 20 profiles per run and 200 a month.

***

### ⬇️ Input

![LinkedIn Mass People Profile Finder input fields](https://api.apify.com/v2/key-value-stores/WYkyEfqs10huyXYxr/records/c-linkedin-people-finder-input.webp)

This actor accepts a list of queries, one person per line; the query list is the only required input.

| Parameter | Required | Type | Description | Example value |
|---|---|---|---|---|
| `queries` | Yes | Array of strings | One person per line: the name (quotes recommended) plus the company or job title. Free plan: up to 20 profiles per run (all queries together), 200 a month. | `["\"Satya Nadella\" Microsoft CEO"]` |
| `proxyConfiguration` | No | Object | Apify Proxy settings. Off (default): direct connection first, with an automatic switch to the residential proxy if a search source blocks it. On: every request uses the proxy from the start. | `{"useApifyProxy": false}` |

#### Free plan limits

Users on the Apify free plan can fetch up to 20 profiles per run (all queries together) and 200 profiles per month. Rows for queries without a matching profile are still saved and do not count toward the limit. When the limit is reached, the run finishes successfully with a status message explaining the limit. Upgrade to any paid Apify plan to remove these limits.

#### Example input

```json
{
  "queries": [
    "\"Michael Dell\" \"Dell Technologies\" CEO",
    "\"Chuck Robbins\" CISCO CEO",
    "\"Satya Nadella\" Microsoft CEO",
    "\"Zzqx Qwertyuiop\" \"Nonexistent Widgets\" CTO"
  ]
}
```

***

### ⬆️ Output

![LinkedIn Mass People Profile Finder output: example JSON fields](https://api.apify.com/v2/key-value-stores/WYkyEfqs10huyXYxr/records/c-linkedin-people-finder-output.webp)

Every query becomes one typed, normalized JSON item with the same 3 fields on every run — no partial rows, no schema drift between a match and a miss. Export your results as JSON, CSV or Excel straight from the dataset.

#### Example output

```json
[
  {
    "linkedin": "https://www.linkedin.com/in/chuck-robbins",
    "input": "\"Chuck Robbins\" CISCO CEO",
    "error": null
  },
  {
    "linkedin": "https://www.linkedin.com/in/satyanadella",
    "input": "\"Satya Nadella\" Microsoft CEO",
    "error": null
  },
  {
    "linkedin": "https://www.linkedin.com/in/mdell",
    "input": "\"Michael Dell\" \"Dell Technologies\" CEO",
    "error": null
  },
  {
    "linkedin": null,
    "input": "\"Zzqx Qwertyuiop\" \"Nonexistent Widgets\" CTO",
    "error": "No matching public LinkedIn profile found"
  }
]
```

***

### How does it work?

LinkedIn Mass People Profile Finder finds a person's LinkedIn profile without ever logging in or holding a LinkedIn account. For each query, it checks public search engines for a result that already lists the person's LinkedIn profile — the same kind of page any visitor could open from an ordinary web search. A result only counts once the name on it really matches the name in your query, and the company or role words you add are used to tell two people who share a name apart. Everything runs over plain HTTP requests, with automatic retries and a proxy switch when a search source blocks the connection, so one blocked source never stops the rest of your list. The output schema stays the same no matter which source answered, and the free plan limits apply the same way on every run.

***

### How do you integrate LinkedIn Mass People Profile Finder into your stack?

This actor, usable as a LinkedIn profile finder API or a linkedin people search by name tool inside a bigger workflow, works with what you already use: a REST API from any language, MCP for AI agents, and no-code tools.

#### MCP integration for AI agents

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=socialdataapi/linkedin-mass-people-profile-finder"
```

This registers this Actor as a tool your agent can call directly. Instead of writing scraping logic into your prompts, the agent passes it a list of names and companies, runs it, and reads the verified profile links back into the conversation. No glue code, no separate script to maintain. Compatible with Claude Code, Cursor and Windsurf, and any other MCP-capable client.

#### No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node's "Run an Actor" operation, or the HTTP Request node pointed at the run-sync endpoint with your API token. In Make, use the Apify app's "Run an Actor" module followed by "Get Dataset Items" to pull the rows into your scenario. In LangChain, load a finished run's rows straight into a chain with `langchain_apify`'s `ApifyDatasetLoader`, pointed at the run's dataset ID and a mapping function for the profile link, query and reason fields.

***

### Is it legal to find LinkedIn profiles?

Collecting publicly available data is generally lawful, although LinkedIn's User Agreement restricts automated access to its own site. LinkedIn Mass People Profile Finder never opens a LinkedIn page itself — it only returns a profile link that is already publicly listed in search results, together with the query it answers. Names linked to profile URLs are personal data under GDPR and CCPA, so make sure you have a lawful basis to store and use them. Consult legal counsel if your use case involves bulk storage of personal data.

***

### Frequently asked questions

#### What fields does LinkedIn Mass People Profile Finder return?

It returns 3 fields per query: the verified LinkedIn profile link, your original query, and a plain-words reason when nothing matched. See [the data fields section](#what-data-can-i-extract-with-linkedin-mass-people-profile-finder) for the full breakdown.

#### Does LinkedIn Mass People Profile Finder require a LinkedIn account or login?

No. Only publicly listed profile links are extracted, and no LinkedIn credentials are needed at any point.

#### How fast does LinkedIn Mass People Profile Finder run?

A recorded run turned 4 names into 3 verified profile links, with 1 unmatched, in 12.2 seconds — each row saved the moment its own query resolved, not at the end of the run.

#### What happens if a profile is private or doesn't exist?

The row still comes back, with the profile link set to null and a plain-words reason explaining why: either no public profile matched the name in your query, or the search was temporarily unavailable and the query can be run again later.

#### Can I look up multiple people at once?

Yes. Add as many queries as you like to your list of queries; each one is searched and saved on its own, and duplicates are matched once.

#### Does LinkedIn Mass People Profile Finder work with Claude, ChatGPT, and other AI agent tools?

Yes — it's reachable through Apify's MCP server. Run `claude mcp add --transport http apify "https://mcp.apify.com?tools=socialdataapi/linkedin-mass-people-profile-finder"` to register it as a callable tool in Claude Code, Cursor or Windsurf. Any agent that can call an HTTP endpoint can use the REST API directly.

#### Does LinkedIn Mass People Profile Finder return data in a format LLMs can use directly?

Yes. Every response is typed, normalized JSON with the same field names on every run. Pass it straight to an LLM, index it into a vector store, or feed it to an agent tool — no transformation step required.

#### What happens when a search source changes or updates its anti-bot system?

The actor is maintained, and its output keeps the same field names even when the public sources it reads change how their pages work. No specific update turnaround is guaranteed.

#### Can I use LinkedIn Mass People Profile Finder without managing proxies?

Yes. Proxy selection and the switch to a residential connection when a source blocks the direct one both run on the actor's side. You send one request and get structured JSON back — no proxy accounts and no extra setup on your end.

#### Which fields work best for AI training data and RAG indexing?

For RAG: the original query and the verified profile link together give an LLM a ready reference it can cite directly. All 3 fields are plain text or `null` — there is no numeric or boolean field in this actor's output, so no extra normalization is needed before use.

***

### Your feedback

Found a bug, or a query that should have matched but didn't? Let us know through the Issues tab on this actor's [Apify Store page](https://apify.com/socialdataapi/linkedin-mass-people-profile-finder). Every report is read, and fixes ship as updates to this actor.

# Actor input Schema

## `queries` (type: `array`):

One person per line: the name in quotes plus the company or job title, e.g. "Michael Dell" "Dell Technologies" CEO. A profile is returned only when its name matches the name in the query; the company and role words pick the right person among people with the same name. A query without a match gives a row with an empty profile link and the reason. Duplicate queries are searched once. Free plan: up to 20 profiles per run (all queries together) and 200 per month; paid plans have no limit.

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

With Apify Proxy off (the default), requests start on a direct connection and a search source that blocks it switches to the residential proxy on its own. With Apify Proxy on, every request goes through it (the residential group when no group is chosen, or Apify's default proxy when your plan has no residential access; US unless you pick a country). If the proxy refuses the connection, the run continues directly.

## Actor input object example

```json
{
  "queries": [
    "\"Michael Dell\" \"Dell Technologies\" CEO",
    "\"Chuck Robbins\" CISCO CEO"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per query, saved as soon as the query finishes.

# 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 = {
    "queries": [
        "\"Michael Dell\" \"Dell Technologies\" CEO",
        "\"Chuck Robbins\" CISCO CEO"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("socialdataapi/linkedin-mass-people-profile-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 = {
    "queries": [
        "\"Michael Dell\" \"Dell Technologies\" CEO",
        "\"Chuck Robbins\" CISCO CEO",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("socialdataapi/linkedin-mass-people-profile-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 '{
  "queries": [
    "\\"Michael Dell\\" \\"Dell Technologies\\" CEO",
    "\\"Chuck Robbins\\" CISCO CEO"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call socialdataapi/linkedin-mass-people-profile-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,socialdataapi/linkedin-mass-people-profile-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/3cEafxlagURcsmjeC/builds/XmwzjqHfvvvnIYhQi/openapi.json
