# Tradewheel Email Scraper (`email_scraper/tradewheel-email-scraper`) Actor

Tradewheel Email Scraper extracts publicly indexed emails from Tradewheel using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured contact datasets for supplier research, manufacturer discovery, B2B lead research, and business intelligence.

- **URL**: https://apify.com/email\_scraper/tradewheel-email-scraper.md
- **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Tradewheel Email Scraper

Tradewheel Email Scraper extracts publicly indexed email addresses associated with Tradewheel pages based on the keywords and email domains you provide. You can target suppliers, manufacturers, exporters, distributors, product-related businesses, or other relevant search terms and optionally narrow the search by country, state, or city.

The Actor returns structured contact records containing the search keyword, page title, description, source URL, and extracted email address. Multiple keywords and email domains can be configured in one run, making it suitable for organized B2B research, supplier discovery, business intelligence, and contact dataset creation.

The workflow is simple: provide search terms, optionally configure a location and email domains, set the desired email limit, and review the resulting Tradewheel contact dataset.

### What Is the Tradewheel Email Scraper?

Tradewheel Email Scraper is an email extraction and data collection Actor designed for Tradewheel-related search results.

Instead of manually searching for Tradewheel pages and checking descriptions for publicly indexed contact addresses, you can define the search criteria and let the Actor collect matching email addresses into a structured Apify dataset.

The Actor supports multiple keyword queries, optional geographic filtering, configurable email-domain suffixes, maximum email targets, and exclusion words or phrases.

It is particularly useful when your research requires business contacts related to specific industries, products, supplier types, manufacturers, or geographic markets.

### 🔍 Key Features

| Feature                       | Description                                                            | User Benefit                                          |
| ----------------------------- | ---------------------------------------------------------------------- | ----------------------------------------------------- |
| Keyword-based search          | Search using one or multiple keywords or queries                       | Target specific business categories and search intent |
| Tradewheel-focused collection | Searches for publicly indexed Tradewheel results                       | Focus research on relevant Tradewheel pages           |
| Location filtering            | Optionally specify a country, state, or city                           | Narrow research geographically                        |
| Custom email domains          | Specify domains such as `@gmail.com`, `@yahoo.com`, or other suffixes  | Focus collection on desired email types               |
| Per-combination email target  | Set a maximum number of emails for each keyword and domain combination | Control collection depth                              |
| Exclusion filtering           | Skip descriptions containing configured words or phrases               | Reduce unwanted results                               |
| Duplicate prevention          | Previously collected email addresses are not added again               | Keep the dataset cleaner                              |
| Structured dataset output     | Results are pushed as structured records                               | Simplify review and downstream analysis               |
| Multiple keyword support      | Process a list of search terms in one run                              | Build broader research datasets                       |

### 📊 What Data Can You Extract?

Each collected result contains five user-facing data fields.

- **Keyword** — The keyword associated with the search that produced the result.
- **Title** — The title of the relevant indexed result.
- **Description** — The available result description containing the publicly indexed information used for email extraction.
- **URL** — The source URL associated with the search result.
- **Email** — The email address matching the configured email-domain suffix.

The output is designed around contact research rather than a large profile schema. It provides the contextual information needed to understand where an extracted email came from.

Because email extraction depends on publicly indexed information, the available records can vary according to the search terms, location, email domains, and information exposed in indexed descriptions.

### 💡 Why Use This Actor?

Manual contact research can require repeatedly searching for relevant businesses, opening pages, checking available descriptions, identifying contact addresses, and recording the results.

Tradewheel Email Scraper turns that repetitive search workflow into a configurable data-collection task.

It can be useful when you need to:

- Research suppliers or manufacturers related to particular keywords.
- Collect publicly indexed business email addresses for research.
- Build structured Tradewheel contact datasets.
- Compare results across multiple industries or search terms.
- Narrow contact research to a geographic region.
- Focus on specific email-domain suffixes.
- Exclude results containing unwanted words or phrases.
- Process several keyword and domain combinations in a single run.

The Actor does not guarantee that every Tradewheel profile contains an email address. Results depend on what is publicly indexed and available for the selected search criteria.

### ✅ Benefits

Tradewheel Email Scraper provides several practical benefits for structured business research.

- **Automation:** Reduce repetitive manual searching and copying of contact information.
- **Structured results:** Receive keyword, title, description, URL, and email in consistent dataset records.
- **Flexible targeting:** Combine multiple keywords with multiple email-domain suffixes.
- **Geographic research:** Use a location value when research needs to focus on a specific market.
- **Filtering:** Exclude descriptions containing unwanted words or phrases.
- **Dataset creation:** Build organized contact data for later review and analysis.
- **Configurable collection depth:** Control the target number of addresses for each keyword and domain combination.
- **Duplicate reduction:** The same email address is not returned repeatedly during collection.

