Company Contact Details Extractor - Emails and Phone

🔎 What can Company Contact Details Extractor do?

Give it a company domain. It finds that company's contact page, then returns the role email addresses on it, a main phone number and a postal address, in one flat row per company.

Role addresses only: info@, support@, sales@, privacy@ and their equivalents. A named individual's address is never extracted, by design and not by accident.

📦 What you get	⚙️ Features and integrations
📧 Role email addresses, never a named individual ☎️ Main phone number and postal address when published 🔗 Contact page URL and how it was found 🧾 25 flat fields, snake_case, one row per company	🛡️ Role addresses only by construction, a privacy safe default 🧮 Rejection accounting, emails_rejected_reasons says what was dropped and why 📊 Coverage per row, so a thin read is visible ⬇️ Export to JSON, CSV, Excel, HTML or XML

Bought by outbound teams that need a deliverable role inbox, procurement and vendor onboarding teams, and anyone building a supplier contact sheet from a domain list.

🚫 This is not a people finder and it never returns a personal email address. It returns role mailboxes such as info@, sales@ and support@. If you need a named person's work email, that is the Work Email Waterfall Finder, and it is a different product with different obligations.

💡 Why use Company Contact Details Extractor?

Every address is checked against your domain. A contact page carries the company's addresses and also its hosting provider's, its cookie vendor's and, on a badly built site, its web agency's. A generic email scraper hands you all of them and you clean the list. This one keeps only addresses whose domain is the company's, and tells you on the row how many it dropped and why.

The addresses are classified, not piled up. email_sales and email_support are separate columns, so a sequence that should go to sales does not go to the support desk.

It finds the page properly. Most contact extractors guess /contact and give up. The page location here reads the company's own link graph first and guesses last, in that order, because guessing is what produces most of the misses.

Named individuals are never returned. If you need people, that is a different actor with a different consent posture. This one returns company contact points.

🧭 Four routes to the contact page, strongest first

1. The homepage link graph. The company's own navigation, in eleven languages, so Kontakt and Contatti are found as readily as Contact.
2. The footer specifically, which is where contact, legal and imprint links conventionally live.
3. The sitemap, matched on the URL slug.
4. Three conventional paths, last, and scored as the weak method it is.

The row records which route answered in contact_page_method and how much that route is worth in contact_page_confidence. Confidence is set per method and never blended, so a 0.55 and a 0.88 mean two genuinely different things rather than one averaged one.

📋 What data can Company Contact Details Extractor extract?

Every row carries 25 flat fields. These are the ones a buyer actually filters and sorts on.

