# Steam Email Scraper - Bulk Keywords, Decodes Hidden Emails (`code-beat/steam-email-scraper-ultra-fast-and-precise`) Actor

🎮 Steam Email Scraper gathers game developer and publisher emails from bulk keyword searches. 🔓 Decodes hidden addresses, skips duplicates. 🕹️ Ideal for game marketing, porting studios & indie publisher outreach.

- **URL**: https://apify.com/code-beat/steam-email-scraper-ultra-fast-and-precise.md
- **Developed by:** [Code Beat](https://apify.com/code-beat) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Steam Email Scraper

**Steam Email Scraper** is an Apify actor built to extract public email addresses from Steam based on the keywords and filters you provide. It’s a practical Steam email extractor and Steam contact scraper for marketers, researchers, and data teams who want to turn manual profile checking into fast, structured Steam data extraction at scale. 🚀

### What is Steam Email Scraper? 🔍

Steam Email Scraper is an automated web scraping tool that helps you find publicly available email addresses from Steam profiles using your chosen keywords. Instead of spending hours on manual Steam user lookup and profile review, this Steam profile email finder collects contacts and profile context in a structured format you can export and analyze quickly.

It’s especially useful for marketers, sales teams, recruiters, and analysts who need Steam marketing leads or Steam user contacts without repetitive research work. By combining keyword targeting with email-domain filters, the Steam account email scraper helps you build focused result sets and scale your outreach workflow with less effort. ⚡

### What Data Does a Steam Email Scraper Collect? 📊

This Steam community scraper returns a compact set of fields designed for lead review and follow-up. The dataset includes the keyword that surfaced the result, the profile title, supporting description text, the profile URL, and the extracted email address.

| Data Category | Fields Extracted | Description |
|---|---|---|
| Contact | `email` | Public email address found in publicly available Steam content |
| Identity | `title` | Profile title or name shown in the result |
| Context | `description` | Supporting text associated with the result |
| Discovery | `keyword` | Search term that surfaced this result |
| Navigation | `url` | Direct link to the Steam profile or page |

### What Do Results from Steam Email Scraper Look Like? 👀

Each result is saved as a structured JSON record in your Apify dataset. Here’s a realistic example of what Steam profile data scraper output looks like:

```json
{
  "keyword": "founder",
  "title": "Megan Carter",
  "description": "Founder at Indie Forge Studios | Open to collaborations and partnerships",
  "url": "https://store.steampowered.com/curator/12345678-Indie-Forge-Studios/",
  "email": "megan.carter@gmail.com"
}
```

Results are available in JSON by default and can also be exported from Apify in CSV format.

#### Core Features: Steam Email Scraper ⚡

| Feature | Benefit |
|---|---|
| ✅ **Keyword-Driven Targeting** | Find relevant Steam profiles by the terms you care about |
| ✅ **Custom Email Domain Filter** | Focus on specific address types such as `@gmail.com` or `@yahoo.com` |
| ✅ **Configurable Result Cap** | Use `maxEmails` to control how many emails you collect |
| ✅ **Location Filter** | Narrow results using a location value when needed |
| ✅ **Structured Output** | Clean dataset rows make Steam data extraction easy to review and export |
| ✅ **Real-Time Saving** | Results are stored as they are found, reducing the risk of lost data |
| ✅ **Built-In Proxy Support** | Helps keep scraping reliable on larger runs |
| ✅ **Retry and Fallback Behavior** | Adds resilience when pages are slow or inconsistent |
| ✅ **Public Data Only** | Collects information from publicly available sources |

### Getting Started with Steam Email Scraper 🚀

1. **Open Apify Store** — Go to [apify.com/store](https://apify.com/store) and search for Steam Email Scraper.
2. **Click Try for Free** — Sign in or create an Apify account.
3. **Open the Input Tab** — Configure your keywords and filters.
4. **Add Keywords** — Enter the Steam user lookup terms you want to target.
5. **Set Optional Filters** — Add a location or custom email domains if needed.
6. **Cap Your Results** — Set `maxEmails` to limit the run and control cost.
7. **Click Start** — Launch the run and monitor progress in the logs.
8. **Access Your Data** — Open the dataset to preview or export your Steam marketing leads.

No coding required. It’s a fast way to turn Steam account lookup work into an organized lead list. ✅

### Ways to Use Steam Email Scraper 💡

- 🎯 **B2B Lead Generation** — Build focused Steam user contacts for outreach campaigns
- 📣 **Email Marketing** — Collect public contact details for newsletters or follow-up sequences
- 🤝 **Recruitment** — Find reachable creators, community managers, and profile owners
- 🔬 **Market Research** — Study Steam communities, niches, and profile patterns
- 📊 **CRM Enrichment** — Add Steam profile data to your existing contact records
- ⚙️ **Workflow Automation** — Use the dataset in repeatable Steam data extraction pipelines

#### Input Parameters — Steam Email Scraper

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | Yes | `["manager","founder"]` | A list of keywords or queries to search for. |
| `location` | String | No | `""` | Location used to filter search results. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | A list of custom email domains to include in the extraction. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

#### Output Parameters — Steam Email Scraper

```json
{
  "keyword": "founder",
  "title": "Megan Carter",
  "description": "Founder at Indie Forge Studios | Open to collaborations and partnerships",
  "url": "https://store.steampowered.com/curator/12345678-Indie-Forge-Studios/",
  "email": "megan.carter@gmail.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that returned this result. |
| `title` | Title | text | The profile title or name shown in the record. |
| `description` | Description | text | Supporting text extracted with the result. |
| `url` | Url | link | Direct link to the Steam result page. |
| `email` | Email | text | The extracted public email address. |

### Why Choose This Steam Email Scraper? 🏆

If you need a Steam web scraper that is simple to run and easy to export, this actor is built for speed and clarity. It combines keyword targeting, email-domain filtering, structured JSON output, and built-in proxy support for reliable scraping. That means less manual checking, faster list building, and a smoother workflow for Steam profile scraper tasks and Steam email harvesting projects.

Because results are saved into a dataset as they are found, you can start analyzing leads right away. If you need help or want to discuss a tailored setup, contact <codebeatapi@gmail.com>. 📧

### How Many Results Can You Scrape? 📈

You can set `maxEmails` anywhere from 1 to 10,000. The actual volume depends on how many publicly available Steam profiles match your keywords and filters. Broader keywords and more domain options can improve coverage, while tighter filters may reduce the total number of results.

The dataset can store all returned records, so you can export your Steam account email scraper results whenever you’re ready. For larger runs, allow extra time in your Apify run options if needed.

### Legal Guidelines for Scraping Steam ⚖️

Steam Email Scraper collects only publicly available data from Steam profiles and pages. It does not require logins or access private content. You are responsible for using the data in line with Steam’s terms, privacy rules, and applicable email and marketing regulations.

Use the results responsibly and only for legitimate purposes. If you need help with data removal or have a compliance-related request, contact <codebeatapi@gmail.com>. ✅

### FAQ — Steam Email Scraper ❓

#### How does the Steam Email Scraper identify data?

The actor uses your keywords and email-domain filters to find relevant public Steam content, then extracts publicly available email addresses and profile details into a dataset.

#### What Steam profile types can I scrape?

You can scrape any public Steam profile or page that includes a publicly visible email address in its accessible content. Private or restricted content is not part of the output.

#### How did the Steam Email Scraper perform in our tests?

The actor is designed for reliable public web data collection with incremental saving, retries, and fallbacks for resilience. Actual results depend on how many matching Steam profiles have public contact details.

#### Why scrape Steam for contacts?

Steam can be a useful source of Steam marketing leads, community contacts, and profile-based research when you need public contact information tied to specific keywords or niches.

#### How much does the Steam Email Scraper cost?

Apify pricing depends on your plan and usage. You can control scraping volume with `maxEmails`, which helps you manage cost and keep each run focused.

#### How does the Steam Email Scraper help my business?

It converts manual Steam user lookup work into a clean dataset you can use for outreach, research, CRM enrichment, or Steam data extraction workflows.

#### What challenges should I expect when using the Steam Email Scraper?

Not every Steam profile includes a public email address, so results can vary by keyword set and domain filters. If your first run is small, try broader keywords or add more email domains.

#### How do I choose a high-performing Steam Email Scraper?

Look for keyword targeting, a clear output schema, configurable limits, built-in proxy support, and incremental saving. Steam Email Scraper includes these practical features in a simple, structured workflow.

### Conclusion 🏁

Steam Email Scraper is a fast, practical way to collect public emails from Steam and turn them into usable leads. Whether you’re building a contact list, enriching your CRM, or doing Steam profile data scraper research, it helps you move from manual work to structured results quickly. 🚀

### 🆘 Support & Feedback

Have a question or feature request for Steam Email Scraper?

- 🐞 **Bug Reports:** Contact the team with details about the issue
- ✨ **Custom Solutions & Feature Requests:** Reach out for tailored help
- 📧 **Email:** <codebeatapi@gmail.com>

### Country & Time Targeting

Both filters are applied to the Google query itself, so they shape which pages
the dork is answered from rather than filtering after the fact.

**Target Country** - runs the search as if from that country (`gl`). Turn on
**Strict country filter** to additionally restrict results to pages Google
attributes to it (`cr=countryXX`); that is much tighter and returns noticeably
fewer results. Leave the country on *Global (no country filter)* for worldwide
results.

**Result Language** - restricts results to a single language (`hl` + `lr`).

**Time Range** - limits results to a publication window: past hour, 24 hours,
week, month, year, or an explicit *Custom range* using **Custom range: from** /
**to** in `YYYY-MM-DD` form. A page Google indexed last week is far more likely
to carry a live mailbox than one it last saw five years ago.

Selecting *Custom range* without either date falls back to no time filter rather
than searching all of time by accident.

# Actor input Schema

## `scrapeMode` (type: `string`):

Find New Emails (default) searches Airbnb by keyword. Clean My List skips searching entirely and instead runs the emails you paste into Email List (below) through the same deliverability checks.

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

A list of keywords or queries to search for.

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

Location to filter search results.

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

List of custom email domains

## `emailList` (type: `array`):

Paste the emails you want checked for deliverability. Only used when Scrape Mode is set to "Clean My List".

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

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `verificationMode` (type: `string`):

Quick Check (default) validates syntax and MX records only - fast, no added latency. Deep Check additionally flags disposable-domain addresses and checks each domain against a public spam blocklist (Spamhaus DBL). Off skips validation entirely.

## `minQualityScore` (type: `number`):

Drop any contact whose quality score (0.0-1.0) falls below this. Leave at 0 for no filter.

## `excludeCatchAll` (type: `boolean`):

Drop contacts on domains confirmed to accept mail for any address (only applies when that signal is available).

## `requireMxValid` (type: `boolean`):

Drop any contact whose domain has no valid mail server (MX record).

## `targetCountry` (type: `string`):

Ask Google to answer as if searching from this country. Leave on "Global (no country filter)" for worldwide results.

## `strictCountry` (type: `boolean`):

Restrict results to pages Google attributes to the target country (cr=countryXX), instead of only preferring them. Much tighter targeting, noticeably fewer results.

## `searchLanguage` (type: `string`):

Restrict results to one language. Leave on "Any language" for no filter.

## `timeRange` (type: `string`):

Only return pages Google indexed within this window. Recent pages are more likely to hold a mailbox that still works.

## `customDateFrom` (type: `string`):

Only used when Time Range is "Custom range". Format: YYYY-MM-DD.

## `customDateTo` (type: `string`):

Only used when Time Range is "Custom range". Format: YYYY-MM-DD.

## Actor input object example

```json
{
  "scrapeMode": "Find New Emails",
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "emailList": [],
  "maxEmails": 20,
  "verificationMode": "Quick Check",
  "minQualityScore": 0,
  "excludeCatchAll": false,
  "requireMxValid": false,
  "targetCountry": "Global (no country filter)",
  "strictCountry": false,
  "searchLanguage": "",
  "timeRange": "Any time",
  "customDateFrom": "",
  "customDateTo": ""
}
```

# 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": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "emailList": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("code-beat/steam-email-scraper-ultra-fast-and-precise").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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "emailList": [],
}

# Run the Actor and wait for it to finish
run = client.actor("code-beat/steam-email-scraper-ultra-fast-and-precise").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "emailList": []
}' |
apify call code-beat/steam-email-scraper-ultra-fast-and-precise --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,code-beat/steam-email-scraper-ultra-fast-and-precise"
        }
    }
}

```

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/4obhhlvYY2v7PNv9b/builds/WpYrSH6QYRox3zxDV/openapi.json