# LinkedIn Email Finder (`khadinakbar/linkedin-email-finder`) Actor

Find and verify work emails from LinkedIn profile URLs. Public data, no cookies. MCP/API-ready.

- **URL**: https://apify.com/khadinakbar/linkedin-email-finder.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $40.00 / 1,000 email founds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

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

**Find the most likely work email from a LinkedIn profile URL — public data, no cookies, no login.**

Give it a LinkedIn profile URL (or a name + company domain). It resolves the person's
name and current company, looks up the company's website domain, generates the most likely
email patterns, and **validates each against the live mail server (DNS MX + best-effort
SMTP)** before returning the highest-confidence address with a transparent score.

> Deliverability check: every returned email is confirmed to have a working mail server
> (MX). When the run network permits an outbound SMTP probe, the mailbox itself is verified
> (`emailStatus: valid`). On clouds that block outbound port 25 (most, including Apify), the
> top-ranked pattern is returned as `mx_valid_unverified` with a confidence score instead —
> honestly labeled, never faked.

Built for SDRs, recruiters, and AI agents that have a LinkedIn URL and need a reachable email.

### What you get

| Field | Description |
|---|---|
| `name` | Person's full name (from public LinkedIn profile) |
| `company` | Current company name |
| `companyDomain` | Resolved company website domain (e.g. `shopify.com`) |
| `email` | Best deliverable work email |
| `emailStatus` | `valid` · `mx_valid_unverified` · `catch_all` · `invalid` · `no_mx` · `profile_not_found` |
| `confidence` | 0–100 score from verification result + pattern probability |
| `smtpVerified` | `true` when the mailbox was confirmed by an SMTP RCPT probe |
| `isRole` | `true` if the address is a role inbox (info@, sales@…) |
| `candidates` | All tested patterns with their individual status + confidence |
| `source` | `scrapecreators`, `sociavault`, or `direct` |

### When to use it

- You have LinkedIn profile URLs and need verified work emails for outreach.
- You already know a name + company domain and just want pattern generation + SMTP verification.
- An AI agent needs a single tool: profile URL in → verified email out.

**Not for:** scraping a private email off LinkedIn (LinkedIn does not expose it, and neither
does this actor). Emails here are **derived from the public name + company domain and then
verified for deliverability** — the same method as Hunter, Apollo, and other finders.

### How it works

1. **Resolve profile** — ScrapeCreators `/v1/linkedin/profile` (SociaVault fallback) → name + current company.
2. **Resolve domain** — ScrapeCreators `/v1/linkedin/company` → company `website` → domain.
3. **Generate** — ~15 ranked permutations (`first.last`, `f.last`, `first`, …).
4. **Validate** — DNS MX lookup (drops domains with no mail server) → best-effort SMTP
   `RCPT TO` probe with catch-all detection. The probe stops early as soon as a mailbox is
   confirmed; when port 25 is blocked it is skipped and the MX result stands.
5. **Score + return** — the highest-confidence email, plus every candidate tested and its
   individual status.

The company domain is reduced to its registrable root (e.g. `news.microsoft.com` →
`microsoft.com`) so the mail-server check runs against the real email domain.

### Input

```json
{
  "linkedinUrls": [
    "https://www.linkedin.com/in/williamhgates",
    "https://www.linkedin.com/in/satyanadella"
  ],
  "includeUnverified": true,
  "maxResults": 100
}
```

Or skip LinkedIn entirely:

```json
{
  "directLeads": [
    { "fullName": "Jane Doe", "companyDomain": "acme.com", "companyName": "Acme" }
  ]
}
```

### Output

```json
{
  "name": "Satya Nadella",
  "company": "Microsoft",
  "companyDomain": "microsoft.com",
  "email": "satya.nadella@microsoft.com",
  "emailStatus": "valid",
  "confidence": 96,
  "smtpVerified": true,
  "isRole": false,
  "candidates": [
    { "email": "satya.nadella@microsoft.com", "status": "valid", "confidence": 96, "pattern": "{first}.{last}" }
  ],
  "source": "scrapecreators"
}
```