Field	Type	Meaning
degraded	boolean	True when this row could not be produced normally, for example the company site was unreachable and no discovery could run. A degraded row is never charged.
degradation_reason	string | null	Why the row is degraded, in plain words. Null on a normal row.
company_domain	string | null	The company domain this row is about, normalized. Null when only a handle or a name was supplied. This is the join key across the whole Mamba Labs fleet.
company_name	string | null	The company name as supplied or derived. Improves search accuracy and is what the identity gate matches against.
contact_page_url	string | null	The located contact page. Null when the site has no contact page reachable from its own link graph, its sitemap or the three conventional paths, which is a real answer and not an error.
contact_page_method	string | null	How the page was located: homepage_anchor, footer_anchor, sitemap or path_guess, strongest first. A path_guess found a page at a conventional URL and nothing on that page confirmed what it is, so filter on this if a wrong page would be expensive for you.
contact_page_confidence	number | null	Confidence in the located page, 0 to 1, set per method and never blended across methods. A link the company itself labelled Contact scores 0.88; a URL that simply answered 200 scores 0.55.
email_general	string | null	The general enquiries role address, for example info@ or hello@. Null when no address of this class was found and kept.
email_support	string | null	The customer support role address, for example support@ or help@.
email_sales	string | null	The sales or partnerships role address, for example sales@ or partnerships@.
email_privacy	string | null	The privacy, data protection or legal role address, for example privacy@ or dpo@. Often the only address a large company publishes, because regulation requires it.
emails_found_count	integer | null	How many distinct addresses were seen on the pages read, before any gate was applied. Zero is a real answer.
emails_rejected_count	integer | null	How many of those addresses were dropped by the gates. A row that found eleven addresses and kept none is a completely different fact from a row that found none, and this column is what tells them apart.
emails_rejected_reasons	string | null	Why addresses were dropped, as counts: foreign_domain (the address belongs to another company), free_mail (a gmail or outlook address, which cannot be checked against your domain), not_a_role_address (a named individual, never extracted by this actor), never_keep (a no-reply or postmaster mailbox). Comma separated.
phone_main	string | null	The company main phone number in E.164 form where the country could be resolved. Null when no number was published or when it is only present inside an image.
phone_source	string | null	Where the number came from: a JSON-LD organization node, a tel: link or the page text, strongest first. A number scraped out of body text is the weakest of the three.
address_line	string | null	Street address as published. Null when the company publishes no postal address, which is normal for a remote first company.
address_city	string | null	City or locality.
address_country	string | null	Country as published, which may be a name or a two letter code depending on the source.
address_source	string | null	jsonld when the address came from a schema.org PostalAddress node, which is authoritative because the company published it as structured data, or footer when it was parsed out of footer text, which is noisy and is marked as such.
contact_form_url	string | null	A form on the contact page carrying both a message field and an email field. Newsletter signups, search boxes and login forms are excluded by name, because none of them is a way to contact the company.
pages_read	integer | null	How many pages were fetched for this company, including the homepage. Useful for reconciling a thin row against what it cost.
coverage	number | null	How much of what this actor can return actually came back on this row, from 0 to 1. Computed over this actor value fields only, never over the identity or status columns. Null on a degraded row, where nothing was attempted. This is a reporting field: nothing is dropped for low coverage and no event fires on it.
fetch_status	string	ok, not_found, not_extractable, blocked, identity_mismatch, auth_failed or skipped. Read this before reading any value on the row. not_found means we looked and there is nothing there; blocked and not_extractable mean we could not look, and they must never be read as an absence.
run_date	string	ISO 8601 timestamp of this run. Social counts move, so a row without a date is a number with no shelf life.

⚠️ How to read these values. emails_rejected_reasons is the field to read when a row looks thin. not_a_role_address=4 means the page carried four individual people's addresses and this actor deliberately did not return them.

🛠️ How to get a company contact email from a domain

1. Put a company domain in company_domain. That is the whole setup.
2. Leave emailTypes on all unless you want one class, for example privacy for a data protection contact sweep.
3. Set allowFreeMailboxes to true for small business or local company lists, where a gmail address on the contact page is often the real one.
4. For a list, pass an array of objects with the same fields.

🧪 Using it in Clay

Add an Enrichment > Apify column, pick this actor, and map company_domain to your domain column. Every output field arrives as its own flat column, snake_case, no nesting.

A useful pattern: run it only on rows where your ICP filter already passed, and use email_sales as the fallback when your people level waterfall returns nothing. A role address is a worse target than a named person and a much better one than an empty cell.

💵 How much does it cost?

Pay per event. You are charged for output, never for input.

Event	Fires when	Price
company-checked	Once per company for which the contact page search completed and a non degraded row was produced, whether or not anything was found. A not_found row fires this event, because looking and finding nothing is a real answer and it is the work you asked for. A degraded row, where the lookup could not run at all, fires nothing.	$0.0035
contact-page-found	Once per company where a contact page was located and fetched. Does not fire when no contact page exists on the site, and does not fire when a page was located but could not be read.	$0.0025
email-extracted	Once per DISTINCT classified role address kept on the row, so a company with a general and a support address fires it twice and a company with none fires it zero times. Addresses dropped by the domain gate or the role gate never charge: the work happened and the honest answer is that there is no address we can vouch for.	$0.0030

