# LinkedIn Email Finder — LinkedIn URL to Email, Bulk (`b2bsearch/linkedin-email-finder`) Actor

LinkedIn email finder: paste LinkedIn profile URLs, get the email addresses on record — recorded addresses, not pattern guesses. $8 per 1,000 profiles with an address at their current employer; $3 when only older company addresses exist, labelled as such. Nothing found = free row.

- **URL**: https://apify.com/b2bsearch/linkedin-email-finder.md
- **Developed by:** [B2B Enrich Search](https://apify.com/b2bsearch) (community)
- **Categories:** Lead generation, Social media, AI
- **Stats:** 5 total users, 5 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 emails founds

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

> **$8 per 1,000 profiles with an address at their current employer. $3 per
> 1,000 when only older company addresses are on record. Nothing found is a
> free row.** Recorded addresses, not pattern guesses.

Paste LinkedIn profile URLs and get the email addresses on record for each
person, from a database of 800M+ professional profiles. Most "email finder"
tools guess `first.last@company.com`; this one returns only addresses that
exist in the person's record, and says so for free when there are none.

### Why this one

1. **Priced by whether the address still works.** A record often carries
   addresses from past jobs, board seats and alumni accounts. An address on
   the domain of the person's **current** employer is sold at $8 per 1,000;
   when only other company addresses exist, the row ships labelled
   `work_other` at $3 per 1,000.
2. **Company addresses by default, personal mailboxes on request.** Turn on
   `includePersonalEmails` to also get gmail, outlook and ISP mailboxes; a
   profile with one then counts at the $8 price.
3. **Misses are free.** A matched profile with nothing on record is a free
   `no_email` row that still names the person, so you can route them to
   [Work Email Finder](https://apify.com/b2bsearch/work-email-finder).

### Who is this for

- Outbound teams turning lists of profile links into send-ready addresses.
- Recruiters contacting sourced candidates outside the platform inbox.
- RevOps filling CRM contacts that carry a profile URL but no email.

### How often it finds an address

Measured on 30 September 2026 over 200 people per country who hold a current
position with a B2B title (manager, director, engineer, sales, head, founder,
consultant, analyst):

| Country | Current employer's address ($8 / 1,000) | Only older company addresses ($3 / 1,000) | No company address (free) | Personal mailbox (with `includePersonalEmails`) |
|---|---|---|---|---|
| United States | 24% | 40% | 37% | 44% |
| France | 20% | 31% | 49% | 28% |
| India | 18% | 24% | 58% | 31% |
| United Kingdom | 16% | 38% | 46% | 23% |
| Germany | 16% | 36% | 49% | 20% |

Most records carry addresses from earlier jobs, which is why they are sold
separately and labelled `work_other`: they reach an inbox the person may no
longer read. Your own list will score differently. Senior titles and larger
employers usually score higher.

### Input

```json
{
  "profileUrls": ["satyanadella"],
  "includePersonalEmails": false
}
```

Links, bare handles and mobile URLs all work; spellings of the same profile
are looked up once. Up to 1,000 profiles per run.

### Output

A found row (addresses made up):

```json
{
  "_status": "found",
  "_input": { "profile": "jane-doe-example" },
  "_freshness": "fresh_90d",
  "fullName": "Jane Doe",
  "jobTitle": "VP Engineering",
  "companyName": "Acme",
  "profileUrl": "https://www.linkedin.com/in/jane-doe-example",
  "email": "jane.doe@acme.example",
  "emailType": "work_current",
  "workEmails": ["jane.doe@acme.example", "jdoe@oldjob.example"],
  "emailCount": 2
}
```

`emailType` is `work_current` (the current employer's domain), `personal`
(when you asked for personal mailboxes) or `work_other` (a company address
we cannot tie to the current employer: usually an earlier job, sometimes a
brand whose mail domain differs from its name). Current-employer addresses
sort first in `workEmails`.

A profile that matched but has nothing to sell:

```json
{
  "_status": "no_email",
  "_input": { "profile": "some-handle" },
  "fullName": "Jane Smith",
  "jobTitle": "VP Engineering",
  "companyName": "Acme",
  "_note": "a personal mailbox is on record — run with includePersonalEmails to get it"
}
```

The `_note` appears only when a personal mailbox is on record and you did
not ask for personal mailboxes.

### Pricing

| Event | Price | When |
|---|---|---|
| Email found (current employer or personal) | $0.008 | an address on the current employer's domain, or a personal mailbox when asked for |
| Email found (other work address) | $0.003 (free until 14 October 2026) | only company addresses we cannot tie to the current employer |
| Matched, nothing on record | **$0** | free row with name, title and employer |
| Not found / removed / invalid | **$0** | always free |

### FAQ

**Where do the addresses come from?** From the contact block of the
person's record: publicly available professional data. Nothing is generated
or guessed.

**Can it check that an address delivers?** Not in this Actor. Work Email
Finder has an optional check for name + domain lookups.

**How fresh is the data?** Every row carries a `_freshness` bucket
(`fresh_90d`, `updated_1y`, `older`).

**Bigger lists?** Up to 1,000 URLs per run; for 10,000+ use
[Bulk People Enrichment](https://apify.com/b2bsearch/bulk-people-enrichment)
with `contacts` on.

### Use LinkedIn Email Finder with AI agents and MCP

This Actor works as a tool for AI agents. Add it to Claude, ChatGPT, Cursor or any other MCP client through the Apify MCP server:

```
https://mcp.apify.com?tools=b2bsearch/linkedin-email-finder
```

- **Fast enough for a tool call.** A small request finishes in seconds, so the agent gets its answer inside one call.
- **The agent pays only for results.** Prices are per result (see the pricing section above) and every miss is a free row. Cap what one call may spend with `maxTotalChargeUsd`.
- **Rows explain themselves.** Each row has a `_status`; a row that is not a result says why in `_error`, so the agent can decide what to do next without guessing.

Input an agent can send as is:

```json
{
  "profileUrls": [
    "satyanadella"
  ]
}
```

The same Actor is available as a tool in LangChain, CrewAI and the OpenAI Agents SDK, and as a step in n8n, Make and Zapier through the Apify integrations.

### Which actor in this family?

One database, ten doors. Misses are free on every one of them.

| Actor | Input → output |
|---|---|
| [Profile Lookup](https://apify.com/b2bsearch/profile-lookup) | profile URL → full career profile |
| [Reverse Email Lookup](https://apify.com/b2bsearch/reverse-email-lookup) | email → person, profile URL and employer |
| [Name to Profile](https://apify.com/b2bsearch/name-to-profile) | name + company domain → profile |
| [Social Handle Lookup](https://apify.com/b2bsearch/social-handle-lookup) | GitHub, X/Twitter or Facebook handle → profile |
| [Bulk People Enrichment](https://apify.com/b2bsearch/bulk-people-enrichment) | CSV of emails, URLs, handles or names → profiles |
| **LinkedIn Email Finder** (this one) | profile URL → email addresses on record |
| [Work Email Finder](https://apify.com/b2bsearch/work-email-finder) | name + company domain → work email candidates |
| [Company Employees](https://apify.com/b2bsearch/company-employees) | company domain → current staff |
| [People Database Search](https://apify.com/b2bsearch/people-database-search) | filters → people |
| [Company Database Search](https://apify.com/b2bsearch/company-database-search) | filters → companies |

### Disclaimer

This Actor is an independent product. It is not affiliated with, endorsed by
or sponsored by LinkedIn. It does not access, crawl or scrape any of them at
run time: answers come from our own database of publicly available
professional data, and the network names only describe the kind of data it
covers. To have a person's data removed, open an issue on this Actor with only
the profile link — nothing else is needed, and it is removed from every listing.

# Actor input Schema

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

One LinkedIn profile URL or bare handle per line. $8 per 1,000 profiles with an address on the current employer’s domain (or a personal mailbox, if you include them); $3 per 1,000 when only other company addresses exist, labelled work\_other. Nothing on record is a free "no\_email" row; an unmatched URL is a free "not\_found" row.

## `includePersonalEmails` (type: `boolean`):

Off by default: the finder returns company addresses. Turn it on to also receive personal mailboxes on record; a profile with one then counts as found at $8.00 per 1,000.

## Actor input object example

```json
{
  "profileUrls": [
    "satyanadella"
  ],
  "includePersonalEmails": false
}
```

# Actor output Schema

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

No description

# 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 = {
    "profileUrls": [
        "satyanadella"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("b2bsearch/linkedin-email-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 = { "profileUrls": ["satyanadella"] }

# Run the Actor and wait for it to finish
run = client.actor("b2bsearch/linkedin-email-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 '{
  "profileUrls": [
    "satyanadella"
  ]
}' |
apify call b2bsearch/linkedin-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,b2bsearch/linkedin-email-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/aaQmB1hxDtRxhCUtX/builds/4mkh9xMgVDHenveN4/openapi.json