# Verified Email Finder ⚡ Bulk Business Emails (`zyra/verified-email-finder`) Actor

Find verified business email addresses in bulk from a full name and company domain. Pay only for verified emails — no charge for misses.

- **URL**: https://apify.com/zyra/verified-email-finder.md
- **Developed by:** [Zyra](https://apify.com/zyra) (community)
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $4.00 / 1,000 verified email founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

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

## ⚡ Verified Email Finder — Bulk Business Emails from Name + Company or LinkedIn URL

Turn a list of **names and company domains**, or **LinkedIn profile URLs**, into **verified business email addresses** —
in bulk, fast, and in parallel. Built for prospecting, lead lists, CRM enrichment, and
recruiting outreach.

**You pay only for verified emails.** No match, no charge.

***

### ✨ Why use it

- ✅ **Verified results** — every returned address is validated, so your bounce rate stays low.
- ⚡ **Bulk & parallel** — drop in hundreds or thousands of people and get results fast.
- 💸 **Pay per result** — you are billed only for emails actually found. Misses are free.
- 🧩 **Dead-simple input** — `full_name` + `domain`, or just a LinkedIn profile URL. Mix both in one list.
- 🔗 **LinkedIn in, email out** — we read the profile for the person's name, job title and current company, then find the email.
- 📊 **Clean, structured output** — one tidy row per person, ready for CRM/CSV/Sheets.

***

### 📥 Input

Provide a list of people. Each entry is **either** a full name plus the company's domain
(or company name), **or** a LinkedIn profile URL — mix them freely:

```json
{
  "leads": [
    { "full_name": "Satya Nadella", "domain": "microsoft.com" },
    { "linkedin_url": "https://www.linkedin.com/in/williamhgates/" },
    "https://www.linkedin.com/in/jane-doe-123/"
  ]
}
```

| field | description |
|---|---|
| `full_name` | the person's full name |
| `domain` | the company's website domain (e.g. `acme.com`) or company name |
| `linkedin_url` | the person's LinkedIn profile URL |

When an entry has both `full_name` and `domain`, those are used as given. Otherwise its
`linkedin_url` is read for the person's name and current employer, and the employer's
website becomes the domain.

Add as many entries as you want — they're processed in bulk, concurrently.

***

### 📤 Output

One row per person in the dataset (export to CSV, Excel, JSON, or Google Sheets):

```json
{
  "full_name": "Satya Nadella",
  "domain": "microsoft.com",
  "email": "snadella@microsoft.com",
  "is_found": true,
  "email_status": "valid",
  "company": "Microsoft",
  "job_title": "Chairman and CEO",
  "linkedin_url": "https://www.linkedin.com/in/satyanadella/"
}
```

| field | description |
|---|---|
| `full_name` | the person you searched for (read from LinkedIn for URL entries) |
| `domain` | the company domain you provided, or the employer's website from LinkedIn |
| `email` | the verified business email (null if not found) |
| `is_found` | whether a verified email was found |
| `email_status` | validation status of the email (e.g. `valid`) |
| `company` | current employer, from LinkedIn |
| `job_title` | current job title, from LinkedIn |
| `linkedin_url` | the profile the entry was resolved from |

When no email is found, `email` is `null`, `is_found` is `false`, and **you are not charged**.

***

### 💳 Pricing

**Pay-per-result:** you are charged a small fixed price **only for each verified email
found**. Runs that find nothing cost nothing. See the **Pricing** tab for the exact rate.

***

### 🚀 Getting started

1. Open the **Input** tab.
2. Paste your list of `{ full_name, domain }` entries.
3. Click **Start**.
4. Grab your results from the **Dataset** tab (or the API).

That's it — no accounts, keys, or setup required.

***

### 💡 Great for

- Sales prospecting & outbound lead lists
- CRM data enrichment and cleanup
- Recruiting and candidate outreach
- Building targeted contact lists at scale

***

### ❓ FAQ

**Do I get charged for people you can't find?**
No. You're only charged for verified emails that are actually returned.

**What do I need to provide?**
Either a full name and a company domain, or a LinkedIn profile URL, per person. No API keys or configuration.

**Can I use private LinkedIn profiles?**
Only public profiles can be read. A profile that is private or no longer exists comes back
with `is_found: false` and is not charged.

**Can I run large lists?**
Yes — it's built for bulk and runs lookups in parallel.

**How accurate are the emails?**
Every returned address is validated before it's handed back, which keeps bounce rates low.

# Actor input Schema

## `leads` (type: `array`):

Your list of people. Each entry is either a full name plus the company's domain (or company name), or a LinkedIn profile URL. When both a full name and a domain are given they are used as is; otherwise the LinkedIn profile is read for the person's name and current employer. Mix both kinds freely. A plain LinkedIn URL string also works as an entry.

## Actor input object example

```json
{
  "leads": [
    {
      "full_name": "Satya Nadella",
      "domain": "microsoft.com"
    },
    {
      "linkedin_url": "https://www.linkedin.com/in/williamhgates/"
    }
  ]
}
```

# Actor output Schema

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

One row per lead: full\_name, domain, email, is\_found, email\_status, company, job\_title and linkedin\_url (the last three are filled for leads given as a LinkedIn profile). When no email was found, email is null, is\_found is false, and that row was not charged.

## `resultsCsv` (type: `string`):

The same rows as a spreadsheet, ready for a CRM import.

## `resultsExcel` (type: `string`):

The same rows as an .xlsx file.

# 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 = {
    "leads": [
        {
            "full_name": "Satya Nadella",
            "domain": "microsoft.com"
        },
        {
            "linkedin_url": "https://www.linkedin.com/in/williamhgates/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zyra/verified-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 = { "leads": [
        {
            "full_name": "Satya Nadella",
            "domain": "microsoft.com",
        },
        { "linkedin_url": "https://www.linkedin.com/in/williamhgates/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zyra/verified-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 '{
  "leads": [
    {
      "full_name": "Satya Nadella",
      "domain": "microsoft.com"
    },
    {
      "linkedin_url": "https://www.linkedin.com/in/williamhgates/"
    }
  ]
}' |
apify call zyra/verified-email-finder --silent --output-dataset

```

## MCP server setup

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