Website Contact Page Email & Phone Crawler: one-request API, MCP and n8n

{
  "urls": [
    "https://apify.com"
  ],
  "maxPagesPerSite": 5,
  "maxConcurrency": 5,
  "maxSitesConcurrency": 3,
  "requestTimeoutSecs": 15,
  "useProxy": false,
  "smartPrioritise": true,
  "respectRobotsTxt": true,
  "useSitemap": true,
  "renderFallback": true,
  "onlyWithContacts": false,
  "includeNamedEmails": true
}

---
name: website-contact-page-email-and-phone-crawler
description: "One record per scanned website with source-backed emails, E.164 phone numbers, social profiles, company name, address, contact forms, crawl diagnostics and status. Runs the Apify Actor nimbryxo-studio/website-contact-page-email-and-phone-crawler. Use when the user needs Website Contact Page data and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/website-contact-page-email-and-phone-crawler"
  store-url: "https://apify.com/nimbryxo-studio/website-contact-page-email-and-phone-crawler"
---

# Website Contact Page Email & Phone Crawler

Use this skill to fetch Website Contact Page data with the Apify Actor `nimbryxo-studio/website-contact-page-email-and-phone-crawler` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `urls` | array, required | Websites to scan for public contact details. You can paste full URLs or bare domains; duplicates are removed. |
| `maxPagesPerSite` | integer | Maximum number of pages to fetch per website. Contact, about, team and imprint pages are prioritised. |
| `maxConcurrency` | integer | How many pages of the same website may be fetched in parallel. |
| `maxSitesConcurrency` | integer | How many websites are scanned in parallel. Lower this if you hit rate limits. |
| `requestTimeoutSecs` | integer | Maximum time to wait for one page before trying the next proxy tier. |
| `defaultCountry` | string | ISO 3166-1 alpha-2 country used to interpret phone numbers written without an international prefix. Leave empty to infer from the website domain. |
| `useProxy` | boolean | Start with the Apify proxy ladder instead of trying direct requests first. The actor always retries blocked requests through the proxy ladder automatically. |
| `smartPrioritise` | boolean | Try common contact, about, team, imprint and support paths first, and queue contact-like links ahead of other internal links. |
| `respectRobotsTxt` | boolean | Skip pages that the website's robots.txt disallows. Turn this off only when you own the site or have permission to crawl it. |
| `useSitemap` | boolean | Read sitemap.xml and robots.txt sitemap entries to find contact and about pages that are not linked from the homepage. |
| `renderFallback` | boolean | If plain HTML contains no email or phone, render up to two pages in a headless browser to capture contacts loaded by JavaScript. |
| `onlyWithContacts` | boolean | Drop records for websites where no email, phone, social profile or contact form was found. |
| `includeNamedEmails` | boolean | Include personal addresses such as jane.smith@company.com. When off, only role addresses such as info@, sales@ and support@ are kept. |

Example `input.json` (the Actor's published prefill):

```json
{
  "urls": [
    "https://apify.com"
  ],
  "maxPagesPerSite": 5,
  "maxConcurrency": 5,
  "maxSitesConcurrency": 3,
  "requestTimeoutSecs": 15,
  "useProxy": false,
  "smartPrioritise": true,
  "respectRobotsTxt": true,
  "useSitemap": true,
  "renderFallback": true,
  "onlyWithContacts": false,
  "includeNamedEmails": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~website-contact-page-email-and-phone-crawler/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~website-contact-page-email-and-phone-crawler/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. The Actor does not publish an output schema, so inspect the first item before mapping fields.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.