# TradeIndia Email Scraper (`email_scraper/tradeindia-email-scraper`) Actor

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

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

### TradeIndia Email Scraper

TradeIndia Email Scraper is an Apify Actor designed to extract publicly indexed email addresses associated with TradeIndia search results using targeted keywords and configurable email domains. It helps users turn search terms into a structured dataset containing relevant keywords, result titles, descriptions, URLs, and matching email addresses.

You can provide multiple keywords, optionally narrow searches by country, state, or city, select the email domains you want to find, and exclude unwanted terms from result descriptions. The Actor processes each keyword and email-domain combination separately and adds discovered results to the Apify dataset.

This makes the TradeIndia Email Scraper useful for B2B research, supplier discovery, manufacturer research, business contact research, market analysis, and structured lead-data collection based on publicly indexed information.

### What Is the TradeIndia Email Scraper?

The TradeIndia Email Scraper is a keyword-based contact extraction tool focused on publicly indexed TradeIndia pages.

Instead of manually searching through TradeIndia results and checking individual pages for contact information, you can configure search keywords and email-domain suffixes and let the Actor collect matching email addresses from available indexed result descriptions.

The workflow is straightforward:

- Provide one or more search keywords.
- Optionally provide a geographic location.
- Select one or more email-domain suffixes.
- Optionally define words or phrases to exclude.
- Set the maximum number of emails for each keyword and domain combination.
- Start the Actor and review the resulting dataset.

The returned records contain the search keyword, result title, description, URL, and extracted email address.

### Key Features

| Feature                     | Description                                                                         | User Benefit                                                      |
| --------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Keyword-based search        | Search TradeIndia using configurable keywords or queries.                           | Target specific business categories and audiences.                |
| Multiple keywords           | Supply several search terms in one run.                                             | Expand research coverage without separate runs.                   |
| Location filtering          | Add a country, state, or city to narrow searches.                                   | Focus research on a geographic market.                            |
| Custom email domains        | Search for domains such as `@gmail.com`, `@yahoo.com`, or other specified suffixes. | Target the types of addresses relevant to your workflow.          |
| Per-combination email limit | Set a maximum number of emails for each keyword + domain combination.               | Control the amount of data collected for each search combination. |
| Exclude words               | Skip result descriptions containing selected words or phrases.                      | Reduce unwanted results based on description content.             |
| Duplicate prevention        | Previously collected email addresses are not added again.                           | Keep the resulting contact dataset cleaner.                       |
| Structured dataset          | Results are stored with consistent fields.                                          | Make collected data easier to review and analyze.                 |
| Incremental results         | Discovered results are added to the dataset during processing.                      | Results can become available progressively during a run.          |

### What Data Can You Extract?

The TradeIndia Email Scraper returns five user-facing data fields for each collected email result:

- `keyword` — The keyword associated with the search that produced the result.
- `title` — The title of the indexed search result.
- `description` — The available result description containing the relevant publicly indexed information.
- `url` — The URL associated with the search result.
- `email` — The email address matching one of the configured domain suffixes.

These fields provide both the extracted contact information and contextual information about where the result was found.

The context fields are particularly useful when reviewing collected contacts because they allow you to understand the search term, source URL, and description associated with an email address.

### Why Use This Actor?

Manual business contact research can require repeated searches, result inspection, and copying information into a spreadsheet or database. The TradeIndia Email Scraper turns this repetitive search process into a configurable Apify workflow.

It is especially useful when your research requires multiple combinations of:

- Business keywords
- Locations
- Email-domain suffixes
- Exclusion terms
- Email collection targets

For example, a user researching manufacturers could search for `manufacturer`, `supplier`, `OEM manufacturer`, and `industrial supplier`, while also specifying relevant email domains and a target location.

Because the Actor returns structured dataset records, the collected information can be reviewed as a consistent table instead of manually assembled search notes.

### Benefits

The TradeIndia Email Scraper provides several practical benefits for structured contact research:

