# Moglix Email Scraper (`email_scraper/moglix-email-scraper`) Actor

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

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

### Moglix Email Scraper

Moglix Email Scraper is an Apify Actor designed to find publicly indexed email addresses associated with Moglix pages and search results using targeted keywords. It helps turn keyword-based searches into a structured dataset containing email addresses, result titles, descriptions, source URLs, and the keyword used to find each result.

You can provide multiple search keywords, optionally narrow searches by country, state, or city, choose specific email domains, and exclude descriptions containing unwanted words or phrases. The Actor processes each keyword and email-domain combination independently, helping you organize targeted searches for supplier discovery, manufacturer research, B2B lead research, business intelligence, and marketplace analysis.

The resulting records are stored in an Apify dataset with a simple structure that is easy to review and use in downstream data workflows.

### What Is a Moglix Email Scraper?

A Moglix Email Scraper is a keyword-driven data collection tool focused on publicly indexed Moglix information containing email addresses. Instead of manually searching for relevant Moglix pages and checking descriptions for contact information, you can configure search terms and email-domain filters and let the Actor collect matching email records.

The Actor searches for Moglix results based on your configured keywords and email domains. Optional location terms can further narrow the search. When a matching email is found in a result description, the Actor stores the email together with contextual information such as the result title, description, URL, and search keyword.

This makes the Actor useful when you need structured Moglix contact data for research rather than manually reviewing search results one by one.

### Key Features

| Feature                      | Description                                                                   | User Benefit                                      |
| ---------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------- |
| Keyword-based search         | Search Moglix using one or multiple keywords or queries.                      | Target specific business categories and roles.    |
| Multiple keywords            | Configure several search terms in one run.                                    | Expand research coverage without separate runs.   |
| Location filtering           | Optionally provide a country, state, or city.                                 | Narrow searches to a geographic area.             |
| Custom email domains         | Specify domains such as `@gmail.com`, `@yahoo.com`, or other domain suffixes. | Focus collection on the email types you need.     |
| Per-combination email target | `maxEmails` applies independently to each keyword and domain combination.     | Control the target for individual searches.       |
| Exclude words                | Skip descriptions containing configured words or phrases.                     | Reduce unwanted results.                          |
| Duplicate prevention         | Previously collected email addresses are not returned again during the run.   | Keep the resulting email dataset cleaner.         |
| Structured dataset           | Results are pushed to an Apify dataset with consistent fields.                | Make collected data easier to review and process. |

### What Data Can You Extract?

The Moglix Email Scraper returns five user-facing fields for each collected email record:

- **Keyword** — The search keyword associated with the result.
- **Title** — The title of the matching search result.
- **Description** — The description or snippet associated with the result.
- **URL** — The source URL associated with the search result.
- **Email** — The email address detected in the result description that matches the configured email-domain filter.

Together, these fields provide both the contact information and enough search-result context to understand where the email was found.

The Actor's dataset is therefore suitable for structured contact research rather than returning email addresses alone.

### Why Use the Moglix Email Scraper?

Manual business contact research can involve repeatedly searching for different keywords, reviewing search-result descriptions, identifying relevant contact information, and recording the results. The Moglix Email Scraper organizes these repetitive search tasks into a configurable Actor run.

You can use several targeted keywords instead of relying on one broad term. For example, searches around `manufacturer` and `supplier` can be configured separately, while additional related terms can be added when you need broader coverage.

The optional location field provides another way to refine a search. Similarly, custom email domains allow you to focus on particular types of addresses.

Because the output is structured into an Apify dataset, the collected records can be reviewed and analyzed as a consistent table.

### Benefits

- **Automated contact research** — Reduce repetitive manual searching for publicly indexed Moglix email information.
- **Targeted discovery** — Use specific keywords to focus research on relevant business categories.
- **Flexible geographic searches** — Add a country, state, or city when location is important.
- **Domain-specific collection** — Search for selected email-domain suffixes instead of treating all domains equally.
- **Structured results** — Receive consistent keyword, title, description, URL, and email fields.
- **Multiple search combinations** — Combine several keywords with several email domains for broader research.
- **Filtering support** — Exclude unwanted descriptions using words or phrases.
- **Duplicate control** — The Actor avoids returning the same email address more than once during a run.

### How to Use the Moglix Email Scraper

The workflow is straightforward:

1. Enter one or more keywords in the `keywords` field.
2. Optionally enter a country, state, or city in `location`.
3. Add the email-domain suffixes you want to search for in `customDomains`.
4. Set `maxEmails` to define the target for each keyword and domain combination.
5. Optionally add words or phrases to `excludeWords`.
6. Start the Actor.
7. Review the resulting records in the Apify dataset.

For better targeting, use specific search terms rather than relying exclusively on broad keywords. If results are too limited, consider adding related keywords, additional email domains, or a broader location.

### Input

The Actor requires the `keywords` field. The other configuration fields are optional.