### ⚙️ How to Use the Tradewheel Email Scraper

The basic workflow is straightforward:

1. Enter one or more keywords in the **Keywords or Queries** field.
2. Add a country, state, or city if geographic filtering is required.
3. Configure the email-domain suffixes you want to search for.
4. Set the maximum email target for each keyword and domain combination.
5. Add exclusion words or phrases if certain descriptions should be skipped.
6. Start the Actor.
7. Review the structured results in the Apify dataset.

For a first run, use a small number of keywords and a modest email target. After reviewing the results, refine the keywords, domains, location, or exclusions according to your research requirements.

### 📥 Input

The Actor requires the `keywords` field. The other fields are optional and have documented defaults.

| Field           | Type             | Required | Default                        | Description                                                                           |
| --------------- | ---------------- | -------- | ------------------------------ | ------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["supplier", "manufacturer"]` | Search keywords or queries to use for Tradewheel research                             |
| `location`      | String           | No       | `""`                           | Optional country, state, or city used to narrow the search                            |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`               | Email-domain suffixes to search for                                                   |
| `maxEmails`     | Integer          | No       | `5`                            | Maximum email target for each keyword + domain combination; allowed range is 1–10,000 |
| `excludeWords`  | Array of strings | No       | `[]`                           | Words or phrases that cause a result description to be skipped                        |

#### Keyword Input

Use specific terms when possible. For example, instead of relying only on a broad term such as `Fitness`, you can use more targeted searches such as:

- `Fitness Coach`
- `Fitness Trainer`
- `Fitness Equipment Supplier`
- `Online Fitness Coach`

More specific queries can help align the collected contacts with a particular research objective.

#### Location Input

The `location` field is optional.

You can enter a country, state, or city manually. Leave it empty when you do not want a geographic filter.

Examples include:

- `United States`
- `Germany`
- `Dubai`
- `New York`

#### Custom Email Domains

The `customDomains` field accepts a list of email-domain suffixes.

Examples:

- `@gmail.com`
- `@yahoo.com`
- `@outlook.com`
- A company-domain suffix such as `@example.com`

The Actor searches according to the domain suffixes you configure.

#### Maximum Emails

`maxEmails` accepts an integer from `1` to `10000`.

The limit applies independently to each keyword + domain combination. For example, with three keywords, two domains, and a limit of `20`, the Actor processes six keyword/domain combinations, with a target of up to 20 addresses for each combination.

The configured target is not a guarantee. If fewer publicly indexed matching email addresses are available, the resulting dataset can contain fewer records.

#### Exclude Words

Use `excludeWords` to skip result descriptions containing unwanted terms.

Single-word entries are matched as whole words, while phrases are matched as phrases. Matching is case-insensitive.

For example:

