# Website Contact Finder - pay only when contacts are found (`forge_creations/website-contact-finder`) Actor

Give it a list of websites; get each site's contact page, contact form, emails, phone numbers (E.164), social profiles and address, with the source page for every value. Respects robots.txt. You pay only for websites where something is found.

- **URL**: https://apify.com/forge_creations/website-contact-finder.md
- **Developed by:** [Forge Creations](https://apify.com/forge_creations) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 website with contacts founds

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?

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

## Website Contact Finder: pay only when contacts are found

Give it a list of websites. For each one it reads the home page and a few likely contact or about pages on the same site, then returns what the site itself publishes:

- **Contact page URL**, and whether the site has a **contact form**
- **Emails** shown on the site, flagged as role-based (info@, sales@) or personal
- **Phone numbers**, normalized to E.164 (+14125550100)
- **Social profiles**: Facebook, Instagram, LinkedIn, X, YouTube, TikTok, Pinterest, GitHub, Threads
- **Postal address**, when the site publishes schema.org data
- The **source page** for every value, so you can check it

### Pricing

You pay **$0.002 per website where at least one contact channel is found** (about $2 per 1,000), plus Apify's standard start fee of $0.00005 per run.
Websites where nothing is found, sites that are unreachable, and sites whose robots.txt disallows reading are not charged the per-website fee. They still appear in the results with a status, so you know what happened.

### Input

```json
{ "websites": ["example.com", "https://www.another-example.org"], "maxPagesPerWebsite": 4 }
```

| Field | Default | Notes |
|---|---|---|
| websites | required | Domains or URLs. Duplicates are removed. |
| maxPagesPerWebsite | 4 | 1-10 pages per site (home page plus likely contact pages). |
| maxConcurrency | 10 | Websites processed in parallel. |
| defaultPhoneRegion | US | Used for local numbers when the domain has no country code. |

### Output (one row per website)

`input, url, final_url, status (ok | no_contacts | unreachable | robots_disallowed | invalid_input), contact_page_url, has_contact_form, contact_form_page, emails[{value, role_based, same_domain, source}], phones[{e164, raw, source}], socials{platform: url}, address{...,source}, pages_checked[], has_contacts`

### What it does not do

- It does not guess or generate email addresses, and it does not verify deliverability.
- It does not log in, solve CAPTCHAs, use other people's data sources, or read pages that robots.txt disallows.
- It reads plain HTML without a browser. Sites that load contact details only through JavaScript may show fewer results; you are not charged when nothing is found.
- You are responsible for using contact data lawfully (for example, CAN-SPAM, GDPR and the site's terms).

### Support

Open an issue on this Actor's Issues tab. Reports with the website and run ID get fixed fastest.

# Actor input Schema

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

Domains or URLs, one per line (e.g. example.com). Duplicates are removed.

## `maxPagesPerWebsite` (type: `integer`):

Home page plus likely contact/about pages. 1-10.

## `maxConcurrency` (type: `integer`):

How many websites are processed in parallel. Lower it if target sites are slow.

## `defaultPhoneRegion` (type: `string`):

Two-letter country code used to read local phone numbers when the domain has no country TLD.

## Actor input object example

```json
{
  "websites": [
    "python.org",
    "w3.org"
  ],
  "maxPagesPerWebsite": 4,
  "maxConcurrency": 10,
  "defaultPhoneRegion": "US"
}
```

# Actor output Schema

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

One row per website: contact page, form, emails, phones, socials and address, each with its source page.

# 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": [
        "python.org",
        "w3.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("forge_creations/website-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": [
        "python.org",
        "w3.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("forge_creations/website-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": [
    "python.org",
    "w3.org"
  ]
}' |
apify call forge_creations/website-contact-finder --silent --output-dataset

```

## MCP server setup

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