# IMDb Email Scraper (`email_scraper/imdb-email-scraper`) Actor

IMDb Email Scraper finds publicly indexed IMDb contact emails using targeted keywords, locations, and custom email domains. Extract structured lead data with titles, descriptions, URLs, and emails for producer research, film industry prospecting, entertainment outreach, and contact discovery.

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

### IMDb Email Scraper

**IMDb Email Scraper** is an Apify Actor designed to extract publicly visible email addresses associated with IMDb search results based on keywords or search terms. It searches for relevant IMDb pages, identifies email addresses matching the domains you specify, and stores the results in a structured dataset.

You can target broad topics, professional roles, or specific searches such as `Production`, `Producer`, `Film Director`, `Actor`, or other IMDb-related terms. An optional location filter can further narrow the search to a country, state, or city.

The Actor is useful for **lead research, market research, contact discovery, business intelligence, audience research, and structured IMDb data collection** where publicly listed email addresses are available in search-result content.

### What Is the IMDb Email Scraper?

The IMDb Email Scraper searches for IMDb-related pages using the keywords you provide and looks for email addresses associated with the selected email-domain suffixes.

For each keyword and email-domain combination, the Actor processes search results and collects unique email addresses it can identify. The resulting records include the search keyword, page title, description snippet, IMDb-related URL, and extracted email address.

The Actor supports optional geographic targeting through the `location` field. You can leave this field empty to search without a geographic filter or enter a country, state, or city to make the search more specific.

The scraper also includes an exclusion filter that can skip search-result descriptions containing specified words or phrases.

### Key Features

| Feature                    | Description                                                              | User Benefit                                                |
| -------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------- |
| Keyword-based search       | Searches IMDb-related results using your specified keywords or queries   | Lets you define the audience or topic you want to research  |
| Email extraction           | Identifies email addresses matching configured domain suffixes           | Produces directly usable contact data                       |
| Custom email domains       | Supports domains such as `@gmail.com` and other user-specified suffixes  | Gives you more control over the type of addresses collected |
| Location filtering         | Optionally adds a country, state, or city to the search                  | Helps narrow research geographically                        |
| Exclude words              | Skips snippets containing specified words or phrases                     | Helps reduce unwanted results                               |
| Unique email tracking      | Previously encountered email addresses are not collected again           | Reduces duplicate contacts                                  |
| Structured dataset output  | Results are pushed incrementally to the Apify dataset                    | Makes collected data easier to review and export            |
| Configurable result target | `maxEmails` can be set from 1 to 10,000 per keyword + domain combination | Lets you control the intended collection depth              |
| Resume support             | Progress is persisted during execution                                   | Helps preserve run progress when a run is interrupted       |

### What Data Can You Extract?

The IMDb Email Scraper creates structured records containing information associated with the search result from which an email address was identified.

The main data includes:

- **Keyword** used to generate the search
- **Title** of the matching result
- **Description** or search-result snippet
- **URL** of the matching result
- **Email** address extracted from the result
- **Network** identifier returned by the Actor, which is `IMDb.com`

The Actor focuses specifically on email addresses that match the email-domain suffixes configured in `customDomains`. For example, using `@gmail.com` limits extraction to addresses containing that suffix.

Because the extraction depends on publicly available search-result content, the Actor can only return information that is actually present and discoverable in the processed results.

### Main Benefits

| Benefit                     | Explanation                                                                                  |
| --------------------------- | -------------------------------------------------------------------------------------------- |
| Automated contact discovery | Reduces the need to manually inspect IMDb search results for publicly listed email addresses |
| Structured information      | Stores extracted contacts together with their related search context                         |
| Flexible targeting          | Keywords, locations, email domains, and exclusion terms can all be configured                |
| Better search coverage      | Multiple keyword and domain combinations can be processed in one run                         |
| Duplicate reduction         | Unique email tracking helps avoid repeatedly storing the same email address                  |
| Incremental results         | Data is pushed to the dataset as contacts are collected                                      |
| Research-friendly           | Useful for lead research, contact discovery, and structured data workflows                   |

