Website Contact Scraper | Emails, Phones & Social Links
Pricing
from $2.55 / 1,000 delivered contact page versions
Website Contact Scraper | Emails, Phones & Social Links
Extract published website emails, phones and social links with source URLs. Optional email-only rows before charging; n8n and Python CSV setup guides included. $3 per 1,000 delivered page versions; no start fee.
Pricing
from $2.55 / 1,000 delivered contact page versions
Rating
0.0
(0)
Developer
Signal Foundry
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Features
Share
Turn a list of public domains or company contact-page URLs into a spreadsheet with source URLs. Each delivered row contains the emails, phone numbers and social profile links found on one page. Contacts are extracted from HTML; mailboxes are not verified.
Choose your setup: Apify Console, n8n to CSV, Python to CSV, or an AI coding assistant.
Paste entries such as example.com, example.com/contact or https://example.com/contact. Domains without a scheme use HTTPS; there is no automatic fallback to HTTP. Duplicate forms of the same normalized URL are fetched once. Existing HTTPS inputs keep the same record identities for repeat-run history.
Start with your use case
| Use case | Preview the input | Copy setup to Apify |
|---|---|---|
| Research software agencies | Software agency public contact pages | Copy agency setup |
| Build a SaaS contact spreadsheet | SaaS public contact pages to CSV | Copy SaaS setup |
| Review a hosting provider's published contacts | Hosting provider public contact audit | Copy hosting setup |
These inputs use public pages as examples. Website content and access rules can change. Replace their URLs with the websites you want to research.
From example to CSV
- Choose Copy setup and sign in to Apify, then review the editable input. For a first run, keep one or two domains or URLs, set
maxPagesPerSiteto1andmaxItemsto10. LeaveincludeEmptyPagesandonlyNewoff. - Set maximum charge to $0.03 in the run options and start the Actor. The base price is $0.003 per delivered page version: ten rows cost $0.03, including platform usage. There is no start fee; eligible Apify plans have lower event prices. A spending cap does not guarantee ten results.
- When the run finishes, open its dataset and export CSV or JSON. In Console, select the columns below if you want a compact spreadsheet. Keep
pageUrlso each contact can be checked at its source.
| Output field | What it contains |
|---|---|
websiteUrl | The starting URL from your input |
pageUrl | The page where the contacts were found |
pageTitle | The page's HTML title, when present |
emails | An array of email addresses found in visible HTML text or mailto: links |
phones | An array of phone numbers found in tel: links or labeled text |
socialLinks | An array of supported social profile links |
One page can contain several contacts in the same row. By default, a row may contain only a phone number or a social link, with an empty emails array. Enable Only pages with an email (requireEmail: true) to omit those rows before delivery and result charging. Use JSON if you want to preserve these arrays directly.
For more sample inputs, try Python and Django contact pages or the project foundation watchlist.
Real result preview
These two page records came from an actual Actor run on 2026-10-02, using the project foundation watchlist with one page per website. Selected published role inboxes and the number of extracted social profile links are shown; other fields and contacts are omitted here.
| Source page | Selected role inboxes from emails | Entries in socialLinks |
|---|---|---|
| Python help | psf@python.org, webmaster@python.org | 6 |
| Django Software Foundation contact | No email extracted | 7 |
With the default requireEmail: false, both are billable page records: a page with only social links can still be delivered. With requireEmail: true, only the Python help row qualifies for delivery; the Django page has no extracted email. The example produced two rows, not one row per individual contact. Website content can change, and extracted email addresses are not mailbox-verified. Copy the preview's source-page setup to review the input before starting your own run.
Keep only page records containing email
Enable Only pages with an email in Input, or set requireEmail: true in an API call:
{"websiteUrls": ["https://www.djangoproject.com/contact/foundation/","www.python.org/about/help/"],"requireEmail": true,"maxPagesPerSite": 1,"maxItems": 1}
No-email pages do not enter the dataset, generate a result charge or consume maxItems. A social-only homepage can still lead to an email-bearing contact/about page when maxPagesPerSite allows it. requireEmail takes precedence over includeEmptyPages. The setting is off by default, so existing input and repeat-run identities stay compatible.
This filter checks whether an email was extracted; it does not validate mailbox existence, ownership or permission to send mail. A row remains one page version with an email array, not one paid result per address. If none of the examined pages contains an email, the dataset is empty. Pages behind JavaScript rendering, contact forms, access restrictions or your page limit may contain contacts this Actor does not see.
What you can do
- Maintain a business directory from public contact pages.
- Prepare a source-linked contact research spreadsheet.
- Refresh an existing company watchlist and skip unchanged contact versions.
Website lists from CSV, including more than 25 starting URLs
The free CSV batch client and setup guide reads a selected website column, removes identical normalized starting URLs, submits sequential batches of up to 25 and combines the returned page records into one CSV. Download the repository so batch_contacts.py and export_contacts.py are in the same folder. The client and guide were created with AI assistance by us, the publisher of this paid Actor.
Run the client without --execute to inspect an offline plan: it makes no API call and needs no token. A hosted job requires your own APIFY_TOKEN, --execute and an explicit --max-total-charge large enough to cover the sum of the batch run caps. For example, 60 unique starting URLs in three batches with a $0.08 cap each reserve a maximum of $0.24 in Actor-run charges. These are caps, not a quote or a guaranteed number of contacts; unrelated account activity and separately billed API/storage usage are outside that bound.
The default scans one starting page per website. --require-email omits no-email rows before result charging. A private checkpoint preserves completed batches and original run IDs; resuming does not recreate a saved run. An interrupted start with no saved ID must be reconciled in Console before recovery. The helper sends no emails, creates no schedule and does not change this Actor's price or per-run input limits. The linked guide includes a synthetic 60-URL planning sample and the limitations of the dated owner checks.
Pricing
The base price is $0.003 per delivered page version ($3 per 1,000 rows), with plan discounts where shown in Apify. A row can include multiple contacts; the price is per delivered row. Identical contact sets repeated on several pages of the same website are emitted only once per run. Pages with no extracted contacts are omitted by default and produce no result charge. If you enable includeEmptyPages, delivered empty-page rows are charged too. When requireEmail: true, pages without an extracted email are omitted and have no result charge, even if includeEmptyPages is also true.
There is no start fee. Apify platform usage is included in this Actor's per-event price. Unchanged versions skipped with onlyNew are not charged. Set a maximum charge in Apify Console or use the API maxTotalChargeUsd parameter.
Quick start
Paste this input in the Actor and choose Start:
{"websiteUrls": ["www.python.org","https://www.djangoproject.com"],"maxPagesPerSite": 3,"includeEmptyPages": false,"maxItems": 10}
For repeated calls, enable onlyNew and reuse stateKey for the same feed. To replay records, change the key or use resetState. History retains the last 25,000 delivered fingerprints; older versions may be delivered again after eviction. Changing your filters with the same key does not clear history. onlyNew scans up to the source scan limit before skipping remembered versions, so repeated runs may read more source records than they deliver. maxItems caps delivered rows.
Export contacts to CSV with n8n
Use the importable workflow or manual recipe below with n8n's built-in nodes; it needs no community-node installation or Google Sheets permission. Connect Manual Trigger → HTTP Request → Code → Convert to File. Keep one trigger item and put the complete website list in one request body: one POST starts one paid Actor run.
Import the ready-made workflow
Download the n8n workflow JSON. In n8n, open the workflow menu, choose Import from URL, and paste that link. You can also save the JSON and choose Import from File.
The template contains four connected built-in nodes and is inactive. Select a private Header Auth credential on Extract contacts — max $0.03: header name Authorization, value Bearer YOUR_APIFY_TOKEN. Edit websiteUrls in that node's JSON body before executing. No token, credential ID or contact results are included in the shared file.
Each manual execution starts one new paid snapshot, with a $0.03 server-side cap and automatic retries disabled. Review the input and current pricing before running it. A lost response may still have started a run; check Apify Console before trying again. Empty results may produce no CSV file.
The JSON settings and embedded transformation were checked locally against the current node definitions; import and execution in a live n8n instance have not been verified. It uses HTTP Request 4.2, Code 2 and Convert to File 1.1. The manual recipe below is available if your instance needs different node settings.
1. Configure the HTTP Request
In a new HTTP Request node, choose Import cURL and paste this command. It intentionally contains no API token:
curl --request POST \--url 'https://api.apify.com/v2/acts/signalfoundryhq~website-contact-extractor/run-sync-get-dataset-items?maxTotalChargeUsd=0.03&memory=256&timeout=120' \--header 'Content-Type: application/json' \--data '{"websiteUrls":["www.python.org/about/help/","https://www.djangoproject.com/contact/foundation/"],"maxPagesPerSite":1,"maxItems":10,"includeEmptyPages":false,"requireEmail":true,"onlyNew":false,"stateKey":"n8n-csv-export"}'
After import, set the body to JSON → Using JSON, then paste the object below. n8n's cURL importer can import values as strings; this step preserves the required numbers and booleans.
{"websiteUrls": ["www.python.org/about/help/","https://www.djangoproject.com/contact/foundation/"],"maxPagesPerSite": 1,"maxItems": 10,"includeEmptyPages": false,"requireEmail": true,"onlyNew": false,"stateKey": "n8n-csv-export"}
For authentication, select Generic Credential Type → Header Auth. Store the header name Authorization and value Bearer YOUR_APIFY_TOKEN in a private n8n credential, replacing the placeholder with your own Apify token. Keep the token out of shared workflow JSON and request URLs.
Set Response Format to JSON, Timeout to 150000 milliseconds, and keep Include Response Headers and Status, Never Error, pagination and Retry On Fail off. Connect the Manual Trigger directly to this node; do not loop the POST once per website or incoming contact.
The query caps this run at $0.03, with a 120-second Actor timeout. At the current base price of $0.003 per delivered page version, ten rows cost $0.03 including platform usage; Store plan discounts can lower that price. requireEmail: true excludes no-email page rows before result charging. The cap does not guarantee ten rows, and the extractor does not verify mailboxes or find private executive emails.
2. Flatten contact arrays
Set the Code node to JavaScript → Run Once for All Items and paste:
// n8n Code node: JavaScript, Run Once for All Items.const fields = ['websiteUrl', 'pageUrl', 'pageTitle', 'emails', 'phones', 'socialLinks'];function spreadsheetCell(value) {const text = Array.isArray(value)? value.map(String).join('; '): value == null ? '' : String(value);const visible = text.replace(/^[\s\uFEFF]+/, '');return /^[=+\-@=+-@]/.test(visible) || /^[\t\r\n]/.test(text)? "'" + text: text;}return $input.all().map((item, index) => {const row = item.json;if (!row || typeof row.pageUrl !== 'string' || !Array.isArray(row.emails)) {throw new Error('Expected a contact dataset row. Check the HTTP response and keep full-response mode off.');}return {json: Object.fromEntries(fields.map(field => [field, spreadsheetCell(row[field])])),pairedItem: { item: index },};});
This keeps one row per delivered page version, joins each contact array into one semicolon-separated cell, and retains its source URLs. Formula-like cells receive a leading apostrophe, including phone numbers beginning with +; that prefix changes the exported string. Import untrusted spreadsheet columns as text and keep the original JSON when you need unmodified phone numbers or arrays.
3. Download the CSV
Set Convert to File to Convert to CSV, put the output file in data, use contacts.csv as the file name, and enable Header Row. Execute the manual workflow after checking the input and charge cap, then download the output file. An empty result array can stop the downstream nodes without producing a file; check the Actor run's dataset and logs before trying again.
Each execution starts a new snapshot run because this example uses onlyNew: false; repeating it can charge for the same records again. If n8n times out or loses the response, inspect recent runs in Apify Console and retrieve the existing dataset before repeating the POST. For jobs beyond the synchronous window, use the asynchronous run API and fetch the dataset when that same run finishes.
References: n8n HTTP Request and cURL import, private HTTP credentials, Code node, Convert to File.
Export contacts to CSV with Python
Download the Python client
Browse the source and setup on GitHub. The public Gist includes the Python client, its README and the synthetic sample dataset; no sign-in is needed to read or download them.
Python client (.py) · Synthetic sample dataset (.json)
Save both linked files in one folder. Try the client without an API token, network request or new Actor run:
$python3 export_contacts.py --from-json sample_contacts.json --output contacts.csv
This writes two CSV rows from synthetic example.com page records. Add --require-email to write one email-bearing row from that same file. These are demonstration records, not collected leads. To scrape real websites, follow the paid-run instructions below. The complete client and its setup guide are available on GitHub.
Download the linked client as export_contacts.py. It uses Python 3.9+ and the standard library. Put one public domain or contact-page URL per line in a UTF-8 file called sites.txt:
www.python.org/about/help/https://www.djangoproject.com/contact/foundation/
Set APIFY_TOKEN to your own Apify API token, then run:
$python3 export_contacts.py --websites sites.txt --output contacts.csv --max-charge 0.03 --max-items 10 --max-pages 1
This starts a new paid Actor run. The default cap is $0.03, with up to ten delivered page versions and one page examined per website. The base price is $0.003 per delivered page version; plan discounts can lower it. The cap and row limit do not guarantee ten results. Repeating this snapshot command starts another run and can charge for the same records again.
For an email-bearing-pages-only CSV, add --require-email:
$python3 export_contacts.py --websites sites.txt --require-email --output contacts-with-email.csv --max-charge 0.03 --max-items 10 --max-pages 1
For a new run, the flag sends requireEmail: true to the Actor, so no-email rows are removed before result charging, rather than hidden afterwards in your CSV. If your starting page has no email, increase --max-pages to examine linked contact/about pages; this does not guarantee a match.
If you already downloaded the dataset as JSON, convert that existing file without a new Actor run or API token:
$python3 export_contacts.py --from-json dataset.json --output contacts.csv
You can also add --require-email to this offline command. It filters the existing JSON locally and cannot change any charges from the original run.
The CSV preserves source-page URLs and stores each contact array in one semicolon-separated cell. It includes a UTF-8 BOM for common spreadsheet imports. Cells that could begin spreadsheet formulas receive a leading apostrophe, including phone numbers starting with +; that prefix is part of the exported data. Spreadsheet behavior varies, especially after saving and reopening a CSV. Import untrusted columns as text and retain the original JSON for automated processing. See OWASP's CSV injection guidance.
The HTTP client sends one POST with a server-side run charge limit and no automatic retries. If the connection fails, inspect the Actor's recent runs in Console before retrying; a broken response does not prove that no run started. This example uses a 120-second Actor timeout and a 150-second client timeout. For longer jobs, use the asynchronous run API and retrieve its dataset after completion.
Export contacts to CSV with an AI coding assistant
The source-linked contacts CSV skill packages this workflow for assistants that support local SKILL.md packages. Download the repository ZIP, then keep the complete skills/apify-source-linked-contacts-csv/ folder: it contains the instructions, Python helper and synthetic sample. Load that folder using your assistant's documented local-skill installation method. Python 3.9+ and its standard library are sufficient for the helper.
Start with a token-free local conversion:
Use the bundled source-linked contacts CSV skill. Convert its sample_contacts.json to contacts.csv locally. Do not access the network or start an Actor run.
For real website data, supply your website list and an explicit spending cap. For example:
Export contacts from these three website URLs to CSV. Keep only pages with published email, inspect one page per site, and spend at most $0.02. Preserve the source URLs. Do not send messages to the extracted contacts.
Replace the example with your own URLs. The skill checks the live input schema and pricing before the first hosted request; a supplied cap limits the charge and does not guarantee a number of matches. It also converts an existing contact JSON dataset without starting another run. Installing or reading the package makes no API call. The skill and helper disclose AI assistance and Signal Foundry's ownership of this paid Actor.
API and export
POST your input to https://api.apify.com/v2/acts/signalfoundryhq~website-contact-extractor/runs?maxTotalChargeUsd=0.05 using an Apify token in the Authorization header. After the run succeeds, read defaultDatasetId from the run and retrieve /v2/datasets/{datasetId}/items. Apify also provides CSV and other exports in Console. OUTPUT contains delivered, duplicatesSkipped and eventChargeLimitReached. Never put tokens in public URLs.
For a compact CSV, request the dataset items with these parameters, using the same Authorization header:
GET https://api.apify.com/v2/datasets/{datasetId}/items?format=csv&clean=true&fields=websiteUrl,pageUrl,pageTitle,emails,phones,socialLinks
Every record includes signalId, recordFingerprint, source, collectedAt and a source page/API URL. Metadata changes create new fingerprints. No background schedule is created by this Actor.
If you get no rows or fewer rows than expected
- Start with the actual contact page. With
maxPagesPerSite: 1, only the starting page is fetched. Use its contact URL directly, or increase the page limit to follow same-origin contact/about/support links. - Check whether the page exposes contacts in HTML. Forms without a published address, contacts inserted by JavaScript and obfuscated addresses may produce no email results. The Actor does not guess addresses or bypass access controls.
- Check run status and logs. A robots exclusion, denied request or non-HTML starting page can fail the run. A successful run can still have an empty dataset when no contacts match.
- Check duplicate history. With
onlyNewenabled,OUTPUT.duplicatesSkippedshows remembered versions that were omitted. TurnonlyNewoff to export them again; delivered rows are charged normally. - Check the limits.
maxItems,maxPagesPerSiteand the maximum charge can stop delivery early.OUTPUT.eventChargeLimitReachedidentifies a result-charge limit. Repeated contact sets within a website are collapsed into one row.
Scope and limitations
Server-rendered HTML only. No browser rendering, login, email guessing, mailbox verification or obfuscation bypass. Contact/about/support links are followed only on the current origin. Default: 3 fetched pages per site; maximum: 25 sites × 10 pages, 250 delivered page rows. Robots exclusions are respected, and private/reserved addresses are rejected. Plain-text phone extraction can be imperfect; values retain the page URL for review. A contact record does not imply permission to contact someone.
Source documentation: Public website HTML. SignalFoundry is independent of the source platform.
Related tool
For product prices, SKUs and stock flags from public WooCommerce catalogs, use WooCommerce Products Scraper. It is a separate Actor priced at $0.0015 per delivered product version.
Support
Open an issue on this Actor with the run URL and a non-sensitive description of the problem. Do not include tokens, passwords or private data.