| Field           | Type             | Required | Default                        | Description                                                                               |
| --------------- | ---------------- | -------- | ------------------------------ | ----------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["manufacturer", "supplier"]` | Keywords or queries used for the Moglix search.                                           |
| `location`      | String           | No       | `""`                           | Optional country, state, or city used to narrow searches.                                 |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`               | Email-domain suffixes to include, such as `@gmail.com` or `@yahoo.com`.                   |
| `maxEmails`     | Integer          | No       | `5`                            | Target number of emails 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.                   |

#### Keywords

`keywords` accepts a list of search terms or queries. Multiple specific terms can provide broader and more targeted coverage than using one general keyword.

For example:

- `manufacturer`
- `supplier`
- `industrial supplier`
- `electrical manufacturer`

The Actor processes the configured keyword and domain combinations separately.

#### Location

`location` is optional. Enter a country, state, or city when you want to narrow your search geographically.

Leave it empty when you do not want to apply a location filter.

#### Custom Email Domains

`customDomains` accepts email-domain suffixes. The default is:

`["@gmail.com"]`

You can provide multiple domains, for example:

- `@gmail.com`
- `@yahoo.com`
- `@outlook.com`

You can also specify other domain suffixes when they are relevant to your research.

#### Maximum Emails

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

Importantly, the configured value applies to each keyword + domain combination rather than acting as one shared target across the entire run.

For example, with 3 keywords, 2 domains, and `maxEmails` set to `20`, the Actor can target up to 20 addresses for each of the 6 combinations.

The target is not a guarantee that the requested number will be found. Results depend on the publicly indexed information available for the searches.

#### Exclude Words

`excludeWords` lets you skip result descriptions containing unwanted words or phrases.

Single-word entries use case-insensitive whole-word matching. Phrases are matched case-insensitively as phrases.

For example:

- `crypto`
- `onlyfans`
- `cryptocurrency business`

If a matching exclusion term appears in a result description, that result is skipped and its email is not collected.

### Input Example

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

### Output

The Actor stores collected records in the **Moglix Emails Dataset**. Each record contains the search context, result information, and matching email address.

| Field         | Description                                                                               |
| ------------- | ----------------------------------------------------------------------------------------- |
| `keyword`     | Keyword that was used for the search.                                                     |
| `title`       | Title of the matching result.                                                             |
| `description` | Description or search-result snippet associated with the result.                          |
| `url`         | URL associated with the result.                                                           |
| `email`       | Email address extracted from the description and matching the configured domain criteria. |

The output is designed to provide enough context to connect an email address with the search result from which it was collected.

### Output Example

```json
{
  "keyword": "manufacturer",
  "title": "Example Industrial Manufacturer",
  "description": "Example Industrial Manufacturer supplies industrial products and can be contacted at example@gmail.com.",
  "url": "https://www.moglix.com/example-profile",
  "email": "example@gmail.com"
}
```

The example illustrates the documented output structure. Actual values depend on the publicly indexed results available during the run.

### Use Cases

The Moglix Email Scraper can support several types of research and structured data workflows:

- **Supplier discovery** — Search for supplier-related Moglix results and collect matching publicly indexed contact emails.
- **Manufacturer research** — Find contact information associated with manufacturer-focused searches.
- **B2B lead research** — Build structured contact datasets around specific business keywords.
- **Marketplace research** — Study publicly indexed business information associated with Moglix.
- **Business intelligence** — Organize search-result contact information for further analysis.
- **Market research** — Collect keyword-specific contact records for targeted research projects.
- **Dataset creation** — Build structured datasets containing email addresses and their source context.
- **Geographic research** — Combine business keywords with country, state, or city filters.

The Actor should be used for legitimate research and contact-data workflows that respect applicable laws, platform rules, and privacy requirements.

### Advantages

The Actor provides a practical combination of keyword targeting, location filtering, email-domain selection, exclusion filtering, and structured output.

Its input structure allows you to create different research strategies without changing the Actor itself. You can focus on manufacturers, suppliers, or other relevant business terms and combine those terms with selected email domains.

The structured output also keeps the email address connected to its keyword, title, description, and URL, which can be useful when reviewing the relevance of collected records.

### Limitations

- The Actor can only collect email addresses that are present in the publicly indexed result information available to its searches.
- `maxEmails` is a target, not a guarantee that the requested number will be available.
- Narrow keywords or restrictive locations can produce fewer results.
- Restricting searches to a small number of email domains can reduce the number of matching addresses.
- Exclusion terms can intentionally remove otherwise matching results.
- Search-result availability can vary over time.
- The same email address is not collected repeatedly within the run.
- Free-tier runs are subject to a maximum of 100 collected emails when the configured limit is above that threshold or no limit is specified. Paid-plan behavior may differ according to the applicable Apify plan.

### Pros and Cons

| Pros                              | Cons                                           |
| --------------------------------- | ---------------------------------------------- |
| Supports multiple search keywords | Results depend on publicly indexed information |
| Optional geographic filtering     | Narrow searches may return fewer emails        |
| Custom email-domain filtering     | Requested email targets are not guaranteed     |
| Exclude-word filtering            | Exclusions can remove matching results         |
| Structured Apify dataset output   | Search-result availability can change          |
| Duplicate email prevention        | Free-tier runs have a 100-email maximum        |