```json
{
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

If a result description matches an exclusion term, that result is skipped for email extraction.

### 🧾 Input Example

```json
{
  "keywords": [
    "supplier",
    "manufacturer",
    "industrial equipment supplier"
  ],
  "location": "United States",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### 📤 Output

Tradewheel Email Scraper writes collected contacts to the Apify dataset.

The user-facing output contains the following fields:

| Field         | Description                                                   |
| ------------- | ------------------------------------------------------------- |
| `keyword`     | Search keyword associated with the collected result           |
| `title`       | Title of the indexed result                                   |
| `description` | Description associated with the result                        |
| `url`         | Source URL for the result                                     |
| `email`       | Extracted email address matching the configured domain suffix |

The dataset view is organized as a table so that the main contact information can be reviewed easily.

Results are added during the run rather than requiring the entire collection process to finish before records become available.

### 🧾 Output Example

```json
{
  "keyword": "supplier",
  "title": "Industrial Equipment Supplier",
  "description": "Supplier of industrial equipment and machinery. Contact: sales@example.com",
  "url": "https://www.tradewheel.com/example-profile",
  "email": "sales@example.com"
}
```

The values above are illustrative examples showing the output structure. Actual values depend on the search results available for your selected inputs.

### 🎯 Use Cases

Tradewheel Email Scraper can support several types of research and data-collection workflows.

- **Supplier research:** Find publicly indexed email addresses related to supplier-focused searches.
- **Manufacturer discovery:** Research manufacturers associated with specific products or industries.
- **B2B lead research:** Build contact datasets around defined business keywords.
- **Market research:** Collect contact information related to selected commercial markets.
- **Geographic research:** Narrow searches to particular countries, states, or cities.
- **Business intelligence:** Organize publicly indexed business contact information for analysis.
- **Contact dataset creation:** Build structured datasets from multiple keyword and domain combinations.
- **Industry research:** Compare contact availability across different business categories.
- **Targeted outreach research:** Prepare publicly indexed contact information for further validation and compliant business workflows.

Users should independently validate collected information before relying on it for important business decisions or communications.

### 🚀 Competitive Advantages

The Actor provides several practical configuration options in one workflow.

- Multiple keywords can be processed in a single run.
- Multiple email-domain suffixes can be configured.
- Geographic filtering is optional.
- Exclusion words can remove unwanted descriptions from collection.
- Email targets can be controlled for each keyword/domain combination.
- Results include contextual fields instead of only an email address.
- Duplicate email addresses are avoided during collection.
- Results are stored in a structured Apify dataset.

These capabilities make the Actor adaptable to different Tradewheel research objectives without requiring users to manually organize every search result.

### 👍 Advantages

| Advantage             | Practical Value                               |
| --------------------- | --------------------------------------------- |
| Multiple search terms | Supports broader or more targeted research    |
| Domain filtering      | Focuses extraction on selected email suffixes |
| Location option       | Supports geographic targeting                 |
| Exclusion filtering   | Helps remove unwanted matching descriptions   |
| Structured output     | Makes collected information easier to review  |
| Configurable target   | Lets users control collection depth           |
| Duplicate prevention  | Reduces repeated email records                |

### ⚠️ Limitations

- The Actor depends on publicly indexed information, so not every Tradewheel page will produce an email address.
- A requested `maxEmails` value is a target rather than a guarantee of available results.
- Narrow keywords or restrictive locations can produce fewer results.
- Restricting the search to a small number of email domains can reduce the number of matching addresses.
- Exclusion terms can intentionally remove otherwise relevant results if they appear in a description.
- Search availability can vary, so two different search configurations may produce different datasets.
- On the free tier, the Actor applies a maximum collection limit of 100 emails when the configured limit is missing or greater than 100. Paid usage does not have this code-level free-tier restriction.

The Actor should therefore be treated as a tool for automated research and collection rather than a guarantee of complete Tradewheel contact coverage.

### ⚖️ Pros and Cons

| Pros                             | Cons                                                              |
| -------------------------------- | ----------------------------------------------------------------- |
| Multiple keywords supported      | Results depend on publicly indexed information                    |
| Multiple email domains supported | Narrow searches may return fewer contacts                         |
| Optional location filtering      | Requested targets are not guaranteed                              |
| Exclusion words and phrases      | Exclusions may remove relevant descriptions                       |
| Structured contact records       | Available data can vary by result                                 |
| Duplicate email prevention       | Free-tier collection is limited to 100 emails in applicable cases |

### 🔄 Comparison With Alternative Approaches

| Capability                     | Tradewheel Email Scraper | Manual / Typical Alternative     |
| ------------------------------ | ------------------------ | -------------------------------- |
| Keyword-based research         | Supported                | Usually performed manually       |
| Multiple keyword processing    | Supported                | Requires repeated searches       |
| Email-domain filtering         | Supported                | Requires manual filtering        |
| Location filtering             | Supported                | Depends on the research process  |
| Exclusion filtering            | Supported                | Often requires manual review     |
| Structured dataset             | Supported                | May require manual formatting    |
| Duplicate prevention           | Supported                | Often requires separate checking |
| Configurable collection target | Supported                | Usually managed manually         |

This comparison describes workflow differences rather than claiming that one approach is universally better.

### 💡 Best Practices

For better-targeted research, consider the following practices:

- Start with a small test run before launching a broad collection.
- Use specific business terms instead of relying only on very broad keywords.
- Combine related search terms when researching several business categories.
- Use a location only when geographic targeting is important.
- Add multiple relevant email domains when broader email coverage is needed.
- Keep `maxEmails` reasonable for initial testing.
- Use exclusion terms carefully so relevant descriptions are not removed.
- Review the resulting dataset before using contacts in downstream workflows.
- Validate important email addresses independently when accuracy is critical.
- If results are sparse, broaden the keywords or location and consider adding additional email domains.

### 🛠️ Troubleshooting

**Invalid or unexpected input:** Check that `keywords`, `customDomains`, and `excludeWords` are arrays of strings. `maxEmails` must be an integer between 1 and 10,000.

**Empty results:** Try broader keywords, remove an overly restrictive location, or add additional email-domain suffixes.

**Fewer emails than requested:** The configured limit represents a target. There may simply be fewer publicly indexed matching addresses for the selected keyword, domain, and location combination.

**Too many irrelevant results:** Use more specific keywords or add appropriate exclusion words and phrases.

**Missing email addresses:** An indexed result may not expose an email matching your selected domain suffix. Try additional domains if appropriate.

**Partial results:** Search availability and indexed information can vary. Review the collected records and consider running a broader configuration when more coverage is needed.

**Large runs take longer:** Multiple keywords, domains, and higher collection targets can require more search activity. The Actor input documentation recommends increasing the run timeout when a wide run needs additional time.

### ❓ Frequently Asked Questions

**What does the Tradewheel Email Scraper do?**

It collects publicly indexed email addresses associated with Tradewheel search results using the keywords, locations, and email-domain suffixes configured in the Actor.

**What data does Tradewheel Email Scraper return?**

Each result contains `keyword`, `title`, `description`, `url`, and `email`.

**Can I use multiple keywords?**

Yes. The `keywords` input is an array, allowing multiple search terms or queries in one run.

**Can I search for a specific country or city?**

Yes. Use the optional `location` field to narrow the search by country, state, or city. Leave it empty to search without a geographic filter.

**Can I choose which email domains are searched?**

Yes. The `customDomains` field accepts multiple email-domain suffixes such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

**How does `maxEmails` work?**

The target applies independently to each keyword + domain combination. For example, three keywords and two domains create six combinations, each with its own configured target.

**Does the Actor guarantee the requested number of emails?**

No. The configured number is a collection target. Actual results depend on the publicly indexed matching information available for the selected search criteria.

**Can I exclude unwanted results?**

Yes. Add words or phrases to `excludeWords`. Matching descriptions are skipped before email extraction.

**Does the Actor remove duplicate emails?**

Yes. An email address already collected during the run is not added again.

**Is the Actor suitable for business research?**

Yes. Its structured keyword, description, URL, and email output can support supplier research, manufacturer discovery, B2B contact research, and business intelligence workflows.

**What should I do if I receive too few results?**

Try more specific but broader sets of related keywords, expand or remove the location filter, and add relevant email domains. A wider configuration can provide more opportunities for matching publicly indexed contacts.

### 🔑 NLP Keywords

- Tradewheel email scraper
- Tradewheel email extractor
- Tradewheel contact scraper
- Tradewheel business emails
- Tradewheel contact data
- Tradewheel supplier emails
- Tradewheel manufacturer emails
- Tradewheel B2B leads
- Tradewheel lead generation
- Tradewheel business contacts
- Tradewheel email collection
- Tradewheel data extraction
- Tradewheel contact extraction
- Tradewheel supplier research
- Tradewheel manufacturer research
- Tradewheel business research
- Tradewheel lead research
- Tradewheel email finder
- Tradewheel contact dataset
- Tradewheel structured data

### Related Keywords

- Tradewheel email scraper online
- Tradewheel business email extractor
- extract emails from Tradewheel
- Tradewheel supplier contact finder
- Tradewheel manufacturer contact scraper
- Tradewheel B2B email extraction
- Tradewheel lead scraper
- Tradewheel contact finder
- Tradewheel email data extraction
- Tradewheel supplier lead generation
- Tradewheel manufacturer lead generation
- Tradewheel business contact extraction
- Tradewheel email collection tool
- Tradewheel public email scraper
- Tradewheel company email finder
- Tradewheel supplier email finder
- Tradewheel business research scraper
- Tradewheel contact dataset builder
- Tradewheel keyword email scraper
- Tradewheel B2B contact research

### 📌 Final Overview

Tradewheel Email Scraper provides a configurable way to collect publicly indexed Tradewheel email addresses using keyword-driven research.

Users can combine multiple search terms with optional geographic targeting, custom email-domain suffixes, collection targets, and exclusion words. The resulting dataset contains the keyword, title, description, source URL, and extracted email, giving each contact useful search context.

For the most useful results, begin with focused keywords, test a small configuration, review the returned dataset, and then broaden the search with additional relevant terms or domains when necessary.

*Contact me:* <Alphascraper69@gmail.com>

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see.

## Actor input object example

```json
{
  "keywords": [
    "supplier",
    "manufacturer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "maxEmails": 5,
  "excludeWords": []
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "supplier",
        "manufacturer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/tradewheel-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "supplier",
        "manufacturer",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/tradewheel-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "supplier",
    "manufacturer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/tradewheel-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/tradewheel-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1wrqiHxRlpSBZT2xg/builds/0BLorSaPClWNsujhq/openapi.json