- **Automated data collection** — Reduce repetitive manual searching for publicly indexed contact information.
- **Targeted research** — Use specific business keywords instead of relying on a single broad query.
- **Geographic targeting** — Narrow searches with an optional location.
- **Domain targeting** — Choose which email-domain suffixes should be considered.
- **Flexible filtering** — Exclude descriptions containing unwanted words or phrases.
- **Structured results** — Receive consistent keyword, title, description, URL, and email fields.
- **Duplicate reduction** — The Actor avoids adding the same email address repeatedly during the run.
- **Scalable research setup** — Combine multiple keywords and domains according to your research requirements.

### How to Use the TradeIndia Email Scraper

A typical run can be configured in a few steps:

1. Enter one or more keywords in the **Keywords or Queries** field.
2. Add a country, state, or city in **Region / Location** if geographic targeting is required.
3. Enter the email-domain suffixes you want to search for.
4. Set **Max Emails** according to the amount of data you want for each keyword + domain combination.
5. Add optional **Exclude words** if certain descriptions should be skipped.
6. Start the Actor.
7. Review the resulting records in the Apify dataset.

For initial testing, use a small number of keywords and a modest email limit. Once the output matches your research requirements, you can expand the configuration.

### Input

The Actor requires the `keywords` field. All other fields are optional and have defaults defined by the Actor schema.