### Comparison With Alternative Approaches

| Capability                  | Moglix Email Scraper        | Manual / Typical Alternative      |
| --------------------------- | --------------------------- | --------------------------------- |
| Keyword-based research      | Configurable keywords       | Requires repeated manual searches |
| Multiple keyword processing | Supported                   | Usually handled separately        |
| Email-domain filtering      | Configurable                | Often requires manual filtering   |
| Location targeting          | Optional location field     | Manually add geographic terms     |
| Exclusion filtering         | Supported                   | Manual review may be required     |
| Structured output           | Apify dataset fields        | Often requires manual collection  |
| Duplicate prevention        | Supported during collection | May require manual cleanup        |
| Repeatable configuration    | Saved as Actor input        | Manual process must be repeated   |

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

### Best Practices

- Start with a small `maxEmails` value to validate your search strategy.
- Use several specific keywords instead of relying only on one broad term.
- Add related business terms when the initial search produces limited results.
- Use `location` when geographic targeting matters.
- Leave `location` empty when broader coverage is more important.
- Add relevant email domains when you need to expand domain coverage.
- Use `excludeWords` carefully because matching descriptions are skipped entirely.
- Review the first results before increasing the size of a larger run.
- Validate important contact information before using it in a business workflow.
- Respect applicable privacy, data-protection, and platform requirements when using collected information.

### Troubleshooting

**Invalid Input**

Check that `keywords` is an array of strings and that `maxEmails`, when provided, is an integer between 1 and 10,000. Email domains should be provided as domain suffixes such as `@gmail.com`.

**Empty Results**

Try broader or more specific keywords depending on your research goal. You can also remove a restrictive location or add additional email domains.

**Partial Results**

A lower-than-expected result count does not necessarily indicate an input problem. The available indexed information may simply be smaller than the requested target.

**Missing Emails**

The Actor only collects matching email addresses available in the result descriptions. A page or result without a matching email does not produce an email record.

**Too Many Excluded Results**

Review the `excludeWords` list. A single matching word or phrase in a description causes that result to be skipped.

**Results Below the Requested Target**

Consider using additional relevant keywords, expanding the email-domain list, or broadening the location. The `maxEmails` setting represents a target rather than a guaranteed number of available results.

### Frequently Asked Questions

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

It searches for publicly indexed Moglix result information using configured keywords and email-domain filters, then creates structured records for matching email addresses.

**What data does the Moglix Email Scraper return?**

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

**Can I use multiple keywords?**

Yes. The `keywords` input accepts an array of search terms or queries, allowing multiple searches in one Actor run.

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

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

**Can I search for different email domains?**

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

**How does `maxEmails` work?**

The configured value is applied independently to each keyword + domain combination. For example, 2 keywords and 3 domains create 6 combinations, each with its own target.

**Does `maxEmails` guarantee the requested number of emails?**

No. It defines the collection target. The Actor can only return matching emails that are available in the indexed search information.

**What does `excludeWords` do?**

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

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

The Actor tracks collected email addresses and avoids adding the same email address more than once during the run.

**What should I do if the results are too limited?**

Try additional relevant keywords, broaden or remove the location filter, or add more email-domain suffixes.

**Is the output structured?**

Yes. Results are stored in an Apify dataset using consistent fields for the keyword, title, description, URL, and email.

### NLP Keywords

- Moglix email scraper
- Moglix email extraction
- Moglix contact data
- Moglix business contacts
- Moglix supplier emails
- Moglix manufacturer emails
- Moglix lead generation
- Moglix business leads
- Moglix contact research
- Moglix data extraction
- Moglix email finder
- Moglix supplier research
- Moglix manufacturer research
- Moglix B2B leads
- Moglix marketplace research
- Moglix contact discovery
- Moglix structured data
- Moglix email dataset
- Moglix business research
- Moglix lead research

### Related Keywords

- Moglix email scraper tool
- scrape Moglix emails
- extract emails from Moglix
- Moglix business email finder
- Moglix supplier contact scraper
- Moglix manufacturer contact finder
- Moglix B2B email scraper
- Moglix lead scraper
- Moglix contact extractor
- Moglix email data extraction
- Moglix supplier lead research
- Moglix manufacturer lead research
- Moglix marketplace contact research
- Moglix business lead extraction
- Moglix email collection
- Moglix public contact research
- keyword based Moglix scraper
- Moglix location email search
- Moglix domain email search
- Moglix contact dataset

### Final Overview

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

The Actor accepts multiple search keywords and creates structured dataset records containing the keyword, result title, description, URL, and matching email address. Its per-keyword and per-domain targeting gives users control over how broadly each search combination is explored, while duplicate prevention and exclusion filtering help keep the resulting dataset organized.

For the best results, start with focused keywords, test a small target, and refine the location, domains, or exclusion terms according to the quality of the returned data.

*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/moglix-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/moglix-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/moglix-email-scraper --silent --output-dataset

```

## MCP server setup

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