# ExportHub Email Scraper (`email_scraper/exporthub-email-scraper`) Actor

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

- **URL**: https://apify.com/email\_scraper/exporthub-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

### ExportHub Email Scraper

ExportHub Email Scraper extracts publicly indexed email addresses associated with ExportHub pages using targeted search keywords and configurable email-domain filters. It is designed for users who need structured contact data for B2B research, supplier discovery, exporter research, buyer research, and business intelligence.

Provide one or more keywords, optionally narrow the search by country, state, or city, select the email domains you want to collect, and optionally exclude profiles whose descriptions contain specific words or phrases. The Actor returns structured results containing the search keyword, profile or result title, description, URL, and extracted email address.

The Actor supports multiple keyword and domain combinations, allowing users to build broader or more targeted ExportHub contact datasets from publicly indexed information.

### What Is an ExportHub Email Scraper?

An ExportHub Email Scraper is a data collection tool focused on finding publicly indexed email addresses associated with ExportHub content.

Instead of manually searching ExportHub-related pages and copying contact information, you can provide search terms and configuration options and receive structured records in an Apify dataset.

The workflow is straightforward:

- **Input:** Keywords, optional location, email-domain suffixes, an email target, and optional exclusion terms.
- **Search:** The Actor searches for relevant ExportHub results matching the configured criteria.
- **Extraction:** Matching email addresses are identified from available result descriptions.
- **Filtering:** Exclusion terms can remove unwanted descriptions before email extraction.
- **Output:** Results are added to the dataset with the keyword, title, description, URL, and email.

Because the Actor relies on publicly indexed information, the number of results depends on what is available and discoverable for the selected search criteria.

### Key Features

| Feature                      | Description                                                                 | User Benefit                                               |
| ---------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Targeted keyword search      | Search ExportHub-related content using your own keywords or queries.        | Focus collection on relevant business categories or roles. |
| Multiple keywords            | Submit a list of search terms in one run.                                   | Cover several target segments without separate runs.       |
| Location filtering           | Optionally provide a country, state, or city.                               | Narrow research to a geographic area.                      |
| Custom email domains         | Specify domains such as `@gmail.com`, `@yahoo.com`, or other suffixes.      | Focus results on the types of email addresses you need.    |
| Per-combination email target | Set a maximum target for each keyword + domain combination.                 | Control collection depth across different searches.        |
| Exclusion filtering          | Skip descriptions containing configured words or phrases.                   | Reduce unwanted results based on your criteria.            |
| Duplicate prevention         | Previously collected email addresses are not returned again during the run. | Keep the resulting contact dataset cleaner.                |
| Structured dataset output    | Results contain consistent fields for each extracted email.                 | Make collected information easier to review and analyze.   |
| Incremental results          | Matching records are added to the Apify dataset during processing.          | Results become available as collection progresses.         |

### What Data Can You Extract?

The ExportHub Email Scraper returns five user-facing fields for each collected contact record.

| Field         | Description                                                                    |
| ------------- | ------------------------------------------------------------------------------ |
| `keyword`     | The keyword associated with the search that produced the result.               |
| `title`       | The title of the indexed ExportHub result.                                     |
| `description` | The available result description containing the extracted contact information. |
| `url`         | The URL associated with the indexed result.                                    |
| `email`       | The email address matching one of the configured domain suffixes.              |

The dataset is therefore useful when you need both the extracted email and the surrounding context that helps identify where the contact came from.

### Why Use This Actor?

Manual contact research can involve repeating similar searches, checking individual results, identifying relevant email addresses, and organizing the information into a consistent structure.

The ExportHub Email Scraper turns that workflow into a configurable data-collection task.

Useful capabilities include:

- Searching with multiple targeted business keywords.
- Applying an optional geographic filter.
- Selecting specific email-domain suffixes.
- Setting a collection target for each keyword and domain combination.
- Excluding descriptions that contain unwanted terms.
- Receiving structured records instead of manually copied information.
- Building datasets that can be reviewed or analyzed within Apify.

The Actor is particularly useful when your research involves multiple business categories, locations, or email-domain requirements.

### Benefits

The main practical benefits are focused on automation and structured research.

