# Bulk LinkedIn Email Finder | $2/1K | No Cookies (`x_guru/bulk-linkedin-email-finder`) Actor

Find work and personal email addresses from lists of LinkedIn profile URLs. Enrich up to 100,000 URLs per run using database lookup, without LinkedIn cookies or login. Export available contact results as CSV or JSON.

- **URL**: https://apify.com/x\_guru/bulk-linkedin-email-finder.md
- **Developed by:** [Hundevmode Labs](https://apify.com/x_guru) (community)
- **Categories:** Lead generation, Jobs, Social media
- **Stats:** 169 total users, 0 monthly users, 100.0% runs succeeded, 4 bookmarks
- **User rating**: 1.00 out of 5 stars

## Pricing

$19.99/month + usage

To use this Actor, you pay a monthly rental fee to the developer. The rent is subtracted from your prepaid usage every month after the free trial period. You also pay for the Apify platform usage, which gets cheaper the higher Apify subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#rental-actors

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

## Bulk LinkedIn Email Finder

Turn a list of LinkedIn profile URLs into contact profiles with available work and personal email addresses. Use bulk email lookup to enrich CRM records and prepare outreach lists without LinkedIn cookies or login.

### How to use

1. Enter your filters or LinkedIn profile URLs in the Input tab.
2. Choose the contact fields and result filters you need.
3. Set the run spending limit and start the Actor.
4. Export the results from the Dataset tab as CSV, JSON or Excel, or retrieve them with the Apify API.

```json
{
  "linkedinUrls": [
    "https://www.linkedin.com/in/example-profile"
  ],
  "includeWorkEmails": true,
  "includePersonalEmails": true,
  "onlyWithEmails": true
}
```

### Input

| Field | Behavior |
| --- | --- |
| `linkedinUrls` | LinkedIn profile URLs; up to 100,000 per run. Duplicate usernames are checked once. |
| `includeWorkEmails` | Include work emails. Defaults to true. |
| `includePersonalEmails` | Include available personal emails. Defaults to true. |
| `onlyWithEmails` | Export only profiles with an included email. Defaults to true. |

The Input tab lists all supported options. This is a database lookup; it does not sign into LinkedIn or scrape live profile pages. Contact availability is not guaranteed, and the database may contain older records.

### Results and matching

With `onlyWithEmails: true`, unmatched URLs and profiles without an included email are not exported or charged as results. With `onlyWithEmails: false`, matching profiles without an email may also be exported and charged. One exported profile is one result, even if it contains several email addresses.

Returned profiles contain the available name, job and company fields together with the requested contact fields and a LinkedIn URL. CSV and JSON exports use the same underlying results.

### Pricing

**Scheduled migration:** pay-per-event pricing takes effect on **October 14, 2026, at 05:34 UTC**. Before that timestamp, the existing **$19.99/month rental** tariff remains active. The PPE prices below apply from that timestamp. The Store Pricing tab is the source of truth.

Pay per event: **$2 per 1,000 exported results** ($0.002 per result). The synthetic Actor Start event is **$0.00005 per allocated GB, with a minimum of one event**. Apify handles these events automatically. Your run spending limit can stop output before the requested maximum.

**Apify Free plan:** up to **500 exported profiles per UTC calendar month**. This is an output limit, not a promise of zero-cost results: the published event prices still apply and use your Apify credits. Checked URLs that produce no output do not consume this allowance. The allowance belongs to this Actor and does not change the counters of other Actors. Paying Apify users and the Actor owner bypass this monthly cap; per-run limits and the run budget still apply.

Concurrent runs reserve quota before exporting. Successfully unused slots are returned to the allowance. An interrupted upload with an unknown outcome retains its reservation to prevent duplicate exports from bypassing the cap. Quota details are saved in the `QUOTA` key-value record. Errors are saved in `ERROR`, never as paid result rows.

This code supports the rental transition and PPE. The Actor ID stays the same while the technical name now matches the Finder positioning.

### Pagination and integration

For larger input lists, split them into runs of up to 100,000 URLs. Repeated exports are separate results and are charged again. A spending limit may stop a run before all input URLs are checked.

The Actor ID is preserved. The technical name is now `bulk-linkedin-email-finder`, replacing the old rental/subscription URL label. API integrations using the Actor ID keep the same reference; update any integrations that use the old technical name. The visible title and search description distinguish this Finder listing from the paired Scraper.

Powered by [Dievio](https://dievio.com).

# Actor input Schema

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

List of LinkedIn profile URLs to find emails for (max 100,000 URLs per run)

## `includeWorkEmails` (type: `boolean`):

Include work/corporate email addresses in results

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

Include personal email addresses (Gmail, Yahoo, etc.) in results

## `onlyWithEmails` (type: `boolean`):

Skip profiles that don't have any email addresses

## Actor input object example

```json
{
  "linkedinUrls": [
    "https://www.linkedin.com/in/williamhgates",
    "https://www.linkedin.com/in/jeffweiner08"
  ],
  "includeWorkEmails": true,
  "includePersonalEmails": true,
  "onlyWithEmails": true
}
```

# Actor output Schema

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

No description

## `quota` (type: `string`):

No description

## `error` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("x_guru/bulk-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 = {}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,x_guru/bulk-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/MpJUaoxOxcHVxlLE4/builds/j6Bbaf1MBHI4Fj17R/openapi.json