Company Role Email, Phone and Address Finder avatar

Company Role Email, Phone and Address Finder

Pricing

from $2.45 / 1,000 company checkeds

Go to Apify Store
Company Role Email, Phone and Address Finder

Company Role Email, Phone and Address Finder

From a domain, the company's role email addresses, main phone, and postal address in one row, never a named person. Role addresses only, never a named individual. Clay ready, one row per company.

Pricing

from $2.45 / 1,000 company checkeds

Rating

0.0

(0)

Developer

Mamba Labs

Mamba Labs

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

0

Monthly active users

11 hours ago

Last modified

Features

Limited permissions

Share

What's new (October 2026)

  • Social profile links. Every row now carries linkedin_url, x_url, instagram_url, facebook_url, youtube_url, and tiktok_url, read from the pages the actor already fetches (JSON-LD sameAs first, then page links). On by default, no extra request, and coverage and fetch_status are computed as before.

No price change. Existing fields and saved inputs work as before.

🔎 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
🧾 36 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 36 flat fields. These are the ones a buyer actually filters and sorts on.

FieldTypeMeaning
degradedbooleanTrue 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_reasonstring | nullWhy the row is degraded, in plain words. Null on a normal row.
company_domainstring | nullThe 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_namestring | nullThe company name as supplied or derived. Improves search accuracy and is what the identity gate matches against.
contact_page_urlstring | nullThe 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_methodstring | nullHow 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_confidencenumber | nullConfidence 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_generalstring | nullThe general enquiries role address, for example info@ or hello@. Null when no address of this class was found and kept.
email_supportstring | nullThe customer support role address, for example support@ or help@.
email_salesstring | nullThe sales or partnerships role address, for example sales@ or partnerships@.
email_privacystring | nullThe 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_countinteger | nullHow many distinct addresses were seen on the pages read, before any gate was applied. Zero is a real answer.
emails_rejected_countinteger | nullHow 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_reasonsstring | nullWhy 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_mainstring | nullThe 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_sourcestring | nullWhere 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.
phone_pagestring | nullWhich page the number came from: contact (the located contact page), support or legal (read at crawl depth 2 when the contact route kept nothing), or homepage. The contact page is tried first and the homepage after it. Null when no number was found.
address_linestring | nullStreet address as published. Null when the company publishes no postal address, which is normal for a remote first company.
address_citystring | nullCity or locality.
address_countrystring | nullCountry as published, which may be a name or a two letter code depending on the source.
address_sourcestring | nulljsonld 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.
address_pagestring | nullWhich page the address came from: contact (the located contact page), support or legal (read at crawl depth 2 when the contact route kept nothing), or homepage. A JSON-LD address on the homepage outranks a footer parse on the contact page. Null when no address was found.
contact_form_urlstring | nullA 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.
linkedin_urlstring | nullThe company LinkedIn page linked from the pages this actor read, JSON-LD sameAs first, then page links. Null when none is linked.
x_urlstring | nullThe company X or Twitter profile linked from the pages read.
instagram_urlstring | nullThe company Instagram profile linked from the pages read.
facebook_urlstring | nullThe company Facebook page linked from the pages read. Share buttons are skipped.
youtube_urlstring | nullThe company YouTube channel linked from the pages read.
tiktok_urlstring | nullThe company TikTok profile linked from the pages read.
pages_readinteger | nullHow many pages were fetched for this company, including the homepage. Useful for reconciling a thin row against what it cost.
coveragenumber | nullHow 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_statusstringok, 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.
row_statusstring | nullok when the lookup ran and found what it looked for, no_match when it ran and there is nothing to find, incomplete when the platform withheld or refused part of it (the reason is in error_reason), error when the row could not be produced. Read from fetch_status and degraded.
error_reasonstring | nullWhy the row is incomplete or an error, in plain words. Null on an ok or no_match row.
billable_events_jsonstringThe pay per event charges this row caused, as a JSON array of {"event","count"}. [] when the row charged nothing. The once per run apify-actor-start event is not on any row.
run_datestringISO 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, put the domains in company_domains, one per line, or 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. Every run is also charged Apify's platform start event, apify-actor-start, at $0.00005 per GB of run memory, one event and $0.00005 at this actor's default of 512 MB. Every other event below is charged only when the work it names is done, as listed. Prices shown are the free plan price; paid Apify plans pay 10 to 30 percent less per event, depending on the plan.