### Why Use This Actor?

Manual IMDb contact research can involve opening many search results, checking descriptions, identifying available contact information, and copying data into a separate spreadsheet or database.

The IMDb Email Scraper turns that repetitive search workflow into an automated Actor run. Instead of checking every result individually, you provide the search criteria and let the Actor collect matching email addresses into a structured dataset.

The biggest advantage is flexibility. You can combine several keywords with several email-domain suffixes and optionally add a location. This makes it possible to build targeted searches rather than relying on one broad query.

For example, a user researching film professionals could use keywords such as:

- `Film Producer`
- `Film Director`
- `Production`
- `Casting Director`
- `Actor`
- `Film Production`

Additional related keywords can increase the breadth of the search.

### How to Use the IMDb Email Scraper

Start by entering one or more relevant keywords in the **Keywords or Queries** field.

For better coverage, use several specific and related terms instead of relying on a single broad keyword. A combination such as `Film Producer`, `Movie Producer`, and `Independent Film Producer` can target different search-result variations.

Next, optionally enter a location. For example:

- `United States`
- `New York`
- `California`
- `Los Angeles`

Then select the email-domain suffixes you want the Actor to search for. The default value is `@gmail.com`, but additional domains can be entered.

Set `maxEmails` according to the desired collection depth and use `excludeWords` when certain descriptions should be ignored.

### Input

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

#### Input Fields

| Input           | Type             | Required | Default                      | Description                                                                                          |
| --------------- | ---------------- | -------- | ---------------------------- | ---------------------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["Production", "Producer"]` | Keywords or queries used to search for relevant IMDb results                                         |
| `location`      | String           | No       | Empty                        | Optional country, state, or city used to narrow searches geographically                              |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`             | Email-domain suffixes to include during extraction                                                   |
| `maxEmails`     | Integer          | No       | `5`                          | Target number of emails collected for each keyword + domain combination; supported range is 1–10,000 |
| `excludeWords`  | Array of strings | No       | `[]`                         | Words or phrases that cause a search-result description to be skipped                                |

The `keywords` field uses a list, allowing multiple searches within a single run.

