Website Contact Extractor
Pricing
$3.00 / 1,000 site with contacts
Website Contact Extractor
Emails, phone numbers and social profiles from a company website: homepage plus its contact, about and imprint pages.
Pricing
$3.00 / 1,000 site with contacts
Rating
0.0
(0)
Developer
Gabor Molnar
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
16 hours ago
Last modified
Categories
Share
Get the email addresses, phone numbers and social profiles a company publishes on its own website. Pass one domain or a list of up to 1,000 in a single run. For each site the Actor reads the homepage and up to three of its contact, about, team and imprint pages, and returns one clean record. You pay only for sites where it found something.
What you get
One dataset item per site you send. Here is one of them, for input heise.de:
{"domain": "heise.de","reasonCode": "contacts_found","emails": ["newstipps@heise.de", "webmaster@heise.de"],"phones": ["+4951153520", "+495115352129"],"socials": [{ "network": "instagram", "url": "https://instagram.com/heiseonline" },{ "network": "linkedin", "url": "https://linkedin.com/company/heiseonline" }],"pagesCrawled": ["https://www.heise.de/","https://www.heise.de/kontakt/","https://www.heise.de/impressum.html"]}
Use it when
- You have a list of company domains and need a way to reach each one.
- You are enriching leads from a CRM export or a scraped directory.
- You want a company's official LinkedIn, X, Facebook, Instagram, YouTube, TikTok or GitHub account, not a share button or a policy page.
- An agent needs one typed contact record per domain.
Input
| Field | Type | Required | What it does |
|---|---|---|---|
domains | array of strings | yes | The websites to read, up to 1,000 per run. A URL or an email address is accepted and reduced to its site, so https://acme.com/pricing and jane@acme.com both mean acme.com. A site that appears more than once is read and charged once. |
Output
| Field | What it holds |
|---|---|
domain | The site that was read, normalized. |
reasonCode | What happened. See the pricing table. |
emails | Every address found, lowercased and deduplicated. Addresses inside scripts and styles are ignored, so SDK keys and logo@2x.png don't show up. |
phones | Valid numbers in E.164 form. Taken from tel: links and from page text written the way people write phone numbers. A number with no country code uses the site's country domain (.de means Germany). A number that doesn't validate is dropped, not guessed at. |
socials | Profile links, one per account, in canonical form (twitter.com/acme becomes x.com/acme). |
pagesCrawled | The pages that were actually read, after redirects. |
Pricing
Pay per event, $3.00 per 1,000 sites with contacts ($0.003 each), charged on the website-contacts-found event.
You pay only when the Actor found at least one contact. If a site loads but shows nothing we recognize, that is free, because a site that draws its contact details with JavaScript looks exactly the same.
reasonCode | Charged |
|---|---|
contacts_found | yes |
no_contacts_found (the pages loaded and held no contacts) | no |
blocked (the site refused us with 401, 403 or 429) | no |
unreachable (no DNS, no connection, a timeout, or a server error) | no |
invalid_domain (an IP, a bare TLD, localhost, a malformed name) | no |
If you set a maximum total charge for a run, the Actor stops as soon as that limit is reached instead of working for free. Items after that point are left out of the dataset and not charged, and the run log says how many; submit them in a new run.
Limits
- Pages are read as HTML. Contacts that appear only after JavaScript runs are not seen.
- At most four pages per site: the homepage plus three contact-type pages linked from it.
- Sites are read one after another. If you set a maximum charge for the run, or the run reaches its timeout, it stops there. The items already written stay in the dataset, so you can re-run the remainder.
Personal data
The Actor reads only pages a site shows to every visitor, at most four per site, and identifies itself with an honest User-Agent. What it returns can still include personal data, such as a named employee's address or a direct line. You decide what that data is used for, so under the GDPR and similar laws you are the controller: you need a lawful basis for processing it (for B2B outreach that is usually legitimate interest), and you must honor objections and opt-outs. Results go to your own Apify dataset under your account's retention settings. The Actor keeps no copy.