# Business Contact & Lead Finder (`apexfaucetdotxyz/lead-contact-finder`) Actor

Crawl company websites for contact details, filter the junk, and separate named decision-makers from generic inboxes.

- **URL**: https://apify.com/apexfaucetdotxyz/lead-contact-finder.md
- **Developed by:** [Martin Raum](https://apify.com/apexfaucetdotxyz) (community)
- **Categories:** Lead generation, Business, Automation
- **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?

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

## Business Contact & Lead Finder

Give it company websites. Get back contactable people.

### What it returns

**Named decision-makers with job titles** — not just an `info@` address. On a real
run: `Bryn Richards [CEO]`, `Peter Morris [Founder]`, `Adam Kudryl [Director]`.
With a name and a title you can infer the email pattern; with `info@` you cannot.
Many SMB sites list their whole team while hiding emails behind a contact form, so
this recovers leads an email-only scraper reports as nothing — one accountancy
firm returned 41 named staff and zero emails.

### The filtering is the product

A plain email regex over a homepage returns `noreply@`, Sentry ingest keys,
`logo@2x.png`, Facebook's tracking pixel and the web agency's own address. A lead
list you have to clean by hand is worth very little. This one:

- **Separates named humans from generic inboxes.** `sarah.jones@acme.com` is a
  lead. `info@acme.com` is a switchboard. They are returned in different fields
  because they are worth different amounts.
- **Flags off-domain emails** rather than hiding them — an address on another
  domain is usually the agency or a partner, not your prospect.
- **Reads the site's own navigation** instead of guessing URLs. Guessed paths
  return styled 404s that still parse as pages — `/our-team` looked like a
  successful scrape and was a not-found. Discovered links are the real pages,
  and this roughly tripled the yield.
- **Trusts `mailto:` and `tel:` links first**, because a human marked those up.
- **Refuses obvious junk.** An early version returned `2015-2026` — a copyright
  year range — as a phone number. Now a match needs a country code, parentheses
  or real separators, and 9-15 digits.

### Output

```json
{
  "website": "https://hjsolicitors.co.uk", "ok": true, "leadScore": 54,
  "peopleCount": 13,
  "people": [{ "name": "Bryn Richards", "title": "CEO" },
             { "name": "Toby Harper", "title": "Founder" }],
  "personalEmails": [], "roleEmails": ["enquiries@harperjames.co.uk"],
  "offDomainEmails": ["enquiries@harperjames.co.uk"],
  "phones": ["0800 689 1700"],
  "linkedinCompany": "linkedin.com/company/harper-james-solicitors",
  "socials": ["facebook.com/hjsolicitors", "linkedin.com/company/harper-james-solicitors"]
}
```

`leadScore` (0-100) weights named people and personal emails highest, then role
inboxes, then a phone and a LinkedIn company page.

A site that could not be fetched is returned with `ok: false` and the reason —
never silently dropped, because a missing row reads as "this company has no
contact details" when the truth is the site did not load.

### Works outside English

Contact-page names and job titles are matched in English, Spanish, German,
French, Italian, Portuguese and Dutch — `kontakt`, `impressum`, `quiénes-somos`,
`equipo`, `chi-siamo`, and titles like `Socio Director` or `Geschäftsführerin`.
The English-only first version found zero people on every Spanish site tested.

Site-builder social accounts are also filtered: a Valencia dental clinic was
reporting `linkedin.com/company/wix-com` as its own page. Shipping a vendor's
profile as the lead's is worse than shipping nothing, because it looks like data.

### Honest expectations

Yield depends on the sector. Professional services, trades and local businesses
publish staff pages and contact details. Large consumer brands hide behind contact
forms and will often return only a phone, socials and whatever names are public.
Page headings are filtered out — an early version reported "Who We Help" as a CEO. Use `onlyWithEmail` if you only want to
pay for records that carry an address.

### Pairs with

Feed it the website column from any company or directory scraper — this is the
enrichment step that turns a list of names into a list you can actually contact.

# Actor input Schema

## `websites` (type: `array`):

Domains or URLs to enrich, e.g. "acme.co.uk" or "https://acme.co.uk". Feed it the output of any company-list scraper.

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

How many pages to crawl per site. The crawler reads the site's own navigation to find real contact/team pages, so more pages means more named people found.

## `onlyWithEmail` (type: `boolean`):

Skip records with no email. Note: many good leads are named people WITHOUT an email, so leaving this off usually returns more usable results.

## `proxyConfiguration` (type: `object`):

Optional. Most business sites do not block datacenter IPs; enable if you hit blocks at volume.

## Actor input object example

```json
{
  "websites": [
    "hjsolicitors.co.uk",
    "perrysaccountants.co.uk"
  ],
  "maxPagesPerSite": 10,
  "onlyWithEmail": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

Companies with named decision-makers, emails and phones.

## `overview` (type: `string`):

Browse the results as a table.

# 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 = {
    "websites": [
        "hjsolicitors.co.uk",
        "perrysaccountants.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apexfaucetdotxyz/lead-contact-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 = { "websites": [
        "hjsolicitors.co.uk",
        "perrysaccountants.co.uk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("apexfaucetdotxyz/lead-contact-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 '{
  "websites": [
    "hjsolicitors.co.uk",
    "perrysaccountants.co.uk"
  ]
}' |
apify call apexfaucetdotxyz/lead-contact-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apexfaucetdotxyz/lead-contact-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/BUhgl7AKUYwDZ7fpZ/builds/R6EqNg59FOiSNanlG/openapi.json