Thomasnet Email Scraper

Thomasnet Email Scraper - public manufacturer contact emails from thomasnet.com

The Thomasnet Email Scraper collects publicly indexed contact emails that appear in Google search results for thomasnet.com. Thomasnet is the long-running North American industrial sourcing platform, descended from the printed Thomas Register, and it exists so that buyers can find and contact manufacturers.

That purpose is why this Actor works at all. A Thomasnet supplier profile is published to attract RFQs, so sales, quoting and enquiry addresses sit in public view rather than behind a login.

The Thomasnet Email Scraper turns that public layer into a structured dataset. It builds Google site:thomasnet.com queries, reads the result pages through the Apify GOOGLE_SERP proxy, and extracts every email matching your domain filter.

The audience is industrial rather than consumer. Procurement teams, MRO and OEM buyers, plant and facility managers, import agents, industrial distributors and trade-show organisers all need a repeatable way to reach many manufacturers at once.

A measured live result, stated plainly

A live Google run of the Thomasnet Email Scraper returned 10 result blocks, 10 rows with account identity, 10 resolvable profile URLs and 6 unique emails. Those are the observed figures from a real run.

Complete identity resolution is the notable part. Thomasnet exposes a clean company slug under /profile/, so the Thomasnet Email Scraper produced a usable username and profileUrl on every row it found.

Six unique emails from ten blocks on the default webmail filter is a normal ratio for an industrial directory. North American manufacturers lean heavily on corporate mail, which makes widening customDomains the single most valuable change you can make.

Features of the Thomasnet Email Scraper

Every feature below is genuinely implemented. Nothing here is aspirational.

Feature	What it means in practice
Google SERP parsing	Reads Google result pages through the Apify GOOGLE_SERP proxy. No browser, no JavaScript rendering
Structural block detection	Locates the <h3> title, then the smallest surrounding block. Does not depend on Google's CSS class names
Domain filter	Only emails ending in one of your customDomains values are kept
Query expansion	Base, quoted, intitle: and one variant per query modifier. Base queries run first
Global deduplication	An email seen once is never pushed twice, across every query and every page
Email normalisation	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠ sign
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same block
Concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Retries	Up to 3 attempts per page, exponential backoff, a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Re-queueing	Blocked or failed queries are retried once at the end of the run
Resumable run	State is stored in the key-value store, keyed by a hash of the input, and saved on PERSIST_STATE, MIGRATING and ABORTING
Fallback parser	If Google's markup changes, the run degrades to "emails without account details" rather than "no emails"
Run summary	Logs pages fetched, blocked pages, retries and emails per page
Dataset output	Rows push immediately and export to CSV, JSON, Excel or XML from the Apify dataset

Query expansion matters unusually much inside the Thomasnet Email Scraper. Thomasnet organises suppliers into tens of thousands of narrow product categories, and a single broad query can only ever scratch the surface of that index.

How the Thomasnet Email Scraper works

The pipeline is six steps and there is nothing hidden inside it.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google search queries with the site: operator against thomasnet.com, for example site:thomasnet.com industrial supplier "@gmail.com" "Ohio".
3. It fetches Google result pages through the Apify GOOGLE_SERP proxy using aiohttp, asynchronously.
4. It parses each result block structurally, finding the <h3> title and the smallest block around it.
5. It extracts emails from that block's text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight into the Apify dataset.

The Thomasnet Email Scraper does not log into Thomasnet, does not use any Thomasnet API, and does not open the site in a browser. Every field comes from publicly indexed Google search results - titles, snippets and site labels, with no authentication and no cookies.

Who the Thomasnet Email Scraper is built for

This is a procurement and industrial sales tool, and its users are the people who source parts, machines and services rather than the people who market to consumers.

Procurement teams and category buyers use it to build a North American vendor shortlist before an RFQ cycle, particularly during reshoring or supplier-diversification reviews. Design engineers and plant managers use it to find a contract manufacturer capable of a specific process.

Import and export agents use it to identify US and Canadian companies open to international trade. Industrial distributors use it to spot manufacturers without territory coverage, and trade-show organisers use it to recruit exhibitors from named industrial segments.

If your prospects are local consumer-facing businesses rather than industrial suppliers, the Thomasnet Email Scraper is the wrong Actor and Fyple Email Scraper or Cybo Email Scraper will fit better.