| Field           | Type             | Required | Default                        | Description                                                                               |
| --------------- | ---------------- | -------- | ------------------------------ | ----------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["manufacturer", "supplier"]` | Search keywords or queries used to find relevant TradeIndia 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 search for.                                                      |
| `maxEmails`     | Integer          | No       | `5`                            | Maximum emails targeted for each keyword + domain combination. Allowed range is 1–10,000. |
| `excludeWords`  | Array of strings | No       | `[]`                           | Words or phrases that cause matching result descriptions to be skipped.                   |

The `keywords` field accepts multiple search terms. Using several specific terms can provide broader coverage than relying on one generic term.

The `location` field can be left empty when geographic filtering is unnecessary.

For `customDomains`, use complete domain suffixes such as `@gmail.com` or `@yahoo.com`. You can specify multiple suffixes.

The `maxEmails` value applies independently to each keyword + domain combination. For example, three keywords and two domains with a limit of 20 create six keyword-domain combinations, each with a target of up to 20 matching emails, subject to available indexed results and other run limitations.

On free usage, the Actor applies a maximum of 100 emails when the requested limit is missing or exceeds that threshold. The Actor code does not apply that same restriction to paid usage.

### Input Example

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

### Output

The Actor produces structured dataset records containing the email address and contextual information from the associated indexed result.

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

Only email addresses that match the configured domain patterns are collected. If a result description contains an excluded word or phrase, that result is skipped.

The Actor also prevents duplicate email addresses from being added repeatedly during the collection process.

### Output Example

```json
{
  "keyword": "manufacturer",
  "title": "Industrial Equipment Manufacturer",
  "description": "Manufacturer and supplier of industrial equipment. Contact us at sales@example.com for product information.",
  "url": "https://www.tradeindia.com/example-business/",
  "email": "sales@example.com"
}
```

The values above are illustrative examples showing the output structure. Actual values depend on the publicly indexed search results available for your selected keywords, domains, and location.

### Use Cases

The TradeIndia Email Scraper can support several research and data-collection workflows:

- **B2B lead research** — Find publicly indexed business contact addresses associated with relevant TradeIndia results.
- **Supplier discovery** — Research suppliers using targeted product or business keywords.
- **Manufacturer research** — Identify contact opportunities around manufacturing-related searches.
- **Market research** — Build structured datasets around specific business categories or geographic markets.
- **Business intelligence** — Combine result context with extracted email addresses for further analysis.
- **Sales research** — Create a starting dataset for manually reviewed business outreach research.
- **Industry research** — Collect contact-related information across multiple business search terms.
- **Dataset creation** — Build structured TradeIndia contact datasets for downstream analysis.
- **Geographic research** — Narrow business contact searches to selected countries, states, or cities.

Collected contact information should be reviewed and used according to applicable laws, platform rules, privacy requirements, and your intended communication practices.

### Advantages

The Actor is designed around configurable search combinations rather than a single fixed search.

Key advantages include:

- Multiple keyword support.
- Optional geographic targeting.
- Configurable email-domain suffixes.
- Per-keyword and per-domain collection targets.
- Description-based exclusion filtering.
- Structured dataset output.
- Duplicate email prevention.
- Incremental dataset updates during processing.

These controls allow users to adapt the Actor to different B2B research requirements without changing the underlying Actor configuration.

### Limitations

The TradeIndia Email Scraper depends on publicly indexed search information, so results can vary according to what is available and indexed at the time of a run.

Important considerations include:

- Not every TradeIndia profile or business listing necessarily has an email address available in indexed information.
- A requested email target is not a guarantee that that number of addresses will be found.
- Narrow keywords may produce fewer relevant results.
- Narrow geographic filters can reduce the available result set.
- Restricting the search to a small number of email domains can reduce coverage.
- Exclusion terms can intentionally remove otherwise relevant results.
- Search-result availability can change over time.
- Free usage is subject to the Actor's 100-email maximum when the configured limit is missing or exceeds that threshold.
- Results may be below the requested target when sufficient matching indexed information is unavailable.

For wider research, consider using several closely related keywords and appropriate domain suffixes rather than relying on one search term.

### Pros and Cons

| Pros                                    | Cons                                                                                |
| --------------------------------------- | ----------------------------------------------------------------------------------- |
| Supports multiple keywords              | Results depend on publicly indexed information                                      |
| Optional location targeting             | Not every listing will expose a matching email                                      |
| Custom email-domain filtering           | Narrow configurations can produce fewer results                                     |
| Exclude-word filtering                  | Exclusion terms can remove potentially relevant snippets                            |
| Structured dataset fields               | Requested email targets are not guaranteed                                          |
| Duplicate email prevention              | Search availability can change between runs                                         |
| Per keyword + domain collection targets | Free usage has a 100-email maximum when the configured limit exceeds that threshold |

### Comparison With Alternative Approaches

| Capability             | TradeIndia Email Scraper       | Manual Search                           |
| ---------------------- | ------------------------------ | --------------------------------------- |
| Keyword-based research | Supported                      | Requires repeated manual searches       |
| Multiple keywords      | Supported                      | Usually handled separately              |
| Location filtering     | Supported                      | Requires manual query refinement        |
| Email-domain targeting | Supported                      | Requires manually constructing searches |
| Exclusion filtering    | Supported                      | Requires manual inspection              |
| Structured output      | Dataset fields for each result | Often requires manual formatting        |
| Duplicate prevention   | Supported during collection    | Requires manual checking                |
| Repetitive collection  | Automated through the Actor    | Primarily manual                        |

This comparison describes workflow differences rather than making claims about other tools or services.

### Best Practices

For better research workflows:

- Use several specific keywords instead of one very broad keyword.
- Combine related business terms such as product categories, roles, or business types.
- Start with a small test configuration before running larger searches.
- Use a location when geographic targeting is important.
- Leave the location blank when broader coverage is desired.
- Add relevant email domains when you need more than the default domain.
- Use exclusion words carefully because matching descriptions are skipped entirely.
- Choose a realistic `maxEmails` value for each keyword + domain combination.
- Review the resulting title, description, URL, and email together rather than evaluating an email address in isolation.
- Validate important contact information before using it in business workflows.
- For broad runs, allow sufficient run time for the configured searches to complete.

### Troubleshooting

**Invalid Input**

Check that `keywords` is an array of strings and that required fields are populated. Numeric `maxEmails` values must be between 1 and 10,000 according to the input schema.

**Empty Results**

Try broader or more specific related keywords, remove an unnecessarily narrow location, or add additional email-domain suffixes. Also check whether the selected terms are likely to appear in publicly indexed TradeIndia information.

**Fewer Results Than Requested**

The `maxEmails` setting is a target, not a guarantee. The Actor can only collect matching addresses available in the indexed result set. Broader keywords or additional domains may increase the available search coverage.

**Unexpectedly Missing Results**

Review your `excludeWords` configuration. A matching word or phrase in a result description causes that entire result to be skipped.

**Duplicate Emails**

The Actor avoids adding the same email address repeatedly during a run. Consequently, the number of unique output records can differ from the number of matching occurrences found across search results.

**Partial Results**

Partial results can occur when the available indexed information is exhausted, matching addresses are limited, or a run cannot continue through additional available results. Review the dataset and consider adjusting the search configuration for another run.

### Frequently Asked Questions

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

The TradeIndia Email Scraper searches for publicly indexed TradeIndia information using your configured keywords and email-domain suffixes, then returns matching email addresses with contextual result data.

**What input does the TradeIndia Email Scraper require?**

The required input is `keywords`, provided as an array of search terms. Location, domains, email limits, and exclusion words are optional.

**Can I use multiple keywords?**

Yes. The `keywords` field accepts multiple strings, allowing you to research several business categories or related search terms in one Actor run.

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

Yes. The optional `location` field accepts a country, state, or city and can be used to narrow the search.

**Which email domains can I search?**

You can configure `customDomains` with email-domain suffixes such as `@gmail.com`, `@yahoo.com`, `@outlook.com`, or other domain suffixes you want to target.

**How does `maxEmails` work?**

The configured maximum applies independently to each keyword + domain combination. A target limits collection for that combination; it does not guarantee that the requested number exists.

**What does `excludeWords` do?**

If an exclusion word or phrase appears in a result description, that result is skipped and no email is collected from it. Single words use whole-word, case-insensitive matching, while phrases use case-insensitive matching.

**Does the Actor return duplicate email addresses?**

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

**Why did the Actor return fewer emails than my limit?**

The requested limit is a collection target. Fewer results can occur when there are not enough matching publicly indexed results, when filters are restrictive, or when relevant email addresses are unavailable.

**Is the TradeIndia Email Scraper suitable for automation?**

Yes. It is an Apify Actor designed to automate a configurable keyword-based email research workflow and produce structured dataset records.

### NLP Keywords

- TradeIndia email scraper
- TradeIndia email extractor
- TradeIndia contact scraper
- TradeIndia business email extraction
- TradeIndia lead scraper
- TradeIndia contact data
- TradeIndia supplier emails
- TradeIndia manufacturer emails
- TradeIndia business contacts
- TradeIndia email finder
- TradeIndia lead generation
- TradeIndia B2B data
- TradeIndia supplier research
- TradeIndia manufacturer research
- TradeIndia contact extraction
- TradeIndia business data extraction
- TradeIndia keyword scraper
- TradeIndia email collection
- TradeIndia lead research
- TradeIndia structured contact data

### Related Keywords

- TradeIndia business email scraper
- TradeIndia supplier contact extractor
- TradeIndia manufacturer contact finder
- TradeIndia B2B lead extraction
- TradeIndia email address finder
- TradeIndia company contact scraper
- TradeIndia supplier lead generation
- TradeIndia business lead research
- TradeIndia contact information scraper
- TradeIndia email data extraction
- TradeIndia company email finder
- TradeIndia industrial supplier research
- TradeIndia manufacturer lead research
- TradeIndia business directory email scraper
- TradeIndia contact dataset
- TradeIndia prospect research
- TradeIndia keyword email extractor
- TradeIndia business intelligence data
- TradeIndia supplier email collection
- TradeIndia public contact research

### Final Overview

TradeIndia Email Scraper provides a structured way to research publicly indexed TradeIndia contact information using keywords, optional geographic targeting, configurable email domains, and exclusion terms.

Its output combines the extracted email address with the keyword, result title, description, and URL that provide context for the collected record. Multiple keyword and domain combinations can be configured in a single run, while duplicate email addresses are prevented from being repeatedly added.

For the most useful results, start with focused keywords, test a small configuration, use geographic filtering when appropriate, and expand domains or related search terms when broader coverage is required. Always review and validate collected information before using it in downstream business workflows.

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

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

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

```

## MCP server setup

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