# LinkedIn Email Finder - Work Emails, No Login (`thirdwatch/linkedin-email-finder-scraper`) Actor

Generate likely work email addresses from public LinkedIn profiles or name and company domain pairs, with MX validation and optional verification.

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

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn Email Finder — Profile URL to Email (No Login)

Generate likely work email addresses from LinkedIn profile URLs or name-and-domain pairs. **No login, cookies, or Sales Navigator seat.** Every result includes ranked candidates and an explicit confidence/verification status so an inferred address is never presented as guaranteed.

Works inside Claude, ChatGPT, and any MCP-compatible agent via the Apify connector. Pairs cleanly with [LinkedIn Employees Scraper](https://apify.com/thirdwatch/linkedin-company-employees-scraper) — run that first to build a target list, then this to fill in emails.

### Two input modes

#### Mode 1 (recommended): Direct contacts

Best for high-volume prospecting. Provide name + domain (or name + company); the actor skips LinkedIn entirely. **This is the right path when chaining from [LinkedIn Employees Scraper](https://apify.com/thirdwatch/linkedin-company-employees-scraper)** — that actor outputs name + company already.

```json
{
  "contacts": [
    {"firstName": "Jane", "lastName": "Doe", "domain": "stripe.com"},
    {"fullName": "John Smith", "company": "Acme Inc", "companyUrl": "https://acme.com"}
  ]
}
```

#### Mode 2: Profile URLs (best-effort)

Supply LinkedIn profile URLs. The actor attempts to fetch each profile for name + company; falls back to URL-slug parsing if LinkedIn's authwall blocks the fetch. **Use `domainOverride` to guarantee a usable domain** when LinkedIn fetch fails.

```json
{
  "profiles": [
    "https://www.linkedin.com/in/jane-doe-12a/",
    "https://www.linkedin.com/in/jsmith-acme/"
  ],
  "domainOverride": "stripe.com"
}
```

### How it works

1. **Extract name + company** — JSON-LD from LinkedIn's public profile page (no login needed)
2. **Resolve domain** — from LinkedIn company website, then heuristic fallback
3. **Generate candidates** — 11 common B2B patterns weighted by real-world frequency: `first.last`, `first`, `flast`, `first_last`, etc.
4. **Verify** — MX lookup + optional SMTP RCPT TO probe with catch-all detection
5. **Rank** — verified > catch\_all > pattern + MX > pattern only

### Output

| Field | Description |
|---|---|
| `fullName` | Person's name |
| `firstName` / `lastName` | Parsed name parts |
| `company` | Current employer (from LinkedIn) |
| `domain` | Derived company domain |
| `primaryEmail` | Best-guess email |
| `candidates` | All weighted candidates `[{email, weight}]` |
| `verificationStatus` | `verified` / `catch_all` / `mx_only` / `no_mx` / `smtp_blocked` / `skipped` |
| `confidence` | `verified` / `catch_all` / `pattern` / `pattern_no_mx` / `low` |
| `verifiedEmails` | Emails the SMTP server accepted |
| `mxHosts` | Mail servers found via DNS |
| `catchAll` | Whether the domain accepts all addresses |
| `profileUrl` | Original LinkedIn URL |

### Verification reality check

SMTP verification works when:

- The target domain's MX accepts inbound connections from our IP
- It returns clear 550-style rejects for unknown addresses (not all do)

When SMTP probing is blocked (port 25 outbound restrictions, greylisting, catch-all configs) the actor falls back to MX-validated pattern guessing. **Pattern-based confidence is ~60-70% on real B2B domains** — high enough for warm outbound, low enough you should still bounce-test before mass sending.

### Pricing

You are charged only when the Actor returns a `primaryEmail`; empty lookups are free. Tiered FREE/BRONZE/SILVER/GOLD pricing is **$0.005 / $0.004 / $0.003 / $0.002 per email candidate**. Candidate generation, MX lookup, and optional SMTP evidence are included.

### Compared to alternatives

| Tool | Cost | Login required | Verification |
|---|---|---|---|
| This actor | From $0.002/email candidate; empty lookups free | No | MX + optional SMTP |
| Hunter.io | $0.049/search | API key | Yes |
| Apollo | $99/mo seat | Account | Yes |
| Snov | $0.027/credit | API key | Yes |

### Tips

1. **Pair with LinkedIn Employees Scraper** — run it first for prospect lists, then feed profile URLs here.
2. **Use `domainOverride`** when LinkedIn shows a parent brand but you want subsidiary emails.
3. **Enable `verifyEmails`** only when you want SMTP evidence. It is off by default because many mail servers block probes.
4. **Always bounce-test before mass sending** — pattern matches without SMTP verification still bounce 30–40% of the time.

Last verified: 2026-07

More scrapers at [thirdwatch.dev](https://thirdwatch.dev).

# Actor input Schema

## `profiles` (type: `array`):

List of LinkedIn profile URLs (e.g. https://www.linkedin.com/in/username/). The actor fetches each profile to extract name and current company, then derives the most likely work email. Use this OR the 'contacts' field below.

## `contacts` (type: `array`):

Pre-extracted contacts as objects with firstName, lastName, and either company or domain. Skips the LinkedIn fetch entirely (cheaper). Example: \[{"firstName":"Jane","lastName":"Doe","domain":"stripe.com"}].

## `domainOverride` (type: `string`):

Force all lookups to use this domain (e.g. 'stripe.com'). Useful when LinkedIn shows a parent brand but you want subsidiary emails.

## `verifyEmails` (type: `boolean`):

Attempt SMTP RCPT TO verification for top candidates. Availability depends on the recipient mail server and network policy; MX validation always remains available.

## `maxResults` (type: `integer`):

Cap total profiles processed across all inputs.

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

Apify proxy configuration. Residential recommended for LinkedIn fetches to maximise success.

## Actor input object example

```json
{
  "profiles": [
    "https://www.linkedin.com/in/satyanadella/"
  ],
  "contacts": [],
  "domainOverride": "",
  "verifyEmails": false,
  "maxResults": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "profiles": [
        "https://www.linkedin.com/in/satyanadella/"
    ],
    "maxResults": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("thirdwatch/linkedin-email-finder-scraper").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 = {
    "profiles": ["https://www.linkedin.com/in/satyanadella/"],
    "maxResults": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("thirdwatch/linkedin-email-finder-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "profiles": [
    "https://www.linkedin.com/in/satyanadella/"
  ],
  "maxResults": 10
}' |
apify call thirdwatch/linkedin-email-finder-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=thirdwatch/linkedin-email-finder-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/WJMzyiITEikwHLwwS/builds/yINhQYHsKT6xVtQKC/openapi.json