The `customDomains` field also accepts multiple values. For example, you can provide `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

The `maxEmails` setting is applied independently to each **keyword + domain combination**. For example, three keywords combined with two domains create six combinations, each with its own target.

The `excludeWords` filter is case-insensitive. Single words are matched as whole words, while phrases are matched as text within the description.

### Input Example

```json
{
  "keywords": [
    "Film Producer",
    "Film Director",
    "Production"
  ],
  "location": "United States",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

This configuration searches for the specified IMDb-related terms, limits the search geographically to the United States, checks three email-domain suffixes, and targets up to 10 emails for each keyword + domain combination.

### Output

The IMDb Email Scraper pushes collected results incrementally to the Apify dataset.

Each collected email is associated with the search context that produced it, making the dataset more useful for research and follow-up processing.

The default dataset view presents these primary columns:

- Keyword
- Title
- Description
- URL
- Email

The Actor also includes a `network` value in each pushed record, identifying the source as `IMDb.com`.

### Output Fields

| Output Field  | Description                                       |
| ------------- | ------------------------------------------------- |
| `network`     | Source network identifier returned as `IMDb.com`  |
| `keyword`     | Keyword or query associated with the result       |
| `title`       | Title of the search result                        |
| `description` | Description or snippet associated with the result |
| `url`         | URL of the matching result                        |
| `email`       | Extracted email address                           |

The `email` field contains the unique address identified from the processed result description and matching the configured domain suffixes.

### Output Example

```json
{
  "network": "IMDb.com",
  "keyword": "Film Producer",
  "title": "Example IMDb Result",
  "description": "Example description containing producer contact information.",
  "url": "https://www.imdb.com/example",
  "email": "producer@example.com"
}
```

The values above are illustrative examples of the output structure rather than guaranteed real IMDb contact information.

### Use Cases

The IMDb Email Scraper can support several practical research workflows where publicly discoverable IMDb-related contact information is relevant.

**Lead research:** Build structured lists of potentially relevant industry contacts associated with terms such as producers, directors, actors, or production.

**Market research:** Collect contact-oriented search data for specific professional categories or geographic markets.

**Film and entertainment research:** Explore publicly discoverable contact information connected to selected IMDb-related searches.

**Business intelligence:** Combine keyword and location targeting to create more focused datasets for analysis.

**Contact discovery:** Identify email addresses that are publicly surfaced in search-result content.

**Research automation:** Run repeatable keyword-based data collection workflows through Apify rather than manually reviewing individual results.

### Advantages

The IMDb Email Scraper is particularly useful when your research requires multiple combinations of topics and email domains.

Instead of running a single broad search, you can build a matrix of targeted queries. For example, four professional keywords and three email domains result in twelve keyword + domain combinations, each processed independently according to the configured target.

The location field provides another level of targeting. A blank location allows broader searching, while a specific city or country can make the search more focused.

The exclusion feature is also useful when certain terms frequently appear in unwanted descriptions. Adding those words or phrases can prevent matching snippets from being used for email extraction.

### Pros and Cons

| Pros                            | Cons                                                                             |
| ------------------------------- | -------------------------------------------------------------------------------- |
| Keyword-based IMDb research     | Results depend on publicly discoverable search content                           |
| Multiple keyword support        | Narrow searches may produce sparse results                                       |
| Multiple email-domain suffixes  | Not every matching result contains an email address                              |
| Optional location filtering     | Location filtering can reduce the available result set                           |
| Exclude-word filtering          | Excluding too many terms may remove useful results                               |
| Structured Apify dataset output | Requested targets are not guaranteed if suitable public results are unavailable  |
| Duplicate email prevention      | The same email may appear in different contexts but is tracked as a unique email |

### Comparison With Alternative Approaches

| Capability                     | IMDb Email Scraper   | Manual Research                      |
| ------------------------------ | -------------------- | ------------------------------------ |
| Keyword-based automation       | Yes                  | Manual                               |
| Multiple search combinations   | Supported            | Requires repeated searches           |
| Structured output              | Apify dataset        | Usually requires manual organization |
| Email-domain filtering         | Configurable         | Manual inspection                    |
| Location targeting             | Supported            | Manual query refinement              |
| Exclusion filtering            | Supported            | Manual checking                      |
| Duplicate email tracking       | Built into the Actor | Usually manual                       |
| Incremental dataset collection | Supported            | Manual copying                       |

The Actor does not guarantee better results than every alternative workflow. Its main advantage is automating repetitive search and organization steps.

### Best Practices

Use several closely related keywords rather than one overly broad term. Specific professional or industry-related phrases can help produce more focused searches.

Use multiple email domains when you need broader email coverage. The default is `@gmail.com`, but you can add other domains that are relevant to your research.

Keep the location field broad enough to allow useful results. A highly specific geographic filter may significantly reduce the available search material.

Start with a smaller `maxEmails` value during testing. After reviewing the results, increase it for larger collection jobs.

Use `excludeWords` carefully. Exclusion terms are applied to the description snippet, so an overly broad term can cause otherwise relevant results to be skipped.

For larger runs, consider increasing the run timeout through Apify Run options when the workload requires substantial pagination and multiple keyword/domain combinations.

### Troubleshooting

**Few or no results:** Try broader keywords, add related search terms, reduce restrictive exclusions, or remove the location filter.

**No emails found:** Check the selected `customDomains`. The Actor only extracts addresses matching the configured suffixes, so using only one domain may limit the results.

**Results are below the requested target:** A `maxEmails` value is a collection target, not a guarantee. The Actor may stop when suitable search results are exhausted, when pages stop producing new emails, or when additional result pages become inefficient.

**Unexpectedly small geographic coverage:** Review the `location` value and consider using a broader country, state, or city term.

**Some descriptions are missing useful contacts:** Review `excludeWords` and remove terms that may be unintentionally filtering relevant snippets.

**A run is interrupted:** The Actor persists progress during execution, allowing its stored state to retain collected email information and the current search position.

### Limitations

The IMDb Email Scraper can only extract email addresses that are publicly available in the processed search-result content and that match the configured email-domain suffixes.

A requested number of emails is not a guarantee that that number will be found. Search coverage depends on the availability of matching results and publicly listed contact information.

The Actor may stop processing a keyword/domain combination when there are repeated pages without new email addresses, repeated empty result pages after deeper pagination, or low recent collection efficiency.

Each keyword + domain combination has its own `maxEmails` target. The supported configuration range is **1 to 10,000** per combination.

Free Apify usage also applies a maximum configured `maxEmails` value of **100** per combination. This is an implementation limit on the per-combination target; the Actor's source code does not enforce a separate global 100-email stop across the entire run.

### Frequently Asked Questions

#### What does the IMDb Email Scraper do?

The IMDb Email Scraper searches for IMDb-related results using your keywords and extracts publicly discoverable email addresses that match your configured email-domain suffixes.

#### What data does the IMDb Email Scraper return?

It returns the keyword, result title, description, URL, extracted email, and the source network identifier `IMDb.com`.

#### What input does the Actor require?

The `keywords` field is required. You can provide one or more search terms as an array.

#### Can I use multiple keywords?

Yes. The `keywords` input accepts multiple values, allowing you to search several related topics within one run.

#### Can I use multiple email domains?

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

#### Can I filter results by location?

Yes. The optional `location` field accepts a country, state, or city. Leaving it blank performs the search without a geographic filter.

#### How does `maxEmails` work?

`maxEmails` sets the target number of email addresses for each keyword + domain combination. It supports values from 1 through 10,000.

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

No. The configured value is a target. The actual number depends on the availability of matching search results and publicly discoverable email addresses.

#### Can I exclude certain results?

Yes. Add words or phrases to `excludeWords`. If a configured term appears in a result description, that snippet is skipped.

#### Is the Actor suitable for automation?

Yes. It is designed as an Apify Actor and produces structured dataset records that can be used in repeatable research and automation workflows.

#### Why are my results sparse?

A search may be too narrow, a location filter may be restrictive, selected email domains may have limited coverage, or matching public email addresses may simply be unavailable. Broader or additional related keywords can improve coverage.

### NLP Keywords

- IMDb email scraper
- IMDb email extraction
- IMDb contact extraction
- IMDb contact data
- IMDb lead research
- IMDb email finder
- IMDb contact finder
- IMDb data extraction
- IMDb profile research
- IMDb search scraper
- IMDb leads
- IMDb business contacts
- IMDb professional contacts
- email address extraction
- keyword-based email scraping
- public contact discovery
- structured IMDb data
- entertainment industry contacts
- film industry lead research
- contact research automation

### Related Keywords

- IMDb email scraper
- IMDb contacts scraper
- IMDb email finder
- IMDb data scraper
- IMDb lead scraper
- IMDb contact scraper
- film producer email
- film director contacts
- entertainment industry email contacts
- movie industry lead research
- IMDb professional contacts
- IMDb profile contacts
- IMDb contact discovery
- email extraction from IMDb
- IMDb keyword scraper
- IMDb search data extraction
- entertainment business research
- film industry contact research
- public email discovery
- IMDb lead generation

### Final Overview

The **IMDb Email Scraper** provides a configurable way to search IMDb-related results and collect publicly discoverable email addresses into a structured Apify dataset. You can control the search with keywords, optional geographic targeting, custom email domains, maximum email targets, and exclusion terms.

For better coverage, use multiple relevant keywords, carefully select email domains, avoid unnecessarily narrow locations, and review your exclusion terms before larger runs. Because results depend on publicly available search content, the quality and quantity of collected contacts can vary by query.

The Actor is best suited to users who need an automated, structured workflow for IMDb-focused email research and contact discovery.

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

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

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

```

## MCP server setup

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