💳 What you are billed for. email-extracted fires once per address KEPT, so a company with two role addresses costs two of that event and a company with none costs zero. Addresses dropped by the gates never charge.

A company whose site could not be read at all produces a degraded row and charges nothing.

What the same coverage costs bought a la carte: The Store carries generic email scrapers priced per page or per result and none of them classifies an address by role or gates it on the company domain, so a buyer running one gets a list that mixes the company, its vendors and its staff and has to clean it. page-finder-extractor locates a page but does not extract contacts. There is no like for like actor that takes a domain and returns classified role contact points, which is the whole reason this exists.

⌨️ Input

Field	Type	Required	Meaning
company_domain	string	no	Bare company domain, for example stripe.com. This is the only required input and it is the join key for every other actor in the fleet.
company_name	string	no	Optional. Used in the row and in logging. This actor gates addresses on the email DOMAIN rather than on the company name, so supplying a name does not change which addresses are kept.
emailTypes	string	no	Which classes of role address to return. "all" (default) returns general, support, sales and privacy. The narrower settings return only what they name and leave the other columns null, which is a different answer from not finding one. Sent as a string for Clay compatibility.
includePhones	string	no	When "true" (default) the contact page is scanned for a main phone number. Set "false" to skip phone extraction entirely, which leaves the phone columns null. Sent as a string for Clay compatibility.
includeAddress	string	no	When "true" (default) a postal address is read from JSON-LD first and from the footer second. Set "false" to skip it. Sent as a string for Clay compatibility.
allowFreeMailboxes	string	no	When "false" (default) an address at gmail, outlook or another free provider is rejected, because it cannot be checked against the company domain. Set "true" for small business and local company lists, where a free mailbox on the contact page is often the real contact point. Sent as a string for Clay compatibility.
crawlDepth	string	no	How many pages to read after the homepage. "1" (default) reads the contact page. "2" also reads a support or legal page when the contact page yielded nothing. This is a cost and thoroughness dial, not a change of answer. Sent as a string for Clay compatibility.
skipCache	string	no	When "false" (default) a successful lookup is cached for seven days and reused, which costs you nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.

{
  "company_domain": "stripe.com",
  "company_name": "Stripe",
  "emailTypes": "all",
  "includePhones": "true",
  "includeAddress": "true"
}

📤 Output

Exports to JSON, CSV, Excel, HTML or XML. One flat, snake_case row per company. No nested objects, so it drops straight into Clay, a spreadsheet or a warehouse table without a flattening step.

{
  "degraded": false,
  "degradation_reason": null,
  "company_domain": "stripe.com",
  "company_name": "Stripe",
  "contact_page_url": "https://stripe.com/contact/sales",
  "contact_page_method": "footer_anchor",
  "contact_page_confidence": 0.85,
  "email_general": null,
  "email_support": null,
  "email_sales": "sales@stripe.com",
  "email_privacy": null,
  "emails_found_count": 7,
  "emails_rejected_count": 6,
  "emails_rejected_reasons": "foreign_domain=5, not_a_role_address=1",
  "phone_main": null,
  "phone_source": null,
  "address_line": null,
  "address_city": null,
  "address_country": null,
  "address_source": null,
  "contact_form_url": null,
  "pages_read": 2,
  "coverage": 0.2,
  "fetch_status": "ok",
  "run_date": "2026-08-22T19:23:48.675Z"
}

false versus null, and why the difference matters

false means we looked and the answer is no. null means we could not look, or the platform withheld it. They are never interchangeable in this output. If you filter for companies with no presence on this platform, filter on false, because null rows are unknown rather than absent and including them will overstate your list.

💡 Tips

