# Contact Page Finder (`eichan/contact-page-finder`) Actor

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

## Pricing

$3.00 / 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?

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

## Contact Page Finder

### What it does

Finds **one contact page linked from the homepage** of one user-provided official public business domain. It recognizes common contact/inquiry text and URL paths (including Japanese `お問い合わせ`), ranks up to three on-site candidates, and returns the highest-ranked page that actually responds with HTML. The Actor does **not** collect emails, phone numbers, names, or form contents.

### Who it is for

B2B research and sales-operations teams who have known company domains and need a public general contact-page URL without harvesting personal contact details.

### Input example (one domain)

```json
{"domain":"example.com"}
```

The Apify input UI prefills only one domain. Replace it with an official corporate domain; no login or URL list is needed.

### Output example

Illustrative JSON schema, not a claim about the sample domain:

```json
{
  "domain": "sample-business.example",
  "contact_url": "https://sample-business.example/contact/",
  "source_url": "https://sample-business.example/",
  "status": "found",
  "error": null
}
```

When no homepage link can be verified, `contact_url` is `null` and `status` is `not_found`. If input, homepage retrieval, or `robots.txt` checks fail, an English plain-language error is logged and the run exits nonzero with no dataset item; no Python traceback is printed.

### Limits and source policy

- **One domain per run.** Reads one homepage (maximum 1 MB HTML), examines at most 400 homepage anchors, and verifies **at most three** matching linked pages (not a recursive crawler).
- Only URLs found in official homepage `<a href>` links; no guessing of `/contact` paths, search engines, LinkedIn scraping, or third-party directories.
- Ignores `mailto:`, `tel:`, social profiles, external links, and links with custom ports. Removes tracking/query strings from candidate links; contact pages that require query parameters may therefore be missed.
- Only apex/`www` of the supplied domain; HTTPS first with HTTP connection fallback, up to three redirects, nine seconds per HTTP request, max 1 MB downloaded per page. JavaScript-only navigation is not available.
- Checks `robots.txt` before fetching pages; disallowed or unavailable robots rules (other than 404/410) are not bypassed. Private/non-public network addresses are blocked before requests. DNS validation is not a replacement for a network-level egress firewall against DNS rebinding.
- A **verified URL** means an accessible HTML page whose official homepage link appears contact-related, **not** independently validated form deliverability. A site with only a footer-generated JS link may return `not_found`.
- No login, individual names, email harvesting, or contact-form submissions.

### Apify configuration and dataset

Standalone project: `.actor/actor.json` points to `input_schema.json`; `src/main.py` uses Python's standard library, directly reads the run's input via Apify REST API, and writes the result to the default dataset. `APIFY_IS_AT_HOME=true` selects cloud storage via `APIFY_API_BASE_URL`, `APIFY_INPUT_KEY`, `APIFY_DEFAULT_KEY_VALUE_STORE_ID`, `APIFY_DEFAULT_DATASET_ID`, and `APIFY_TOKEN`. Bearer tokens are not placed in URLs or logs.

For local testing, create `storage/key_value_stores/default/INPUT.json` containing the input, then run:

```bash
python src/main.py
```

Alternatively set `ACTOR_INPUT_JSON='{"domain":"example.com"}'` before execution. Results are appended locally under `storage/datasets/default/` as one numbered JSON file per item. When using Docker locally, mount `storage` at `/usr/src/app/storage`. The `storage` directory is not included in this deliverable.

### Store placement and suggested pricing

**Suggested Apify Store categories (max 3):** Generate leads · Find contact information · Company research. These are suggestions for Store classification, not extra `actor.json` keys; Apify is rolling out platform-assigned categorization.

**Suggested monetization:** Pay per event (PPE), synthetic `apify-default-dataset-item`, **$0.003 per emitted dataset item** (~**$3 per 1,000 items**) with optional small actor-start fee if needed for per-run costs. Configure it manually in Apify Console after testing: monetization is **not enabled in these files**. `found` and `not_found` both create a dataset item and would count toward synthetic item billing; errors create none. At one result per run, verify actual compute and networking costs before setting a live price.

# Actor input Schema

## `domain` (type: `string`):

Exactly one public company domain; no login, paths, IPs, credentials, or custom ports.

## Actor input object example

```json
{
  "domain": "example.com"
}
```

# Actor output Schema

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

Dataset containing the Actor's result items

# 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 = {
    "domain": "example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("eichan/contact-page-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 = { "domain": "example.com" }

# Run the Actor and wait for it to finish
run = client.actor("eichan/contact-page-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 '{
  "domain": "example.com"
}' |
apify call eichan/contact-page-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eichan/contact-page-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/3E28d0cdbsYjbdOZV/builds/Sjw0nIIzho3DIiczk/openapi.json