# LinkedIn Email and Phone Finder (`moltsets/linkedin-email-phone-finder`) Actor

Find business emails, personal emails, mobile phones and SHA256 hashes from LinkedIn profile URLs. Bring your own MoltSets API key; you only pay MoltSets for hits.

- **URL**: https://apify.com/moltsets/linkedin-email-phone-finder.md
- **Developed by:** [MoltSets](https://apify.com/moltsets) (community)
- **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 Email and Phone Finder: business emails, mobile phones and hashes from LinkedIn URLs

Find business emails from LinkedIn profile URLs, plus optional personal emails (US), carrier-verified mobile phone numbers, SHA256 and MD5 email hashes, and full profile and company data. Paste URLs or point it at the dataset from any LinkedIn scraper run, and get back one enriched row per profile, with a deliverability grade on every email. Powered by [MoltSets](https://moltsets.com).

- **Business or best email**: work emails only, or the best available email (business first, falling back to personal for the highest match rate).
- **Personal email (US only)**: Gmail, iCloud and similar addresses with A to F risk grades. Depends on your MoltSets plan.
- **Mobile phone**: carrier-verified mobile numbers, no landlines or VoIP. Needs a MoltSets phone token subscription.
- **SHA256 hashes**: hashed emails for Meta, Google and LinkedIn ad audience matching.
- **Full profile**: name, title, seniority, location and company firmographics (industry, headcount, revenue band).
- **Never charged twice**: pick two or more of email, personal email and hashes and the Actor makes one combined lookup per profile instead of one per field.
- **Clean input**: URLs are normalised and de-duplicated; company pages, Sales Navigator links and junk are flagged without spending anything.

### Bring your own MoltSets API key

This Actor calls the [MoltSets API](https://developer.moltsets.com) with your own key, so MoltSets data is billed to your MoltSets account and Apify only charges for compute (the Actor itself is free).

1. [Create a free MoltSets account](https://app.moltsets.com/signup?utm_source=apify\&utm_medium=actor\&utm_campaign=linkedin-email-phone-finder).
2. Copy a key from [API keys](https://app.moltsets.com/dashboard/api_keys). Keys start with `ms_`.
3. Paste it into the **MoltSets API key** field. Apify stores it encrypted and the Actor never logs it.

### What it costs

**You only pay for hits.** A lookup that finds nothing costs no tokens. It still counts towards your MoltSets Fair Use request limits.

| Lookup | MoltSets tool | Cost |
| :--- | :--- | :--- |
| Email (business or best) | `linkedin_to_business_email` / `linkedin_to_best_email` | 1 token per email found |
| Personal email (US) | `linkedin_to_best_personal_email_usa` | 1 token per email found |
| SHA256 hashes | `linkedin_to_sha256` | 1 token per profile with hashes |
| Two or more of the above, or Full profile | `reverse_linkedin_lookup` | 1 token per profile found, covering all of them |
| Mobile phone | `linkedin_to_mobile_phone` | 1 phone token per number found |

Costs are read live from your account (`get_billing`) at the start of every run, and the log shows a worst-case estimate before any lookups are made. If your balance is lower than the worst case the run still starts, because misses are free; if tokens run out it stops gracefully and keeps everything found so far.

Token costs are the published MoltSets rates at the time of writing. With a single email option the Actor uses the dedicated lookup, which only charges when that email is found. The combined lookup charges when the profile is found, even if it has no email, which is why it is only chosen automatically when it saves you money (or when you ask for the full profile). Mobile numbers spend **phone tokens**, a separate balance from a monthly phone token subscription (paid plans only).

### Input

| Field | Name | Default | Description |
| :--- | :--- | :--- | :--- |
| `apiKey` | MoltSets API key |  | Required. Your MoltSets API key (starts with `ms_`). No account yet? [Sign up free](https://app.moltsets.com/signup?utm_source=apify\&utm_medium=actor\&utm_campaign=linkedin-email-phone-finder), then copy a key from [API keys](https://app.moltsets.com/dashboard/api_keys). MoltSets bills your MoltSets account directly, and only for hits. |
| `linkedinUrls` | LinkedIn profile URLs |  | Profile URLs (`https://www.linkedin.com/in/...`) or bare profile slugs. Duplicates and company pages are filtered out before any lookup. |
| `datasetId` | Read profiles from a dataset |  | Use the results of another run, for example a LinkedIn scraper. Combined with any URLs above. |
| `datasetField` | Dataset column with the profile URL |  | Column to read, for example `linkedinUrl` or `author.profileUrl` (dot paths work). Leave empty to try common names: linkedinUrl, linkedInUrl, profileUrl, linkedin_url, linkedinProfileUrl, url, publicIdentifier. |
| `businessEmail` | Email | `true` | Find an email for each profile. |
| `emailType` | Email type | `"business"` (`business`, `best`) | Business only returns work addresses. Best returns a business email when one exists and otherwise a personal one, for the highest match rate. |
| `personalEmail` | Personal email (US only) | `false` | Personal addresses such as Gmail, for US profiles. Depends on your MoltSets plan: if your plan does not include personal email, rows are marked `restricted` and nothing is charged. |
| `mobilePhone` | Mobile phone | `false` | Carrier-verified mobile numbers. Needs a MoltSets phone token subscription (paid plans only); each number found costs one phone token. Numbers are not screened against Do Not Call registries: compliance is your responsibility. |
| `sha256` | SHA256 hashes | `false` | Hashed emails (SHA256 and MD5) for ad platform audience matching. Not available on every MoltSets plan; restricted rows are marked as such. |
| `includeProfile` | Full profile | `false` | Add name, job title, seniority, location and company firmographics. Uses one combined lookup per profile. This is also chosen automatically when you pick two or more of email, personal email and hashes, so you are not charged once per field. |
| `maxItems` | Maximum profiles | `100` | Hard cap on unique profiles processed in this run. |
| `maxRetryWaitSecs` | Longest Fair Use wait | `120` | If MoltSets asks the run to wait for a Fair Use window up to this long, it waits and carries on. Longer waits stop the run gracefully and keep the results so far. |

Example input:

```json
{
    "apiKey": "ms_XXXXXXXXXXX",
    "linkedinUrls": [
        "https://www.linkedin.com/in/john-smith-123",
        "jane-doe-456"
    ],
    "businessEmail": true,
    "emailType": "business",
    "personalEmail": false,
    "mobilePhone": true,
    "sha256": false,
    "maxItems": 100
}
```

### Output

One row per input item, in input order. Each lookup has a `<lookup>_status` column:

| Status | Meaning |
| :--- | :--- |
| `found` | Data returned (and charged). |
| `not_found` | Nothing on file. Free. |
| `restricted` | Not included in your MoltSets plan. Nothing charged. See `notes`. |
| `skipped` | Not attempted: invalid input, out of phone tokens, or the run stopped early. See `notes`. |
| `error` | MoltSets could not complete the lookup after retries. Free; worth running again. |

Example row:

```json
{
    "linkedin_url": "https://www.linkedin.com/in/john-smith-123",
    "linkedin_url_normalised": "https://www.linkedin.com/in/john-smith-123",
    "input_status": "valid",
    "email_status": "found",
    "email": "john.smith@example.com",
    "email_type": "business",
    "email_risk_score": "A",
    "email_validated_at": "2026-09-12",
    "mobile_phone_status": "found",
    "mobile_phone": "5555555555",
    "mobile_phone_validated_at": "2026-03-04",
    "notes": null
}
```

- **Risk scores** grade send safety, not identity: `A` validated deliverable, `B` known engagement, `C` catch-all domain, `D` never send (bounce, complaint or trap), `F` no signal. Suppress `D`; treat `C` and `F` as unknown rather than bad.
- **Restricted is not missing.** If your plan withholds personal emails or SHA256 hashes, those columns say `restricted` and `notes` explains why, so you can tell a plan boundary from a profile with no data.
- **Hashes**: with SHA256 as the only option, the dedicated lookup returns one business and one personal hash in each format. When it is combined with other options, the combined lookup returns business email hashes only (`sha256_personal` and `md5_personal` stay empty).
- **Mobile numbers are not screened against Do Not Call registries.** MoltSets does not return DNC status. `mobile_phone_validated_at` only says the number was in service on that date. Scrubbing against the DNC registries that apply to you, and following calling and messaging rules, is your responsibility.

A run summary (hits and misses per lookup, tokens used, skipped lookups and why, stop reason) is saved as `SUMMARY` in the run's key-value store and shown in the run's status message.

### Chaining from a scraper

Run any LinkedIn scraper from the Apify Store, then pass its dataset to this Actor. In the Console, choose the dataset under **Read profiles from a dataset** and, if needed, name the column holding the profile URL (common names such as `linkedinUrl` and `profileUrl` are detected automatically).

From code, with the [Apify API client](https://docs.apify.com/api/client/js/):

```js
import { ApifyClient } from 'apify-client';

const apify = new ApifyClient({ token: process.env.APIFY_TOKEN });

// 1. Any LinkedIn scraper that outputs profile URLs.
const scrape = await apify.actor('<linkedin-scraper-actor-id>').call({ /* scraper input */ });

// 2. Enrich its results.
const enrich = await apify.actor('moltsets/linkedin-email-phone-finder').call({
    apiKey: process.env.MOLTSETS_API_KEY,
    datasetId: scrape.defaultDatasetId,
    datasetField: 'linkedinUrl',
    businessEmail: true,
    maxItems: 500,
});

const { items } = await apify.dataset(enrich.defaultDatasetId).listItems();
```

To run it automatically after every scraper run, add an [integration](https://docs.apify.com/platform/integrations/actors) on the scraper that starts this Actor with `{"datasetId": "{{resource.defaultDatasetId}}"}` plus your key.

### Limits

- **Plan-restricted lookups**: personal emails need a plan that includes them; SHA256 hashes are not available on the $397 and $997 plans. Restricted lookups are never retried and never charged.
- **Phone tokens**: mobile lookups need a MoltSets phone token subscription (paid plans only, from $27 a month for 180 phone tokens). When phone tokens run out, mobile lookups stop and everything else carries on.
- **Fair Use**: MoltSets limits enrichment records and requests per rolling 5-hour and 1-week window, by plan (for example $27: 1k records and 5k requests per 5 hours; $97: 15k and 75k). Every lookup counts as a request, hit or miss. If MoltSets asks the run to wait less than **Longest Fair Use wait** (default 120 seconds) it waits and continues; otherwise it stops gracefully, keeps its results and says when the window resets. See the [Fair Use Policy](https://moltsets.com/fair-use-policy-enrichment/).
- **Out of tokens**: the run stops, keeps everything processed so far and links to billing. Unprocessed rows are marked `skipped`.
- **Maximum profiles** caps unique profiles per run (default 100), so a large dataset cannot spend more than you intended.
- **Personal email is US only.**

### Other MoltSets Actors

- Email Finder by Name and Company (coming soon): business emails from a name and company domain.
- Reverse Email Lookup (coming soon): the person and LinkedIn profile behind an email address.
- IP to Company Lookup (coming soon): the company behind an IPv4 address.
- LinkedIn Profile Enricher (coming soon): full profile, emails and company firmographics from LinkedIn URLs.
- B2B Lead List Builder (coming soon): lead lists of people or companies by title, industry, location and size.
- LinkedIn Profile Finder (coming soon): LinkedIn profile URLs from an email or a name and company.
- Audience Match Keys (coming soon): hashed emails and mobile ad IDs for customer match audiences.

### Support

- MoltSets API docs: [developer.moltsets.com](https://developer.moltsets.com)
- Account, billing and plan questions: support@moltsets.com
- Bugs in this Actor: open an issue on the **Issues** tab.

# Actor input Schema

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

Required. Your MoltSets API key (starts with <code>ms\_</code>). No account yet? <a href="https://app.moltsets.com/signup?utm_source=apify&utm_medium=actor&utm_campaign=linkedin-email-phone-finder" target="_blank">Sign up free</a>, then copy a key from <a href="https://app.moltsets.com/dashboard/api_keys" target="_blank">API keys</a>. MoltSets bills your MoltSets account directly, and only for hits.

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

Profile URLs (<code>https://www.linkedin.com/in/...</code>) or bare profile slugs. Duplicates and company pages are filtered out before any lookup.

## `datasetId` (type: `string`):

Use the results of another run, for example a LinkedIn scraper. Combined with any URLs above.

## `datasetField` (type: `string`):

Column to read, for example <code>linkedinUrl</code> or <code>author.profileUrl</code> (dot paths work). Leave empty to try common names: linkedinUrl, linkedInUrl, profileUrl, linkedin_url, linkedinProfileUrl, url, publicIdentifier.

## `businessEmail` (type: `boolean`):

Find an email for each profile.

## `emailType` (type: `string`):

Business only returns work addresses. Best returns a business email when one exists and otherwise a personal one, for the highest match rate.

## `personalEmail` (type: `boolean`):

Personal addresses such as Gmail, for US profiles. Depends on your MoltSets plan: if your plan does not include personal email, rows are marked <code>restricted</code> and nothing is charged.

## `mobilePhone` (type: `boolean`):

Carrier-verified mobile numbers. Needs a MoltSets phone token subscription (paid plans only); each number found costs one phone token. Numbers are not screened against Do Not Call registries: compliance is your responsibility.

## `sha256` (type: `boolean`):

Hashed emails (SHA256 and MD5) for ad platform audience matching. Not available on every MoltSets plan; restricted rows are marked as such.

## `includeProfile` (type: `boolean`):

Add name, job title, seniority, location and company firmographics. Uses one combined lookup per profile. This is also chosen automatically when you pick two or more of email, personal email and hashes, so you are not charged once per field.

## `maxItems` (type: `integer`):

Hard cap on unique profiles processed in this run.

## `maxRetryWaitSecs` (type: `integer`):

If MoltSets asks the run to wait for a Fair Use window up to this long, it waits and carries on. Longer waits stop the run gracefully and keep the results so far.

## Actor input object example

```json
{
  "linkedinUrls": [
    "https://www.linkedin.com/in/retentionadam"
  ],
  "businessEmail": true,
  "emailType": "business",
  "personalEmail": false,
  "mobilePhone": false,
  "sha256": false,
  "includeProfile": false,
  "maxItems": 100,
  "maxRetryWaitSecs": 120
}
```

# Actor output Schema

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

One row per input profile.

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

Hits and misses per lookup, tokens used, skipped lookups and stop reason.

# 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/retentionadam"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("moltsets/linkedin-email-phone-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/retentionadam"] }

# Run the Actor and wait for it to finish
run = client.actor("moltsets/linkedin-email-phone-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 '{
  "linkedinUrls": [
    "https://www.linkedin.com/in/retentionadam"
  ]
}' |
apify call moltsets/linkedin-email-phone-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moltsets/linkedin-email-phone-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/8Wj1oQ7TLu31MNKul/builds/jLBvuuTUwlhxmH5RV/openapi.json