# Website Contact Finder — Every Email Verified (`alaudinburki/lead-finder-verified-emails`) Actor

Give it company websites (or domains from a Google Maps export) and get contact emails, phones and social profiles — with every email verified against live DNS before it reaches your dataset. No stale database rows.

- **URL**: https://apify.com/alaudinburki/lead-finder-verified-emails.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Contact Finder — Every Email Verified

Give it company websites (or domains from a Google Maps export) and get contact emails, phones and social profiles — with every email verified against live DNS before it reaches your dataset. No stale database rows.

Built reliability-first: **every row reports what was found and what was missing** — you never get a
silent blank, and a run summary tells you exactly what happened.

### What you get

| Field | Description |
|---|---|
| `site` | Site |
| `companyName` | Company Name |
| `email` | Email |
| `emailStatus` | Email Status |
| `emailReason` | Email Reason |
| `isRoleAccount` | Is Role Account |
| `phones` | Phones |
| `linkedin` | Linkedin |
| `foundOnPage` | Found On Page |

### How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or **schedule it** to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

### Input

```json
{
  "domains": [
    "apify.com"
  ],
  "startUrls": [],
  "maxPagesPerSite": 5,
  "maxLeads": 500,
  "includeSitesWithoutEmails": true
}
```

### Sample output

```json
[
{
  "site": "example",
  "companyName": "Example companyName",
  "email": "name@example.com",
  "emailStatus": "name@example.com",
  "emailReason": "name@example.com",
  "isRoleAccount": 1284,
  "phones": "example",
  "linkedin": "https://example.com/item/1",
  "foundOnPage": 42
}
]
```

### Typical uses

- **Google Maps → outreach pipeline**: Maps scraper → this Actor → your CRM, fully on Apify.
- **List cleaning at the source**: instead of buying 10K stale rows and verifying them, collect 500 fresh ones already verified.
- **Local lead gen agencies**: one scheduled run per niche+city list, deduped, graded, CSV-ready.

### Pricing

**$1.60 / 1,000 results** (`$0.0016` per result), plus a near-zero start fee. You are **never charged beyond your limit**, and blocked or
failed items are reported honestly — not billed as data.

### FAQ & limitations

- Public data only — no login walls, no cookies required.
- Rate limits on the source may require the proxy or a retry on very large pulls.
- Every row reports its own status, so partial results are always labeled, never faked.
- **Integrations:** output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
- **Formats:** results export as JSON, CSV, Excel, or HTML from the dataset.

### Related actors

- **Email Verifier**
- **Lead List Deduplicator**
- **Website Contact Finder**

# Actor input Schema

## `domains` (type: `array`):

Company domains to scan, one per line (with or without https://). Invalid entries are reported and skipped, never silently dropped.

## `startUrls` (type: `array`):

Full page URLs to start from instead of (or in addition to) the domains list.

## `maxPagesPerSite` (type: `integer`):

Homepage plus up to this many contact-like pages (contact, about, team, impressum...). 5 finds nearly everything; raise it for very large sites.

## `maxLeads` (type: `integer`):

Hard limit on output rows. Strictly enforced — you will never be charged for more than this.

## `includeSitesWithoutEmails` (type: `boolean`):

On: sites with no published email still get one row saying so (with phones/socials if found) — you always know every site was actually scanned. Off: only rows with an email.

## `findPeople` (type: `boolean`):

Extract people (name + role) from team/about pages, and work out the company's email convention from any address that belongs to one of them. A named contact with a title is worth far more than a generic info@ address.

## `guessMissingEmails` (type: `boolean`):

For a person found without a published address, build one from the company's convention. These are clearly labelled (emailSource: pattern\_inferred / guessed) and are NEVER presented as found. Off by default — a constructed address is a hypothesis, not a lead.

## Actor input object example

```json
{
  "domains": [
    "apify.com"
  ],
  "startUrls": [],
  "maxPagesPerSite": 5,
  "maxLeads": 500,
  "includeSitesWithoutEmails": true,
  "findPeople": true,
  "guessMissingEmails": false
}
```

# Actor output Schema

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

The dataset of results produced by this run.

# 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 = {
    "domains": [
        "apify.com"
    ],
    "startUrls": [],
    "maxPagesPerSite": 5,
    "maxLeads": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/lead-finder-verified-emails").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 = {
    "domains": ["apify.com"],
    "startUrls": [],
    "maxPagesPerSite": 5,
    "maxLeads": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/lead-finder-verified-emails").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 '{
  "domains": [
    "apify.com"
  ],
  "startUrls": [],
  "maxPagesPerSite": 5,
  "maxLeads": 500
}' |
apify call alaudinburki/lead-finder-verified-emails --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/lead-finder-verified-emails"
        }
    }
}

```

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/TF5bJBf5mDrJBG8bG/builds/jmv13YdXjT22qnROU/openapi.json