# Website Contact Finder: Emails, Phones & Social Links (`ninoventures/website-contact-finder`) Actor

Give websites or domains, get one row per site with the emails, phone numbers and social profiles (LinkedIn, X, Facebook, Instagram, YouTube, TikTok...) published on the homepage and its contact, about and imprint pages. You pay only for sites where something was found: $3 per 1,000.

- **URL**: https://apify.com/ninoventures/website-contact-finder.md
- **Developed by:** [Nino Ventures](https://apify.com/ninoventures) (community)
- **Categories:** Lead generation, Automation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 website with contacts

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: Emails, Phones & Social Links

Give it a list of websites. For each one it reads the homepage and the pages most likely to have contact details (contact, about, imprint/Impressum, team, support, in English, Dutch, German, French, Spanish, Italian and Portuguese) and returns **one row per website**: emails, phone numbers, social profiles, and the company name and address when the site publishes them as structured data.

**Price: $3 per 1,000 websites where something was found.** Sites with no contact details, sites that don't load, and duplicates are free. No start fee.

### Output

```json
{
  "domain": "manufactum.de",
  "companyName": "Manufactum",
  "address": "Hiberniastraße 5, 45731, Waltrop, DE",
  "emails": ["info@manufactum.de", "behoerdenkontakt@manufactum.de", "produktsicherheit@manufactum.de"],
  "emailDetails": [{ "email": "info@manufactum.de", "foundOn": "https://www.manufactum.de/", "sameDomain": true }],
  "phones": [{ "phone": "+49230993900", "foundOn": "https://www.manufactum.de/impressum-c199455/" }, "...4 more"],
  "socials": { "facebook": ["..."], "instagram": ["https://instagram.com/manufactum"], "pinterest": ["..."] },
  "linkedin": null,
  "instagram": "https://instagram.com/manufactum",
  "pagesScanned": ["https://www.manufactum.de/", "https://www.manufactum.de/impressum-c199455/", "https://www.manufactum.de/kontakt-c199446/"],
  "status": "ok",
  "hasContacts": true
}
```

The `linkedin`, `x`, `facebook`, `instagram` and `youtube` columns hold the first profile found so the table and CSV stay flat; `socials` has all of them, including TikTok, Pinterest, GitHub, Threads, Telegram and WhatsApp links.

Every email has a `foundOn` page and a `sameDomain` flag. Imprint pages often list other organisations (a bank's imprint names its regulator, for example). Turn on **Only emails on the site's own domain** to drop those.

### How it finds things

- `mailto:` and `tel:` links
- Email addresses written in the page text, including Cloudflare-obfuscated ones
- Links to social profiles (share buttons and post links are ignored)
- schema.org `Organization` / `LocalBusiness` JSON-LD: name, address, telephone, email, `sameAs` profiles

Phone numbers only come from `tel:` links and structured data, not from guessing digits in text. That keeps out order numbers and VAT IDs, but means a number written only as plain text is missed.

### Test run numbers

50 websites (shops, agencies, restaurants, SaaS, banks) in the US, UK, NL, DE, FR and DK on 31 October 2026, default settings:

- 111 seconds on 1 GB memory, platform cost $0.006.
- 46 sites loaded. 4 blocked the request (HTTP 403 or 429 from bot protection) and were free; Apify Proxy didn't change that.
- 44 sites had at least one contact detail and were charged: $0.13 for the run.
- Emails on 26 sites (25 with an address on their own domain), phone numbers on 13, social profiles on 42 (Instagram 36, LinkedIn 26), a postal address on 12.
- 2 sites render everything with JavaScript and returned nothing (free).

Large brands often hide email behind contact forms, so expect fewer emails on big consumer sites and more on small businesses, agencies and anyone with an imprint page (German, Austrian and Dutch sites almost always have one).

### Limits

- No browser: sites that build their pages entirely in JavaScript, or sit behind a Cloudflare/Akamai challenge, return nothing. You're not charged for them.
- Contact forms aren't submitted or read.
- It doesn't guess or verify addresses. What you get is what the site publishes.

### Use the data responsibly

This actor collects what businesses publish on their own sites. Emails of named people are still personal data under GDPR and similar laws. Cold email to businesses is regulated differently per country (in the Netherlands and Germany, for example, unsolicited commercial email usually needs prior consent). Check the rules that apply to you before contacting anyone.

### Questions or bugs

Open an issue on the Issues tab with the domain that went wrong.

# Actor input Schema

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

Domains or URLs, one per line: example.com, https://www.example.com/contact. Duplicates are removed.

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

The homepage plus the most likely contact pages (contact, about, imprint/Impressum, team, support) in many languages.

## `sameDomainEmailsOnly` (type: `boolean`):

Drops addresses like regulators or partners that a site mentions (e.g. poststelle@bafin.de on a bank's imprint). Off by default; every email has a sameDomain flag either way.

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

Usually not needed. Turn on if many sites answer with HTTP 403.

## Actor input object example

```json
{
  "websites": [
    "basecamp.com",
    "plausible.io",
    "hetzner.com"
  ],
  "maxPagesPerSite": 6,
  "sameDomainEmailsOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `contacts` (type: `string`):

No description

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

No description

# 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": [
        "basecamp.com",
        "plausible.io",
        "hetzner.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ninoventures/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": [
        "basecamp.com",
        "plausible.io",
        "hetzner.com",
    ] }

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

```

## MCP server setup

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