• Read emails_rejected_reasons before concluding a site publishes nothing. It usually publishes plenty and the addresses belong to people rather than roles.
• email_privacy has the highest hit rate on large companies, because regulation makes them publish it. If you need any address at all for a big enterprise, that is usually the one that exists.
• Turn allowFreeMailboxes on for local business lists and leave it off for B2B software.
• crawlDepth: 2 is worth it on sites with no contact page, where the legal or imprint page carries the address instead. It costs one more fetch.

⚠️ Known limits

• Obfuscated addresses are invisible. An address rendered as an image, assembled in JavaScript, or written as info [at] example.com cannot be read by any static extractor. The row reports not_extractable rather than not_found when obfuscation was detected, because the two mean different things.
• Named individuals are not returned and this is not configurable. There is no setting that turns it on.
• No team pages are walked. Discovery goes to the contact page, and optionally a support or legal page. It never crawls a people directory.
• A phone number inside an image is invisible, for the same reason an email inside an image is.
• Footer parsed addresses are noisy. address_source says whether the address came from structured data or from footer text, and only the first is authoritative.

❓ FAQ

Will this give me a decision maker's email? No. It returns company role addresses only. A named individual's address is dropped by the role gate whether or not you want it.

Why is emails_found_count six and every email column null? Because all six failed a gate. Read emails_rejected_reasons: the usual answer is that they were individuals' addresses or belonged to another domain.

Does it need a proxy or an API key? Neither. It reads the company's own public pages.

What is the difference between a null email column and fetch_status: "not_extractable"? A null column means that class of address was not found. not_extractable on the row means the page was read but its addresses are obfuscated and no static extractor can see them.

Is this GDPR safe? It extracts company contact points, which is what a company publishes a contact page for. It does not extract personal data about named individuals, and it will not do so on request. Your own use of the output is still yours to justify.

🧩 Want other GTM data?

Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay-ready output convention, so their rows join on company_domain with no cleaning step:

🕵️ Agent Accessibility Auditor	🤖 AI Tooling Detector
📡 B2B Buying Signals Aggregator	🚀 Prospect Engine
📝 Publishing Frequency Tracker	⏩ Sequencer Lead Push
🔄 Company Change-Event Feed	🧭 Company Discovery List Builder
🏢 Company Firmographic Enricher	🪪 Company Identity Resolver
🌐 Company Social Presence Mapper	🏷️ Contact Classifier
📬 Domain Deliverability Checker	🔗 Domain to LinkedIn URL Resolver
✉️ Work Email Waterfall Finder	🎪 Event Presence Index
💰 Funding and Press Signal Scanner	🧑‍💼 GTM Hiring Signal Scraper
📋 Job Posting Monitor	🧱 Tech Stack Detector
🎯 ICP Fit Scorer	🔑 Job Board Keyword Scanner
⚖️ Legal Entity Resolver	💼 LinkedIn Company Page Mapper
💬 LinkedIn Post Tracker and Comment Capture	📸 Instagram and Facebook Brand Mapper
📮 Outbound Stack Detector	📄 Page Finder and Extractor
👤 People Finder and Email Verifier	📌 Pinterest Brand Presence Mapper
🏛️ Government Contract Award Monitor	📅 Public Company Reporting Window Finder
👥 Team Page People Extractor	🎵 TikTok Brand Presence Mapper
🏅 Workplace Program Detector	▶️ YouTube Channel Stats Extractor

Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything.

🛠️ Need something custom built for you or your team? Tell us what you are trying to find and we will build it. Talk to Mamba Labs.

🆘 Support

Issues, field requests and bug reports: open an issue on the actor's Issues tab. Mamba Labs reads every one.

ℹ️ Sourcing and legal. Every field is read from pages the company publishes on its own website, with robots.txt honored. Only role addresses are kept and named individual addresses are rejected by construction, which emails_rejected_reasons records. You remain responsible for compliance with applicable marketing and data protection law.

Built by Mamba Labs.