- **Less repetitive searching:** Configure keywords once instead of manually repeating similar searches.
- **Flexible targeting:** Combine business terms with optional geographic criteria.
- **Domain-specific collection:** Choose which email suffixes should be considered.
- **Structured contact records:** Keep email addresses connected to their keyword, title, description, and URL.
- **Multiple search combinations:** Work across several keyword and domain combinations within one run.
- **Filtering control:** Exclude descriptions that contain words or phrases you do not want.
- **Dataset creation:** Build organized ExportHub contact datasets for further analysis.
- **Research flexibility:** Adjust keywords, domains, locations, and exclusions according to the project.

### How to Use the ExportHub Email Scraper

A typical workflow takes only a few configuration steps:

1. Enter one or more keywords or search queries in the `keywords` field.
2. Add a country, state, or city in `location` if geographic targeting is required.
3. Configure the email-domain suffixes in `customDomains`.
4. Set `maxEmails` according to the desired collection depth.
5. Add unwanted words or phrases to `excludeWords` when filtering is needed.
6. Start the Actor.
7. Review the structured results in the Apify dataset.

For broader research, use several specific keywords instead of relying on one very broad term. For example, rather than only searching for `exporter`, you might use terms such as `textile exporter`, `food exporter`, `garment supplier`, or another category relevant to your research.

### Input

The Actor requires the `keywords` field. All other fields are optional and provide additional control over the search.

| Field           | Type             | Required | Default                    | Description                                                                           |
| --------------- | ---------------- | -------- | -------------------------- | ------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["exporter", "supplier"]` | Keywords or search queries used to find relevant ExportHub results.                   |
| `location`      | String           | No       | `""`                       | Optional country, state, or city used to narrow the search.                           |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`           | Email-domain suffixes to include when extracting addresses.                           |
| `maxEmails`     | Integer          | No       | `5`                        | Target number of emails for each keyword + domain combination. Valid range: 1–10,000. |
| `excludeWords`  | Array of strings | No       | `[]`                       | Words or phrases that cause matching result descriptions to be skipped.               |

#### Keywords

`keywords` accepts multiple search terms. Specific terms can help create more focused datasets.

Example:

```json
{
  "keywords": [
    "textile exporter",
    "garment supplier",
    "food exporter"
  ]
}
```

#### Location

`location` is optional. Leave it empty when geographic filtering is not required.

Example:

```json
{
  "location": "Bangladesh"
}
```

#### Custom Email Domains

`customDomains` accepts one or more email suffixes.

Example:

```json
{
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ]
}
```

#### Maximum Emails

`maxEmails` accepts an integer from `1` through `10000`. The configured target applies independently to each keyword + domain combination.

For example, with three keywords, two domains, and a target of `20`, the Actor works through six keyword-domain combinations, with a target of up to 20 addresses for each combination. Actual results can be lower when matching publicly indexed information is limited.

#### Exclude Words

`excludeWords` can contain individual words or phrases.

Single words are matched case-insensitively as whole words. Phrases are matched case-insensitively within the description. If a description matches an exclusion term, that result is skipped and an email is not extracted from it.

### Input Example

