Find emails and phone numbers from a list of websites in n8n
Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site.
What this workflow does
Import it and n8n runs the Website Contact Page Email & Phone Crawler Actor on Apify every day at 08:00 with the starter input below. Each row comes back with website url, status, company name, emails and 22 more; repeats with the same websiteUrl are dropped. A Google Sheets append is included and stays off until you add your sheet. The only credential it needs is your Apify API token.
Read from the workflow file, built for Website Contact Page Email & Phone Crawler version 1.1.3. Updated 2026-11-14.How the rows travel
6 nodes, in the order n8n runs them. The yellow stop is the call to the Apify Actor; the dashed stop is optional.
- Daily trigger Schedule trigger
- Configure input Code
- Run Apify Actor HTTP Request
- Normalize + dedupe Code
- Rows ready No operation
- Google Sheets (optional) Google Sheets, off until you switch it on
From the Short
This workflow is the one the video points to: the number in each video opens this page.
Input
The Configure input node holds the starter input. Change it there; every setting the Actor accepts is listed below.
{
"urls": [
"https://apify.com",
"https://n8n.io"
],
"maxPagesPerSite": 10
}| Setting | Type | Required | Default | What it does |
|---|---|---|---|---|
| urls | array | Yes | – | Websites to scan for public contact details. You can paste full URLs or bare domains; duplicates are removed. |
| maxPagesPerSite | integer | No | 20 | Maximum number of pages to fetch per website. Contact, about, team and imprint pages are prioritised. |
| maxConcurrency | integer | No | 5 | How many pages of the same website may be fetched in parallel. |
| maxSitesConcurrency | integer | No | 3 | How many websites are scanned in parallel. Lower this if you hit rate limits. |
| requestTimeoutSecs | integer | No | 15 | Maximum time to wait for one page before trying the next proxy tier. |
| defaultCountry | string | No | – | ISO 3166-1 alpha-2 country used to interpret phone numbers written without an international prefix. Leave empty to infer from the website domain. 245 choices. |
| useProxy | boolean | No | false | 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 | No | true | Try common contact, about, team, imprint and support paths first, and queue contact-like links ahead of other internal links. |
| respectRobotsTxt | boolean | No | true | 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 | No | true | Read sitemap.xml and robots.txt sitemap entries to find contact and about pages that are not linked from the homepage. |
| renderFallback | boolean | No | true | 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 | No | false | Drop records for websites where no email, phone, social profile or contact form was found. |
| includeNamedEmails | boolean | No | true | Include personal addresses such as jane.smith@company.com. When off, only role addresses such as info@, sales@ and support@ are kept. |
What each row holds
Every field the Actor returns stays in the row (26 in its dataset schema). Normalize + dedupe trims text, drops empty fields, removes repeats with the same websiteUrl and adds _source and _scrapedAt. The main fields:
| Field | What it is |
|---|---|
| websiteUrl | Website Url |
| status | Status |
| companyName | Company Name |
| emails | Emails |
| primaryEmail | Primary Email |
| roleEmails | Role Emails |
| namedEmails | Named Emails |
| emailDetails | Email Details |
| phones | Phones |
| primaryPhone | Primary Phone |
| phoneDetails | Phone Details |
| socialLinks | Social Links |
| socialProfiles | Social Profiles |
| address | Address |
| contactPageUrl | Contact Page Url |
| contactForms | Contact Forms |
| pagesCrawled | Pages Crawled |
| pagesCrawledUrls | Pages Crawled Urls |
| maxDepthReached | Max Depth Reached |
| skippedByRobots | Skipped By Robots |
| browserUsed | Browser Used |
What the first run costs
Each run starts at $0.40 on the Free plan (4 GB of memory), then $0.99 per 1,000 results, plus platform usage.
The Actor lists $0.99 per 1,000 results; its catalogue page breaks the price down by Apify plan. The Apify Free plan includes $5 of usage a month.
The Actor behind it
Website Contact Page Email & Phone Crawler: Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site.
The same job from an AI agent
The matching agent skill gives Claude Code, Codex, Cursor and other agents the same Actor, input and fields. Install it in one line:
npx skills add https://scraperfinder.com --skill website-contact-page-email-and-phone-crawler The find emails and phone numbers from a list of websites skill, with manual install and run steps
Questions people ask
How do I import this workflow into n8n?
Copy https://scraperfinder.com/n8n/website-contact-page-email-and-phone-crawler.json. In n8n, open a new workflow, click the three-dot menu, choose Import from URL and paste it. Or download the JSON file and use Import from File; both give the same 6 nodes.
Do I need an Apify account?
Yes. The workflow calls the Website Contact Page Email & Phone Crawler Actor through the Apify API with your own token, and each run is billed to your Apify account. The Free plan includes $5 of usage a month.
What does a run cost?
Each run starts at $0.40 on the Free plan (4 GB of memory), then $0.99 per 1,000 results, plus platform usage. The Actor's Store page shows the current price.
Can I change what it collects?
Yes: edit the input object in the Configure input node. The Actor takes 13 settings; the table on this page lists each one with its default.
Does it work without Google Sheets?
Yes. The rows wait in the Rows ready node, so you can connect any other node there: a database, Airtable, a webhook or an email. The Google Sheets node is only one option.
Workflow updated 2026-11-14