# LinkedIn Bulk Email Finder (`creatorharsh/linkedin-bulk-email-finder`) Actor

Find verified business emails from LinkedIn profiles in bulk using Findymail, Anymail Finder, or Apollo. Process 1,000+ profiles per run with your own API keys. Free to use, with pay-as-you-go provider and Apify compute costs.

- **URL**: https://apify.com/creatorharsh/linkedin-bulk-email-finder.md
- **Developed by:** [Harsh Vardhan](https://apify.com/creatorharsh) (community)
- **Stats:** 1 total users, 0 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 Email Finder workflow](https://api.apify.com/v2/key-value-stores/dPYPDciuTb0cf5HIJ/records/LinkedInEmailFinderWorkflowBanner.png?signature=1DS3EbGBqqDvoOPC2E5Em)

## LinkedIn Bulk Email Finder

Turn a spreadsheet of LinkedIn profile URLs into work emails. Pick **Findymail**, **Apollo** or **Anymail Finder**, paste your own API key, upload your file, and get the same sheet back with an email next to each profile.

The actor itself is free. Lookups are charged to your own account with the provider you choose, so you stay in control of the cost.

#### Use cases

- **Sales outreach:** enrich a list of prospects exported from LinkedIn, Sales Navigator or a CRM.
- **Recruiting:** find contact emails for candidates you sourced on LinkedIn.
- **Lead list cleanup:** add emails to a lead list that only has profile links.
- **Provider comparison:** run the same file through two providers and compare hit rates.
- **Pair with a profile finder:** feed it the LinkedIn URLs found by another actor, saved as a `.csv` or `.xlsx`.

#### How it works

1. You pick an email provider and paste your API key for it.
2. You upload an `.xlsx` or `.csv` file. The first sheet is used, the first non-empty row is the header, and the column holding LinkedIn links is detected automatically. Hyperlinked Excel cells are supported.
3. The actor cleans each URL (country subdomains, tracking parameters, trailing slashes, a missing `https://`) and looks up each unique profile once.
4. Lookups run in parallel and slow down automatically if the provider rate limits you.
5. You get back one row per input row, in the same order as your file, with all your original columns kept.

#### Input

| Field | Required | Description |
|---|---|---|
| Email provider | Yes | Findymail, Apollo or Anymail Finder |
| API key | Yes | The key for the provider you selected. Stored encrypted and never written to logs or output. |
| Spreadsheet upload | Yes | An `.xlsx` or `.csv` file, or a public link to one. Old `.xls` files must be saved as `.xlsx` first. |

Where to get your key:

| Provider | Where to find the key | Notes |
|---|---|---|
| Findymail | app.findymail.com/api | Only found emails are charged. |
| Apollo | Apollo > Settings > Integrations > API | Needs a **master API key** on a paid plan with API access. Returns only emails with status `verified`. |
| Anymail Finder | app.anymailfinder.com/settings/api | Returns only `valid` emails. Risky emails are not returned or charged. |

Example input:

```json
{
  "provider": "findymail",
  "apiKey": "YOUR_API_KEY",
  "spreadsheetUrl": "https://example.com/leads.xlsx"
}
```

#### Output

One dataset row per input row, in your original order. Your own columns are kept as they are. If one of them clashes with an output column name (for example `email`), it is renamed with an `input_` prefix.

| Column | Description |
|---|---|
| `row_number` | Row number in the uploaded file |
| *(your columns)* | Everything from the uploaded sheet |
| `linkedin_url_normalized` | The cleaned URL that was looked up |
| `email` | The email, if one was found |
| `full_name` | Name returned by the provider |
| `domain` | Company domain returned by the provider |
| `status` | `found`, `not_found`, `invalid_url`, `duplicate`, `error` or `not_processed` |
| `error` | Plain-English reason when the status is not `found` |

Example row:

```json
{
  "row_number": 2,
  "Name": "Jane Doe",
  "linkedin_url_normalized": "https://www.linkedin.com/in/jane-doe",
  "email": "jane.doe@example.com",
  "full_name": "Jane Doe",
  "domain": "example.com",
  "status": "found",
  "error": null
}
```

What each status means:

| Status | Meaning |
|---|---|
| `found` | A verified email was returned |
| `not_found` | The provider has no verified email for this profile |
| `invalid_url` | Not a person profile (Sales Navigator link, company or school page, empty cell, not LinkedIn) |
| `duplicate` | Same profile as an earlier row. It is looked up once and the result is copied |
| `error` | The lookup failed after retries. The `error` column says why |
| `not_processed` | The run stopped early, for example because credits ran out. Re-run with only these rows |

Download the results as Excel, CSV or JSON from the Storage tab. A `RUN_SUMMARY` record in the key-value store holds the totals: rows, valid and duplicate URLs, emails found, hit rate and credits used. Apollo has no balance endpoint, so credits used is not reported for it.

#### Tips and limits

- Test with a small file first (10 to 20 rows) to check that your key works and the right column is detected.
- The column with LinkedIn links is picked automatically. If your file has several such columns, keep only the one you want to look up.
- If you run out of credits, the actor stops cleanly, keeps everything found so far and marks the rest `not_processed`.
- If a run is restarted, it resumes from its last checkpoint and does not pay twice for emails already found.
- Parallel lookups are set automatically: 10 for Findymail and Anymail Finder, 5 for Apollo.
- Very large Excel files use more memory. Set the run memory to 1 GB for files with many thousands of rows, or use `.csv`.
- The default run timeout is 4 hours. Raise it in the run options for very large files.

#### Legal and ethical considerations

You are responsible for using the data lawfully, including GDPR and similar privacy laws, anti-spam rules and the terms of your email provider. Only contact people you have a legitimate reason to contact, and respect opt-out requests. This actor does not scrape LinkedIn. It sends the profile links you provide to the provider you choose, and it keeps no data beyond your own run storage.

#### Support

Found a bug or need another provider? Open an issue on the [GitHub repository](https://github.com/webethics/linkedIn-bulk-email-finder) or message the actor owner on Apify.

# Actor input Schema

## `provider` (type: `string`):

Which email-finding service to use. Lookups are charged to your own account with that provider.

## `apiKey` (type: `string`):

Your API key for the provider selected above. Findymail: app.findymail.com/api. Apollo: Settings > Integrations > API (a master key is required). Anymail Finder: app.anymailfinder.com/settings/api. Stored encrypted.

## `spreadsheetUrl` (type: `string`):

Upload a file or paste a public link to one. The first sheet is used, the first non-empty row is the header, and the column with LinkedIn links is detected automatically.

## Actor input object example

```json
{
  "provider": "findymail"
}
```

# Actor output Schema

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

One item per input row with the original columns, the cleaned LinkedIn URL, the email found, and a status.

## `runSummary` (type: `string`):

Totals for the run: rows, valid and duplicate URLs, emails found, hit rate and credits used.

# 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("creatorharsh/linkedin-bulk-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("creatorharsh/linkedin-bulk-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 creatorharsh/linkedin-bulk-email-finder --silent --output-dataset

```

## MCP server setup

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