# LinkedIn Company Employees Scraper + Email Finder (`sitcod3.lab/linkedin-company-email-scraper`) Actor

Extract employees from LinkedIn companies and find their verified email addresses. Perfect for lead generation, recruitment, and B2B sales outreach.

- **URL**: https://apify.com/sitcod3.lab/linkedin-company-email-scraper.md
- **Developed by:** [The Profesor Baltazar](https://apify.com/sitcod3.lab) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 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/actors/running/actors-in-store.md#pay-per-usage

## 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 Company Employees Scraper + Email Finder

Turn a list of company names into a lead list of their **publicly visible employees**
from LinkedIn, with work-email discovery for cold outreach, recruitment, and
market research.

**No login. No cookies. No account risk.** The actor only reads pages that are
already public to logged-out visitors — the same pages Google indexes.

***

### 🧭 How it works

| Step | What happens | Source |
|---|---|---|
| 1. Company resolution | Fetches the public `linkedin.com/company/<slug>` page and parses its schema.org JSON-LD (name, description, website) | Public company page |
| 2. Employee discovery | Finds public `linkedin.com/in/<profile>` URLs tied to the company via search-engine results (`site:linkedin.com/in "Company"` + your job-title/location terms) | Public SERP |
| 3. Profile scraping | Each public profile page → name, headline, job title, location, employer (JSON-LD `Person`) | Public profile page |
| 4. Email finding | Extracts emails the company publishes on its own website (contact/team pages), infers the company's email format, generates candidates per name | Public company website |
| 5. Email labeling | Domain MX check; optional SMTP probe. Statuses are honest: `listed_on_profile`, `verified`, `pattern_match`, `mx_ok`, `invalid_domain`, `not_found` | DNS / SMTP |

> ⚠️ **Honesty note:** LinkedIn does not expose emails to logged-out visitors.
> Emails returned are either *publicly listed on a profile/company page* or
> *pattern-generated candidates*. A `pattern_match` email is a best guess that
> has **not** been proven deliverable — verify before sending at scale.
> Only `verified` means the mail server accepted the mailbox on a live probe.

***

### 📥 Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `companies` | `string[]` | ✅ | — | One per line: LinkedIn slug (`stripe`), company URL (`https://www.linkedin.com/company/stripe`), or domain (`stripe.com`) |
| `maxEmployees` | `integer` 1–200 | ❌ | 50 | Cap per company |
| `findEmails` | `boolean` | ❌ | `true` | Pattern + public-email discovery from the company site |
| `verifyEmails` | `boolean` | ❌ | `false` | SMTP RCPT probe per candidate (slower, +status `verified`) |
| `jobTitles` | `string[]` | ❌ | — | Filter, e.g. `["CFO", "VP Finance"]` |
| `locations` | `string[]` | ❌ | — | Filter, e.g. `["San Francisco", "London"]` |
| `department` | `string` | ❌ | `any` | Keyword filter on title/headline |
| `decisionMakersOnly` | `boolean` | ❌ | `false` | Keep only C-Level / Director / Manager |
| `proxyConfiguration` | `object` | ❌ | Apify Proxy | **RESIDENTIAL recommended** — LinkedIn aggressively blocks datacenter IPs |

#### Example

```json
{
  "companies": ["stripe", "https://www.linkedin.com/company/plaid"],
  "maxEmployees": 30,
  "findEmails": true,
  "verifyEmails": false,
  "jobTitles": ["engineer"],
  "decisionMakersOnly": false,
  "proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}
}
```

***

### 📤 Output — one row per employee

| Field | Example | Meaning |
|---|---|---|
| `fullName` | `Jane Smith` | From public profile |
| `jobTitle` | `Staff Software Engineer` | Headline / jobTitle JSON-LD |
| `companyName` | `Stripe` | Matched public company |
| `companyDomain` | `stripe.com` | From company page website field |
| `linkedinUrl` | `https://www.linkedin.com/in/...` | Source profile |
| `location` | `San Francisco Bay Area` | Public profile location |
| `seniority` | `Senior` | Classified from title: C-Level/Director/Manager/Senior/Mid/Other |
| `email` | `jane.smith@stripe.com` | Best candidate (or listed email) |
| `email_status` | `pattern_match` | See honesty note above |
| `email_confidence` | `60` | listed\_on\_profile=99, verified=95, pattern\_match=60 |
| `email_candidates` | `[...]` | Up to 4 generated candidates |
| `dataSource` | `public linkedin wayback` | How the profile was fetched (direct/proxy/wayback) |
| `scrapedAt` | ISO UTC | |

Export as JSON / CSV / Excel from the **Output** tab, or pull the dataset via
API. Failed pages are skipped (not billed, not returned).

***

### 🚀 Run it

1. **Console** — open the actor, paste companies, Start, watch the run log,
   export the dataset.
2. **API**
   ```bash
   curl -X POST "https://api.apify.com/v2/acts/sitcod3.lab~linkedin-company-email-scraper/runs?token=$APIFY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"companies":["stripe"],"maxEmployees":10}'
   ```
3. **Python**
   ```python
   from apify_client import ApifyClient
   client = ApifyClient("YOUR_TOKEN")
   run = client.actor("sitcod3.lab/linkedin-company-email-scraper").call(
       run_input={"companies": ["stripe"], "maxEmployees": 10})
   items = client.dataset(run["defaultDatasetId"]).list_items().items
   ```

***

### ⚖️ Compliance

This actor reads only public, logged-out-visible pages. You are the data
controller for anything you collect. Bulk personal data falls under GDPR/CCPA
— establish a lawful basis and honor opt-outs before outreach. Output may not
be resold as a database. The tool is not affiliated with or endorsed by
LinkedIn. Respect applicable laws and terms when using the data.

### 🛠 Troubleshooting

| Problem | Fix |
|---|---|
| `no profiles discovered` | Search-engine result blocked this IP — re-run (proxy group rotates) or check `RESIDENTIAL` is selected |
| Profile rows missing email | `findEmails` off, or company domain has no MX — status tells you which |
| `pattern_match` only, never `verified` | Target mail servers reject RCPT probes (common, by design) — set `verifyEmails:false` to save time |
| Slow runs | `verifyEmails` costs 5–15 s/contact; disable unless deliverability matters |

# Actor input Schema

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

One per line: company LinkedIn slug (stripe), full URL (https://www.linkedin.com/company/stripe), or plain domain (stripe.com).

## `maxEmployees` (type: `integer`):

Cap of employee rows returned per company (1-200).

## `findEmails` (type: `boolean`):

Generate email candidates from the company domain using patterns observed on the company website. Results are labeled pattern\_match / listed\_on\_profile — never claimed verified unless SMTP-checked.

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

Probe each candidate via SMTP RCPT (where the mail server allows) and mark status verified. ~5-15 s per contact.

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

Keep only employees whose title/headline contains one of these (case-insensitive).

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

Keep only employees whose profile location matches one of these.

## `department` (type: `string`):

Keep only employees whose title or headline contains this keyword. Leave 'any'.

## `decisionMakersOnly` (type: `boolean`):

Keep only C-Level, Director and Manager seniority rows.

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

RESIDENTIAL strongly recommended; the actor probes groups and falls back automatically.

## Actor input object example

```json
{
  "companies": [
    "stripe"
  ],
  "maxEmployees": 50,
  "findEmails": true,
  "verifyEmails": false,
  "department": "any",
  "decisionMakersOnly": false
}
```

# Actor output Schema

## `fullName` (type: `string`):

No description

## `jobTitle` (type: `string`):

No description

## `companyName` (type: `string`):

No description

## `companyDomain` (type: `string`):

No description

## `linkedinUrl` (type: `string`):

No description

## `location` (type: `string`):

No description

## `seniority` (type: `string`):

No description

## `email` (type: `string`):

No description

## `email_status` (type: `string`):

listed\_on\_profile | verified | pattern\_match | mx\_ok | invalid\_domain | not\_found | no\_domain | not\_requested

## `email_confidence` (type: `string`):

No description

## `email_candidates` (type: `string`):

Comma-separated generated candidates.

## `companyWebsite` (type: `string`):

No description

## `dataSource` (type: `string`):

No description

## `scrapedAt` (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 = {
    "companies": [
        "stripe"
    ]
};

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

# Run the Actor and wait for it to finish
run = client.actor("sitcod3.lab/linkedin-company-email-scraper").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 '{
  "companies": [
    "stripe"
  ]
}' |
apify call sitcod3.lab/linkedin-company-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sitcod3.lab/linkedin-company-email-scraper"
        }
    }
}
```

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/MkUjLNzyBjISO2mEN/builds/vWIILjp8V1Xke8zib/openapi.json