```json
{
  "keywords": [
    "textile exporter",
    "garment supplier",
    "food exporter"
  ],
  "location": "Bangladesh",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### Output

The Actor stores extracted contacts in an Apify dataset. Each result contains the search context, indexed result information, and matching email address.

| Field         | Description                                                    |
| ------------- | -------------------------------------------------------------- |
| `keyword`     | Search keyword that produced the result.                       |
| `title`       | Title associated with the indexed result.                      |
| `description` | Description or snippet associated with the result.             |
| `url`         | URL of the indexed result.                                     |
| `email`       | Extracted email address matching the configured domain suffix. |

The Actor adds results incrementally, so the dataset can contain records as they are successfully collected.

### Output Example

```json
{
  "keyword": "textile exporter",
  "title": "Example Textile Exporter",
  "description": "Example Textile Exporter supplies textile products and can be contacted at contact@example.com.",
  "url": "https://www.exporthub.com/example-textile-exporter",
  "email": "contact@example.com"
}
```

The example uses fictional information to demonstrate the output structure.

### Use Cases

The ExportHub Email Scraper can support several research and data-collection workflows.

- **B2B lead research:** Identify publicly indexed business contacts associated with relevant ExportHub searches.
- **Supplier discovery:** Research suppliers by product category, business role, or location.
- **Exporter research:** Build contact datasets around specific export-related industries.
- **Buyer research:** Search for business-related terms that identify potential buyers or commercial contacts.
- **Market research:** Collect structured contact information for selected market segments.
- **Business intelligence:** Combine contact records with keyword and location context for analysis.
- **Industry research:** Create datasets covering multiple product or business categories.
- **Contact dataset creation:** Organize extracted emails together with source URLs and descriptions.
- **Geographic research:** Compare contact discovery across different countries, states, or cities.
- **Targeted outreach research:** Prepare publicly indexed contact information for further validation and appropriate business use.

### Competitive Advantages

The Actor provides several practical configuration options without requiring users to manually organize search results.

Its strengths include:

- Multiple keyword support.
- Multiple email-domain support.
- Optional geographic targeting.
- Configurable email collection targets.
- Description-based exclusion filtering.
- Structured dataset fields.
- Duplicate email prevention.
- Incremental dataset updates.

These capabilities make the Actor adaptable to both broad research projects and more focused ExportHub contact searches.

### Advantages

| Advantage                  | Why It Matters                                                                      |
| -------------------------- | ----------------------------------------------------------------------------------- |
| Flexible keyword targeting | Different business categories can be researched in one run.                         |
| Geographic filtering       | Searches can be narrowed to a selected location.                                    |
| Domain selection           | Users can focus collection on specific email suffixes.                              |
| Configurable targets       | Collection depth can be adjusted for individual search combinations.                |
| Contextual output          | Email addresses are returned with title, description, URL, and keyword information. |
| Exclusion filtering        | Unwanted descriptions can be removed based on user-defined terms.                   |
| Structured dataset         | Results are easier to review and process than manually collected information.       |

### Limitations

The Actor works with publicly indexed information, so results depend on the information available for the selected keywords, domains, and locations.

Important considerations include:

- A requested `maxEmails` value is a target, not a guarantee that that many matching addresses exist.
- Narrow keywords or geographic filters can produce fewer results.
- Some relevant ExportHub pages may not contain an email address in the available indexed description.
- Results can vary according to the publicly indexed information available at the time of a run.
- Duplicate email addresses are not returned repeatedly, so the number of unique records can be lower than the combined per-combination targets.
- Free usage is subject to a code-level maximum of 100 collected emails. Paid usage does not have this code-level ceiling.
- Empty or partial results can occur when matching indexed information is limited.

### Pros and Cons

| Pros                                | Cons                                                          |
| ----------------------------------- | ------------------------------------------------------------- |
| Supports multiple search keywords   | Results depend on publicly indexed information                |
| Supports multiple email domains     | Not every relevant result contains an extractable email       |
| Optional location targeting         | Narrow searches may return fewer contacts                     |
| Configurable per-combination target | A target does not guarantee that many results                 |
| Exclusion filtering                 | Overly broad exclusions can remove potentially useful results |
| Structured dataset output           | Result availability can vary between searches                 |
| Duplicate email prevention          | Unique results may be fewer than requested                    |

### Comparison With Alternative Approaches

| Capability             | ExportHub Email Scraper | Manual / Typical Alternative              |
| ---------------------- | ----------------------- | ----------------------------------------- |
| Keyword-based research | Supported               | Often requires repeated manual searches   |
| Multiple keywords      | Supported               | Usually managed manually                  |
| Location filtering     | Supported               | Depends on the research workflow          |
| Email-domain filtering | Supported               | Often requires manual checking            |
| Exclusion terms        | Supported               | Usually handled manually                  |
| Structured output      | Supported               | May require manual formatting             |
| Duplicate prevention   | Supported               | Requires manual or separate data cleaning |
| Apify dataset          | Supported               | May require separate organization         |

This comparison describes workflow differences rather than guaranteeing a particular result volume or data quality.

### Best Practices

For more focused research, consider the following practices:

- Start with a small test using one or two specific keywords.
- Use specific business terms rather than relying only on broad categories.
- Add a location when geographic targeting is important.
- Use several relevant email domains when your research permits it.
- Keep `maxEmails` reasonable during initial testing.
- Add exclusion terms only when they clearly represent unwanted results.
- Review a small dataset before expanding the search.
- Broaden keywords or remove a restrictive location when results are sparse.
- Validate important contact information before using it in downstream workflows.
- Treat extracted information as research data and use it in accordance with applicable laws, policies, and the source's terms.

### Troubleshooting

**Invalid Input:** Verify that `keywords` is an array of strings and that integer values such as `maxEmails` are within the documented range.

**Empty Results:** Try more specific or alternative keywords, remove an overly restrictive location, or include additional email-domain suffixes.

**Fewer Emails Than Requested:** `maxEmails` is a target rather than a guarantee. The available indexed results may not contain enough matching addresses.

**Too Many Excluded Results:** Review `excludeWords`. A matching exclusion term causes the complete result description to be skipped.

**Unexpectedly Small Dataset:** Remember that duplicate email addresses are not collected repeatedly. Multiple searches can therefore produce fewer unique contacts than their individual targets suggest.

**Partial Results:** Publicly indexed information can vary, and some searches may not provide enough matching contact information to reach the configured target.

**Run Takes Longer Than Expected:** Larger keyword lists, more email domains, higher targets, and broader searches can require more processing. For wide runs, consider increasing the available run timeout when necessary.

### Frequently Asked Questions

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

It searches for publicly indexed ExportHub results and extracts matching email addresses from available result descriptions according to your configured keywords and email-domain filters.

**What inputs does the ExportHub Email Scraper support?**

The Actor accepts required `keywords` plus optional `location`, `customDomains`, `maxEmails`, and `excludeWords` settings.

**Can I use multiple keywords?**

Yes. The `keywords` field accepts an array of search terms, allowing you to cover multiple business categories or search intents in one run.

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

Yes. Enter a country, state, or city in `location` to narrow the search geographically.

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

Yes. Use `customDomains` to specify email suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

**How does `maxEmails` work?**

The value sets the target for each keyword + domain combination. It ranges from 1 to 10,000 in the input schema. The target does not guarantee that the requested number of matching public emails exists.

**What does `excludeWords` do?**

It prevents a result from being collected when its description contains one of the configured exclusion words or phrases.

**Does the Actor return duplicate emails?**

The Actor tracks collected email addresses and avoids returning the same email address repeatedly during the run.

**What output does the ExportHub Email Scraper produce?**

Each dataset record contains `keyword`, `title`, `description`, `url`, and `email`.

**Why did I receive fewer results than my target?**

The target can exceed the number of matching publicly indexed results. Narrow keywords, locations, selected domains, exclusion terms, and duplicate prevention can also reduce the number of unique contacts.

**Can I use this Actor for automated research workflows?**

Yes. The Actor is designed to run as an Apify data-collection task and produces structured dataset records suitable for subsequent review and analysis.

### NLP Keywords

- ExportHub email scraper
- ExportHub email extraction
- ExportHub contact data
- ExportHub business contacts
- ExportHub leads
- ExportHub supplier contacts
- ExportHub exporter contacts
- ExportHub buyer research
- ExportHub email finder
- ExportHub contact scraper
- ExportHub lead generation
- ExportHub data extraction
- ExportHub business research
- ExportHub supplier research
- ExportHub contact discovery
- ExportHub email collection
- ExportHub structured data
- ExportHub public emails
- ExportHub B2B contacts
- ExportHub contact dataset

### Related Keywords

- ExportHub email scraper tool
- scrape ExportHub emails
- ExportHub contact extractor
- ExportHub business email finder
- ExportHub supplier email scraper
- ExportHub exporter email extraction
- ExportHub B2B lead scraper
- ExportHub contact data scraper
- ExportHub email lead generation
- extract emails from ExportHub
- ExportHub supplier lead research
- ExportHub business lead extraction
- ExportHub email data collection
- ExportHub public contact scraper
- ExportHub email address finder
- ExportHub company contact research
- ExportHub supplier contact finder
- ExportHub exporter contact finder
- ExportHub business intelligence data
- ExportHub lead dataset

### Final Overview

ExportHub Email Scraper provides a configurable way to collect publicly indexed email addresses associated with ExportHub results and organize them into structured Apify dataset records.

Users can control the search with multiple keywords, optional geographic targeting, custom email domains, per-combination email targets, and exclusion terms. Each collected record preserves useful context through the keyword, title, description, URL, and email fields.

For the most useful results, begin with specific keywords, test a small configuration, review the returned dataset, and then expand the search with additional relevant terms or domains. Keep in mind that available results depend on publicly indexed information and that configured email targets are not guarantees.

*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": [
    "exporter",
    "supplier"
  ],
  "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": [
        "exporter",
        "supplier"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/exporthub-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": [
        "exporter",
        "supplier",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/exporthub-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": [
    "exporter",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/exporthub-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/exporthub-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/QQqDRtvzVSzPj80mz/builds/fR9ethesKdUEYPrbb/openapi.json