Free Apify plan: up to 900 results per calendar month, reset on the 1st. Any paid Apify plan removes the cap.

Spend limits. Set max_charge_usd and the run stops before its charges pass that amount. The maximum cost per run you set in Apify is honored the same way. Either way every row already charged is kept, and each row lists its own charges in billable_events_json.

EventFires whenPrice
company-checkedOnce 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-foundOnce 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-extractedOnce 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

FieldTypeRequiredMeaning
company_domainstringnoBare 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_namestringnoOptional. 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.
emailTypesstringnoWhich 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.
includePhonesstringnoWhen "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.
includeAddressstringnoWhen "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.
allowFreeMailboxesstringnoWhen "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.
crawlDepthstringnoHow 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.
skipCachestringnoWhen "false" (default) repeat lookups inside seven days are served from cache; a cached row is still charged the same events as a fresh one: company-checked, plus contact-page-found and email-extracted when the row carries them. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
company_domainsarraynoOptional. A list of bare company domains, one per line, for example stripe.com. Each domain becomes its own row, so a list of 500 is one run and one start charge instead of 500. Per company fields above (name, handle, ids) apply only to the single Company Domain row, never to the list.
max_charge_usdnumbernoOptional. The run stops before its event charges pass this amount, for example 2.50. Every row already charged is kept. Leave empty for no cap beyond the maximum cost per run you set in Apify, which is also honored.
{
"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,
"phone_page": null,
"address_line": null,
"address_city": null,
"address_country": null,
"address_source": null,
"address_page": null,
"contact_form_url": null,
"linkedin_url": "https://www.linkedin.com/company/stripe",
"x_url": "https://twitter.com/stripe",
"instagram_url": "https://instagram.com/stripehq",
"facebook_url": "https://www.facebook.com/StripeHQ",
"youtube_url": "https://youtube.com/@stripe",
"tiktok_url": null,
"pages_read": 2,
"coverage": 0.2,
"fetch_status": "ok",
"row_status": "ok",
"error_reason": null,
"billable_events_json": "[{\"event\":\"company-checked\",\"count\":1}]",
"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.
  • Social links come only from the pages read. A profile the company does not link from its homepage or contact page is null. Follower counts are not read here; Company Social Presence Mapper returns them.
  • 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:

ActorActor ID
Account Hiring WatchgRAZA5WBi1r6L0gy7
Agent Accessibility AuditoranxbRv0lKrpQ1pnua
Agent to Brokerage ResolverePRRGLxOGyaVHO4dI
AI Answer Visibility TrackerRJZvzKniYK4nswcMg
AI List Extractor for Any WebsiteD5hOdIez45M0NX5jD
AI Tooling DetectorEwkHhmqiuJgRoVEbE
Amazon Product, Price, and Stock TrackerMtJPZoyjJ3IeqTFyo
Amazon Top Reviews Scraperwh6Mq6G6BlW1CRPwx
API Deprecation and Breaking Change MonitorpHsbS3xXUK8Jqutz5
App Store and Google Play Review MonitorMaCMEhGrbchxQZ92G
B2B Reddit Conversation MonitorSoDryzzsjmY3SsiyG
B2B Social Video TranscriptsdG2UYVKE2e4zfDucK
Bluesky Brand Presence MappereLpxzP4IuXznlFVND
Bluesky Posts ScraperKldSjS7wjoeZ7vQGm
Brand Sponsor FinderPPgK6xrgOmvL7Nrys
Bulk WHOIS and RDAP Domain Age LookupMTrkG5FLU6SjqLdJY
Business PDF Field ExtractorvM7JCk0CMAx5W0oJh
Career Change Signal EnginevX2Yga1a6wGaXaP14
Company Careers Page Jobs, 17 ATS BoardsizP0rfIgf5YaRZfIh
Company Change Event FeedoX44rS0fkEJ3rXLWe
Company Discovery List Builderjch0HdaZnpbMqlcGS
Company Firmographic EnricherYlUtLWjfPpqykmB8g
Company Funding RecordOFS4Mt1gyYNtGfUbE
Company Headcount EstimatoraHC4GROnNt6kfZe5r
Company Identity Resolverlr8fTRAmZCBZmuwwh
Company Role Email, Phone and Address Finder4mMncKaJykiq94grz
Company Social Presence Mapper4k6CCemkgBDz18m2h
Competitor Price, Stock, and Changelog MonitoryxdgCbUQ4PYQWwRNU
Contact Classifier0lGSeYJmniXhGANnO
Contractor License Search, CA, TX, WA, OR, LAWBYK3CPI2kdeq4bP1
CRM Contact Job Change CheckerL8UbEmMJC1XYPSZOb
Domain Deliverability Checker0tVgxI7A6o9jMlxmc
Domain to LinkedIn URL Resolver3HtnSaqPHOg1Qg5gx
Ecommerce Platform Profiler5G2NeYjBbQTjaTn9L
Ecommerce Store DiscoveryPeHu4sLyFvQHXUUrX
Email List Verifier, Bring Your Own KeyCzVJ4NlaCKk80xpgE
Event Presence IndexWLhMy8fMDgsxdYxv5
Eventbrite Events Scrapersgc6znyrbjOy5Yk9f
Expert Witness Finder, US and AustraliaLIpwlgfE3LaQBaXd4
Facebook Posts ScraperT6jxIeq4ua0SLXnqG
Facebook Reels ScraperAkOg4iNPHwYZD7Q5E
Funding and Press Signal ScannerFS13X6dhQVgX3XOM6
GDPR Cookie Banner and Consent CheckerTrKyOS0KBoGC35nbr
GitHub Followers and Following ExportSGNxDmFb9v3tRDaFI
GitHub Organization Signal ScannerahF8RRpv5mzPao5CN
Google Ads Transparency Center Scraper by Domain1eOwxhBVxzvOXAm4s
Google Flights FaresoVCatSfzcXbkFfcav
Google Maps Places ScraperSuvHCNJ7pIuw6gn54
Google Trends ScraperOeDzaACKmBYJXzHZk
GTM Hiring Signal ScraperD7O1SA2EqwHGsGr1P
GTM Signals AggregatorxKdRfnfFNkdMpFuNs
Healthcare Provider NPI EnricherMrgbHzcpDq3mOv9Df
ICP Fit ScorerW161DT8W4kW55dMFh
Influencer Change Monitord2VVgahNL6UmcLkhg
Influencer Lead List BuilderKnmByszcv135yM30G
Influencer Profile ScraperEqEnklDVMIcB1V499
Influencer Search Across TikTok, Instagram and YouTubetpkedmloIIWtXx6sg
Influencer Talent Agency LookupzCuX4Mgyg6JvXgGzd
Instagram Facebook Brand Presence MapperHXh65I0JBjPsunbY8
Integration and Marketplace Presence MapperV0guNuvM85Q61f2gj
Job Board Keyword Signal Scanner4DvqpvhMR74NLcDDY
Job Posting Liveness CheckerqRI0ohsnkCwLeDKtw
Job Posting MonitorQCfICD9kOPiOdj5iI
Journalist and Media List BuildermAfizsZC8qRoR0ecS
Kick Channels, Streams, and ClipsREl7yEdagIx2YvoQU
Launch Directory List BuildercRq3bmvEZxZtioQ7U
Lead File Import CheckerRwlGVXTf46LqZdUgt
Legal Entity ResolverKHFyPCDIx7CyqULYm
Link in Bio Scraper and Newsletter DetectorOorucdheTIgu7RFzK
LinkedIn Company Page DetailsN9rfy1Cj2FRTOawvx
LinkedIn Company Page MapperzOPm6A9JEhUGcIdFW
LinkedIn Jobs FeedSH6N0d8cz46BhCC8B
LinkedIn Post TrackeroiGLNPuaf5BRaz9K5
Local Business Lead BuilderqMN97aoHhsAS5bznV
Local Rank and Map Pack Trackergv0kyHGDIg8XscclB
Lookalike Companies from Seed Domainse2O426WBAbLLQL4Z2
Manufacturer and Supplier FinderQcsdmd0lUfPzVkonh
MCP Server Change and Health MonitorIeqjWF9U0BdDQFY08
Media URL TranscriberSyfr7Ya3EsHgWfrB6
Medium Articles Scrapervw3X3RXnB353CXdxC
Meta Ad Library Ads by Company, Graph APIJ1GWlSXfSGU3u8Wng
Mobile Phone Waterfall6OOgPktf7RIa5XCOP
Multi Platform Social Posts and CommentsicFuHR1EzDvUcfCQ5
Netherlands Rental ListingssGKGsbwoX18lFb6dR
New Hire FindercKuc38p4nYHNF3IW8
Newly Registered Companies, UK, Norway, Finland, Franceg2WfZhWvCtc57g2Jo
News and Media Mention Monitorgol1PPUKrsIk4QLBd
News Site Article ArchiveNjcF3UD8791raFNHh
Newsletter Sponsor TrackerqSwpqxD1TiPZpLQHv
Open Tender and RFP FinderkPTGz6t6TFoUUyfaO
Outbound Stack Detectorv43UJC8r7qW7cBSTG
Page Finder and ExtractorTpurgcOZbVnknlaiC
Partner and Member Directory ExtractorZX0XJPPUvnFJxeC1a
People Finder & Email VerifierLEgloG7tWgQl4o6TD
Person LinkedIn URL ResolverssuyPV8LnEsL8qbnb
Person Social Footprint MapperjfQXa2zW9FHCJot9K
Personal Email to Company ResolverAefT5Ye6YNPFQwJBf
Pinterest Brand Presence Mapperd1HvjZfKhgvWsoEwn
Podcast Guest and Host Findero2MGSvgbSLeeXOsIo
Private Company Funding HistoryH02K3rQIVOYpnLYc3
Product Hunt Daily Launches with Maker DomainsO4VX63drWK9Y9x641
Property Owner Records0J7ovG1iaZpQD1P0T
Prospect Engineq9rT6v64nUJdPexOQ
Public Feature Board and Roadmap MonitorrcHF5gj5r2Vqnry35
Publishing Frequency TrackerTbLwaUUATdYb6wp4N
Recent Funding Rounds FeedKueVp9MOz7iOoAgDp
Reddit Brand Presence MapperpKQZmDaT70SEb54bZ
Reddit Search and Thread Scraper4Gsth5cP2Xt9V2xDN
Reporting Window FinderuINxR7a1IW8qUTRUX
Research Topic Institutions and AuthorsOH8ANqt7bCKbo72Gk
Semrush Domain Metrics3dqa0abJrpssHtrYL
Sequencer Event PollerS6s8Rjd61tGdrMRk4
Sequencer Lead Push0Jv27VeWM5tSZQs9x
Shopify App Store and Chrome Web Store ListingsgaY0BzkLyN77mD3wI
Site Crawler for Links and TableslLLJ6JxZ4XqN8ULz0
Sports Scores and FixturesyLoRnLcvqptp08cvX
Streaming Subscription Prices by CountrytbMroS2Zyn57bW17E
Substack Newsletter and Posts ScraperUEFsdwiPLmPNVy9xd
Team Page People Extractorj8a9zX0k4mNbvDbWK
Tech Stack Signal Detectorqyd7nNyqFPelQViBx
Tennis Match Datav3OX6zxXHZOf2yurO
Threads Posts by Keyword, Exact Match2OT8K8RiEEWtaj2MW
Threads Profile and PostsMbwVXjHdBt01kr2aF
Ticketmaster Event PricesCrvPX4IwLXQX9bls1
TikTok Brand Presence Mapperfco8FvoJcSafbeyd1
TikTok Video Statsuz9Q3cEycRgA6NfqA
Trustpilot Reputation Enricher3lIqfCt61j4hqE1xz
US and UK Contract Award Winners by CompanyzhEtllASykOcx9hJ8
US Import Records Buyer FinderVIMafpKF5ggOw0COU
VC and Accelerator Portfolio List BuilderchH8hrfuoqqolW06m
Website Accessibility Checker, WCAG 2.2 AAP3jBj3FRghKEhX52z
Website Phrase and Business Model ClassifierCBuZ9k7sRwBeiKiCS
Website Screenshot CapturenWd9M6qngY0sFiM8N
Website Traffic Rank EstimatorGnOFUzlNVIoXgeJjH
Work Email WaterfallOT6xqTFThC0Rjf7Zj
Workplace Program DetectorLi6pPDhqbdzFz3h7G
X Brand Presence MapperoLOgadhHUkNAyDA3w
YouTube Channel and Video List ScrapertxaAjeBqgj5MStFE4
YouTube Channel Email FinderIDgKZcmeeuunUbccN
YouTube Channel from Company Domain6hSpD3kd2s2IQ4VSs
YouTube Shorts ScraperjUTHnhThr8jaI5ZQS
Zillow Listing DetailsyG4zM0Enfsw2NefJ1

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.

🆘 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.