Input fields for the Thomasnet Email Scraper

Field	Type	Default	Meaning
keywords	array (required)	["manufacturer", "industrial supplier"]	Search terms - niche, job title, industry
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; the @ is optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "export", "wholesale", "sales enquiries"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

How the Thomasnet Email Scraper input fields actually behave

keywords is where the industrial specificity goes. The defaults manufacturer and industrial supplier are broad, and Thomasnet rewards replacing them with process or product terms such as cnc machining, metal stamping, injection molding or industrial gaskets.

queryModifiers only fire when expandQueries is true. The defaults export, wholesale and sales enquiries steer queries towards the parts of a supplier profile where a contact route is printed.

customDomains decides your ceiling. Established North American manufacturers usually publish a corporate address, so adding @outlook.com, @hotmail.com, @aol.com or a specific supplier domain broadens what the Thomasnet Email Scraper can keep.

maxEmails is a hard stop shared across the worker pool. Raising it does not create leads that are not indexed; it simply lets the run finish the expanded query set.

maxConcurrency and maxPagesPerQuery trade throughput against politeness, and the defaults of 5 and 30 are sensible for a single large domain.

JSON input example for the Thomasnet Email Scraper

{
  "keywords": ["cnc machining", "metal stamping", "injection molding"],
  "location": "Ohio",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com", "@aol.com"],
  "maxEmails": 200,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "export", "wholesale", "sales enquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

That is a realistic sourcing configuration for the Thomasnet Email Scraper: three specific manufacturing processes, a state-level location, a US country code and a widened domain filter.

Thomasnet is an English-language North American platform, so unlike the European directories in this family there is no multilingual angle to exploit here. Specificity of process terminology is what replaces it.

Output fields of the Thomasnet Email Scraper

Every dataset item carries all fourteen fields.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints
fullName	Display name parsed from a profile-style title; empty for non-profile results
username	URL-safe handle when the platform exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio or snippet text, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, for example @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email - verify before sending
foundAt	ISO 8601 UTC timestamp

On Thomasnet, username and profileUrl are populated on most rows because supplier pages live under a stable /profile/ slug. The Thomasnet Email Scraper builds the canonical link as https://www.thomasnet.com/profile/{username}.

Always check possiblyTruncated before you send. When it is true, Google's snippet ellipsis may have clipped the address and it should be confirmed on the source page.

JSON output example from the Thomasnet Email Scraper

[
  {
    "network": "Thomasnet",
    "keyword": "cnc machining",
    "query": "site:thomasnet.com cnc machining contact \"@gmail.com\" \"Ohio\"",
    "title": "Midwest Precision Machining Inc. - Cleveland, OH - Thomasnet",
    "accountName": "Midwest Precision Machining Inc.",
    "fullName": "Midwest Precision Machining Inc.",
    "username": "midwest-precision-machining-30412708",
    "profileUrl": "https://www.thomasnet.com/profile/midwest-precision-machining-30412708",
    "url": "https://www.thomasnet.com/profile/midwest-precision-machining-30412708",
    "description": "CNC turning and milling job shop serving aerospace and automotive OEMs. RFQ and quoting contact.",
    "email": "quotes.midwestprecision@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-29T11:21:06Z"
  },
  {
    "network": "Thomasnet",
    "keyword": "metal stamping",
    "query": "site:thomasnet.com metal stamping \"sales enquiries\" \"@outlook.com\"",
    "title": "Great Lakes Stamping Co. - Toledo, OH - Thomasnet",
    "accountName": "Great Lakes Stamping Co.",
    "fullName": "Great Lakes Stamping Co.",
    "username": "great-lakes-stamping-30988145",
    "profileUrl": "https://www.thomasnet.com/profile/great-lakes-stamping-30988145",
    "url": "https://www.thomasnet.com/profile/great-lakes-stamping-30988145",
    "description": "Progressive die stamping and short-run fabrication. Wholesale and OEM supply, ISO certified.",
    "email": "sales.greatlakesstamping@outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-29T11:22:33Z"
  }
]

Use cases for the Thomasnet Email Scraper

Audience	What they do with the data
Procurement and category buyers	Build a North American vendor shortlist before an RFQ cycle
MRO and OEM sourcing teams	Find alternate suppliers for a part number or process at risk
Design engineers and plant managers	Reach contract manufacturers capable of a specific process
Import and export agents	Identify US and Canadian firms open to international trade
Industrial distributors	Spot manufacturers with no territory representation and pitch distribution
Trade-show and expo organisers	Recruit exhibitors from named industrial and manufacturing segments
Industrial marketing agencies	Assemble a manufacturer prospect list for an account-based campaign
Supply-chain researchers	Map which manufacturing categories publish contact routes and where

Each of these is outbound work aimed at a company inbox that a supplier published to attract quote requests. That is the honest boundary of what the Thomasnet Email Scraper does.

Targeting tips for the Thomasnet Email Scraper

location and countryCode are both real levers here, and North American manufacturing is regional enough to make them worth using.

location appends a phrase to every query, so "Ohio", "Michigan", "Ontario" or "Greater Houston" narrows to an industrial belt rather than a whole continent. Buyers who need a supplier within trucking distance should always set it.

countryCode changes the search proxy's country. Setting US or CA shifts which regional Thomasnet pages Google prefers, and the Canadian slice of the index behaves noticeably differently from the American one.

Because Thomasnet is single-language, your leverage comes from vocabulary rather than translation. Use trade terminology - swiss screw machining, powder coating, EDM wire cutting - instead of generic words like factory.

Keep expandQueries on so the modifiers reach the pages where addresses appear. For overlapping European industrial coverage, run Europages Email Scraper or Kompass Email Scraper with the same product terms.

Limitations of the Thomasnet Email Scraper

Read all of these before your first run.

• The Thomasnet Email Scraper only finds addresses that are publicly visible in Google's index. Anything Google has not indexed is invisible to it.
• Google caps a single query at roughly 300 results, which is exactly why query expansion exists and defaults to on.
• possiblyTruncated: true means Google's snippet ellipsis may have cut the email short. Verify it before sending.
• It requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
• Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
• username and profileUrl are only populated when Google exposes a handle. Thomasnet usually does, but rows built from category or search pages can still arrive with username: null and an empty profileUrl. That is a Google limitation, not a bug.
• Results vary with keywords, domains and location. No volume is guaranteed by the Thomasnet Email Scraper or by any Actor in this family.

Responsible use of Thomasnet Email Scraper output

The addresses the Thomasnet Email Scraper surfaces are business contacts that manufacturers published on an industrial sourcing platform so that buyers could send them enquiries. Treat them accordingly.

Even in a B2B context, a named individual's work address is personal data under GDPR when that person is in scope, and US rules such as CAN-SPAM apply to commercial mail regardless. Record your lawful basis, identify yourself in the first line, and make the relevance obvious.

Honour opt-outs immediately and permanently, keep your list current, and follow the marketing rules of each jurisdiction you contact. Do not use this output for bulk unsolicited mail.

FAQ about the Thomasnet Email Scraper

How many results should I expect from the Thomasnet Email Scraper?

A live Google run returned 10 result blocks, 10 identified accounts, 10 profile URLs and 6 unique emails on default settings. Volume scales with how many keyword and domain combinations you supply, so ten process keywords across five domains will produce far more than the default pairing. No specific number is guaranteed, because everything depends on what Google has indexed.

Does the Thomasnet Email Scraper log into Thomasnet or use its API?

No. It builds Google site:thomasnet.com queries, fetches result pages through the Apify GOOGLE_SERP proxy and parses them. There is no browser, no login, no API and no cookies.

Why do most Thomasnet Email Scraper rows have a working profile URL?

Because Thomasnet supplier pages sit under a stable /profile/ slug that Google prints in the result. The Thomasnet Email Scraper derives username from that slug and builds profileUrl from it.

What is the fastest way to increase Thomasnet Email Scraper yield?

Widen customDomains beyond the two webmail defaults, and use precise process keywords instead of generic ones. Established manufacturers frequently publish on corporate or secondary webmail domains.

Should I use non-English keywords?

Not usually. Thomasnet is a North American English-language platform, so translated terms add little. For multilingual sourcing, use Kompass Email Scraper or Europages Email Scraper instead.

Can the Thomasnet Email Scraper find addresses on a manufacturer's own domain?

Only if the address appears in the Google result block and you list that domain in customDomains. The filter compares the end of each address, so every domain you want must be in the array.

Why does the Thomasnet Email Scraper turn expandQueries on by default?

Google caps one query at roughly 300 results. Expansion runs base, quoted and intitle: variants plus one per modifier, reaching category pages a single query cannot. Base queries always run first.

Can I run the Thomasnet Email Scraper on a free Apify plan?

Yes. Free plans are capped at 100 emails per run, and paid plans are uncapped.

What happens if a Thomasnet Email Scraper run is interrupted?

State is saved in the key-value store, keyed by a hash of your input, and written on Apify's PERSIST_STATE, MIGRATING and ABORTING events. Restarting with the same input resumes rather than starting over.

Which export formats are available?

Anything the Apify dataset supports - CSV, JSON, Excel and XML - plus the API for pushing rows straight into a CRM or sourcing system.

Is the Thomasnet Email Scraper affiliated with Thomasnet?

No. It is an independent Actor that reads publicly indexed Google results and has no relationship with, or endorsement from, the platform.

Which other Actor pairs best with the Thomasnet Email Scraper?

For European industrial supply, Europages Email Scraper and Kompass Email Scraper. For Asian export supply, EC21 Email Scraper and TradeIndia Email Scraper.

Related Actors

More email scrapers from the same Business & Professional Directories family, built on the same Google SERP pipeline.

Actor	What it collects
Thomasnet Email and Phone Number Scraper	Emails and phone numbers from Thomasnet
Thomasnet Phone Number Scraper	Public phone numbers from Thomasnet
Angi Email Scraper	Public contact emails from Angi
Bark Email Scraper	Public contact emails from Bark
Better Business Bureau Email Scraper	Public contact emails from Better Business Bureau
Bizapedia Email Scraper	Public contact emails from Bizapedia
Brownbook Email Scraper	Public contact emails from Brownbook
Callupcontact Email Scraper	Public contact emails from CallUpContact
Capterra Email Scraper	Public contact emails from Capterra
Clutch Email Scraper	Public contact emails from Clutch
Crunchbase Email Scraper	Public contact emails from Crunchbase
Cybo Email Scraper	Public contact emails from Cybo
Cylex Email Scraper	Public contact emails from Cylex
EC21 Email Scraper	Public contact emails from EC21
Europages Email Scraper	Public contact emails from Europages
ExportHub Email Scraper	Public contact emails from ExportHub
FindUsLocal Email Scraper	Public contact emails from FindUsLocal
Foursquare Email Scraper	Public contact emails from Foursquare
Fyple Email Scraper	Public contact emails from Fyple
G2 Email Scraper	Public contact emails from G2
Hotfrog Email Scraper	Public contact emails from Hotfrog
Houzz Email Scraper	Public contact emails from Houzz
Infobel Email Scraper	Public contact emails from Infobel
Kompass Email Scraper	Public contact emails from Kompass
Lacartes Email Scraper	Public contact emails from Lacartes
Manta Email Scraper	Public contact emails from Manta
MapQuest Email Scraper	Public contact emails from MapQuest
N49 Email Scraper	Public contact emails from N49
Porch Email Scraper	Public contact emails from Porch
Scoot Email Scraper	Public contact emails from Scoot
Thumbtack Email Scraper	Public contact emails from Thumbtack
Touch Local Email Scraper	Public contact emails from Touch Local
TradeIndia Email Scraper	Public contact emails from TradeIndia
Trustpilot Email Scraper	Public contact emails from Trustpilot
Tupalo Email Scraper	Public contact emails from Tupalo
Yalwa Email Scraper	Public contact emails from Yalwa
Yellow Pages Email Scraper	Public contact emails from Yellow Pages
Angi Email and Phone Number Scraper	Emails and phone numbers from Angi
Bark Email and Phone Number Scraper	Emails and phone numbers from Bark
Better Business Bureau Email and Phone Number Scraper	Emails and phone numbers from Better Business Bureau
Bizapedia Email and Phone Number Scraper	Emails and phone numbers from Bizapedia
Brownbook Email and Phone Number Scraper	Emails and phone numbers from Brownbook

Leave a review

If the Thomasnet Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.