### Pricing (pay per event)

| Event | Price |
|---|---|
| Actor start | $0.00005 |
| Profile resolved (name + company domain) | $0.02 |
| Email found (deliverable email returned) | $0.04 |

Typical lead with a found email: ~**$0.06**. You are not charged the email event when no
deliverable address is produced.

### Companion actors

- `linkedin-profile-search-scraper` — find profile URLs to feed this actor.
- `email-address-validator` — bulk-validate an existing email list.
- `linkedin-profile-email-scraper` — pull on-profile contact fields when present.

### Legal

Returns only public data and standards-based mail-server verification. No login, no cookies,
no private LinkedIn fields. You are responsible for using the output in compliance with
applicable laws (GDPR, CAN-SPAM, CCPA) and LinkedIn's terms. Email patterns are predictions
verified for deliverability, not data extracted from a private source.

# Actor input Schema

## `linkedinUrls` (type: `array`):

Public LinkedIn profile URLs to find a work email for, e.g. 'https://www.linkedin.com/in/williamhgates'. Each profile is resolved to a name + current company via ScrapeCreators (SociaVault fallback), the company website domain is looked up, then an email is generated and verified. Defaults to empty. NOT a search query and NOT a company URL — for company-wide enumeration use a company scraper instead.

## `directLeads` (type: `array`):

Skip LinkedIn lookup and find an email directly from a known person + company. Each item is an object like {"fullName": "Jane Doe", "companyDomain": "acme.com", "companyName": "Acme"}. Use this when you already know the company domain and only need email generation + SMTP verification. companyName is optional. Defaults to empty.

## `includeUnverified` (type: `boolean`):

When true (default), if the mail server cannot be SMTP-probed (port 25 blocked) or is catch-all, the highest-probability pattern email is still returned with a confidence score and an honest emailStatus. When false, only mailbox-confirmed ('valid') emails are returned in the email field. Set false for strict deliverability-only output.

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

Hard cap on how many leads are processed and billed this run (across linkedinUrls + directLeads). Protects your budget on large inputs. Defaults to 100. Minimum 1.

## `maxCandidatesPerLead` (type: `integer`):

How many ranked email permutations to verify per person before stopping (verification stops early once a mailbox is SMTP-confirmed). Higher = more thorough, slower. Defaults to 15. Range 1-15.

## Actor input object example

```json
{
  "linkedinUrls": [
    "https://www.linkedin.com/in/satyanadella"
  ],
  "directLeads": [
    {
      "fullName": "Jane Doe",
      "companyDomain": "acme.com",
      "companyName": "Acme"
    }
  ],
  "includeUnverified": true,
  "maxResults": 100,
  "maxCandidatesPerLead": 15
}
```

# Actor output Schema

## `emails` (type: `string`):

Dataset of leads with their best deliverable email and verification status.

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

Counts of profiles resolved, emails found, and estimated cost.

# 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 = {
    "linkedinUrls": [
        "https://www.linkedin.com/in/williamhgates"
    ],
    "directLeads": [],
    "maxResults": 100,
    "maxCandidatesPerLead": 15
};

// Run the Actor and wait for it to finish
const run = await client.actor("khadinakbar/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 = {
    "linkedinUrls": ["https://www.linkedin.com/in/williamhgates"],
    "directLeads": [],
    "maxResults": 100,
    "maxCandidatesPerLead": 15,
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/linkedin-email-finder").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 '{
  "linkedinUrls": [
    "https://www.linkedin.com/in/williamhgates"
  ],
  "directLeads": [],
  "maxResults": 100,
  "maxCandidatesPerLead": 15
}' |
apify call khadinakbar/linkedin-email-finder --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/QPGUyrwcV7CPITZdI/builds/5ph77qXXXLZ8afJMS/openapi.json