# Patreon Email Scraper (`solid-scraper/patreon-email-scraper`) Actor

🚀 Patreon Email Scraper extracts creator emails from Patreon campaigns fast and accurately. 🎯 Find targeted contacts by niche and keywords—ideal for outreach, agencies, and growth teams. 📩 Get more leads, less manual work.

- **URL**: https://apify.com/solid-scraper/patreon-email-scraper.md
- **Developed by:** [SolidScraper](https://apify.com/solid-scraper) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

### Patreon Email Scraper 📬

**Patreon Email Scraper** is an Apify actor that scrapes email addresses from publicly available Patreon-related sources using your chosen **keywords** and **custom email-domain filters**. If you’re looking for a *Patreon email scraper* to build a *Patreon creator email list*, this tool automates the heavy lifting—helping you turn research into outreach-ready data in less time.

Whether you’re a marketer, researcher, or data analyst, this **Patreon Email Scraper** supports workflows like extracting emails for lead generation, scraping Patreon contact email data, and building email lists for campaigns at scale—saving you hours of manual work.

***

### Why choose Patreon Email Scraper?

| Feature | Benefit |
| --- | --- |
| ✅ **Keyword-driven extraction** | Searches using your provided keywords to find relevant email mentions |
| ✅ **Custom email domains filter** | Keeps results focused on the email types you care about (e.g., `@gmail.com`) |
| ✅ **Proxy configuration support** | Helps you run reliable scraping jobs using your proxy settings |
| ✅ **Fallback logic for empty results** | If no emails are found, the actor can switch to a fallback proxy approach to improve outcomes |
| ✅ **Structured JSON output** | Produces consistent records with `keyword`, `title`, `description`, `url`, and `email` fields |
| ✅ **Deduplication (no repeats)** | Avoids duplicate emails using internal tracking of already-seen addresses |

***

### Key features

- 🔎 **Patreon email scraping by keywords**: Use your keyword list to target the most relevant Patreon creator email opportunities.
- 🎯 **Email-domain filtering**: Provide `customDomains` so the scraper focuses on specific domains while harvesting emails.
- 🧩 **Platform setting included**: The actor includes a `platform` input (currently only `Patreon`) so your runs are explicitly scoped.
- 🛡️ **Proxy configuration support + resilience**: Includes built-in proxy handling so runs can succeed even when connectivity varies.
- 🔁 **Fallback behavior for empty batches**: If no emails are found for a keyword, it can automatically switch to a fallback proxy configuration to try again.
- 💾 **Clean, structured dataset records**: Each extracted record includes the exact `email` plus the context fields used to find it.
- 📊 **Bulk collection workflow**: Loops over every combination of `keywords` and `customDomains`, collecting results across your full batch.

***

### Input

Provide input via an `input.json` file. Example structure:

```json
{
  "keywords": ["john", "marketing"],
  "location": "",
  "platform": "Patreon",
  "customDomains": ["@gmail.com"],
  "proxyConfiguration": {}
}
```

#### Input Fields

| Field | Required | Description |
| --- | --- | --- |
| `keywords` | ✅ Yes | A list of keywords to search for. The actor will use each keyword during scraping. |
| `location` | ❌ No | Optional location text used to filter results. Leave it empty for no location filtering. |
| `platform` | ❌ No | Platform selector. Choose `Patreon` (this actor is scoped to Patreon). |
| `customDomains` | ❌ No | List of custom email domains used to filter which emails are collected (e.g., `@gmail.com`). |
| `proxyConfiguration` | ❌ No | Configure proxies for this Actor. This is an object used to control proxy behavior. |

Nested `proxyConfiguration` fields (documented by the actor input schema behavior):

| Field | Required | Description |
| --- | --- | --- |
| `proxyConfiguration.proxy support` | ❌ No | When provided, controls whether the actor uses Apify Proxy based on your configuration. |
| `proxyConfiguration.proxy support` | ❌ No | Optional list of proxy group names used inside the proxy configuration. |

> Note: In the actor logic, if proxy settings are not selected by the user, it can automatically obtain a proxy configuration and may use fallback behavior when no emails are found.

***

### Output

The actor saves collected results in **JSON format** by pushing an array of records to the default dataset.

Sample output:

```json
[
  {
    "keyword": "marketing",
    "title": "Example Result Title",
    "description": "Some publicly available snippet text that includes contact info.",
    "url": "http://example.com/",
    "email": "contact@example.com"
  }
]
```

#### Output Fields

| Field | Type | Description |
| --- | --- | --- |
| `keyword` | string | The keyword currently being used for extraction. |
| `title` | string | The title text associated with the result item where email content was found. |
| `description` | string | Extracted text context from the result description that contained (or led to) the email. |
| `url` | string | The link URL associated with the extracted result item. |
| `email` | string | The extracted email address. |

The actor also deduplicates emails internally, so each email should appear only once per run.

***

### How to use Patreon Email Scraper (via Apify Console)

1. **Open Apify Console**\
   Log in at https://console.apify.com and go to the **Actors** tab.

2. **Find Patreon Email Scraper**\
   Search for **Patreon Email Scraper** and open the actor page.

3. **Go to the INPUT section**\
   Configure the built-in input form or upload your `input.json`.

4. **Set your keywords**\
   Enter one or more items in `keywords` (e.g., creator topics, brand terms, or names).\
   This actor uses every keyword you provide, so include only what you want to target.

5. **(Optional) Filter by location**\
   Add `location` if you want the run to filter results using that location text. Leave it blank to scrape without location filtering.

6. **Choose email domains to collect**\
   In `customDomains`, list the domains you want to harvest (for example: `@gmail.com`).\
   This helps keep results aligned with your outreach preferences.

7. **(Optional) Configure proxies**\
   If you want to control how requests are routed, fill out `proxyConfiguration`.\
   The actor supports proxy configuration and can also switch to a fallback proxy approach when a keyword run returns no emails.

8. **Run and monitor results**\
   Start the run with the **Run** button. During execution, watch logs for progress and extracted entries.\
   When finished, open the **OUTPUT** dataset to view and export the JSON results (e.g., JSON/CSV depending on your workflow).

No coding required—get accurate Patreon email scraping results in minutes with this **Patreon Email Scraper**.

***

### Advanced features & SEO optimization

- 🔍 **Engineered for “Patreon email scraper” workflows**: Designed specifically for *scrape Patreon emails* use cases driven by `keywords` + `customDomains`.
- 📦 **Patreon creator email list building**: Ideal for assembling a *Patreon subscriber email extractor* style dataset where each record includes email + context.
- 🛡️ **Rate/availability resilience via proxy handling**: Includes proxy support and fallback logic to improve real-world success rates when runs are inconsistent.
- 🧼 **Deduplication for cleaner outreach lists**: Prevents repeated emails from cluttering your *Patreon lead generation email scraper* output.
- 📊 **Structured results for fast downstream use**: Output records include `keyword`, `title`, `description`, `url`, and `email`, which makes it easier to plug into analysis or outreach tools.

***

### Best use cases

- 📈 **Outreach marketers building a Patreon outreach email scraper list**: Collect targeted emails quickly by topic (keywords) and domain filters (`customDomains`).
- 🧑‍🔬 **Market researchers mapping creator communities**: Use *Patreon email harvesting tool* outputs to study contact patterns around specific niches.
- ✉️ **CRM and sales ops enriching lead databases**: Import *Patreon contact email scraper* results into your pipeline for segmentation and follow-up.
- 🧠 **Data analysts validating email-domain hypotheses**: Analyze which email domains appear most often for specific keywords and contexts.
- 🧾 **Campaign managers extracting Patreon campaign email extraction data**: Gather email contacts that appear in publicly available contexts tied to your campaign themes.
- 💻 **Developers building bulk email list workflows**: Use the JSON dataset output for automated processing (dedupe, scoring, and enrichment) in your own systems.
- 👥 **Creators and agencies sourcing fan email leads**: Support *Patreon fan email scraper* tasks where you need faster list building for outreach and partnerships.

***

### Technical specifications

- **Supported Input Formats**
  - ✅ `keywords` as an array of strings
  - ✅ `location` as a string (optional)
  - ✅ `platform` with the `Patreon` option
  - ✅ `customDomains` as an array of strings
  - ✅ `proxyConfiguration` as an object (optional)

- **Proxy Support**
  - ✅ Yes—supports user-provided proxy configuration via `proxyConfiguration`
  - ✅ Built-in fallback proxy behavior when no emails are found for a keyword run

- **Retry Mechanism**
  - ✅ Uses resilient execution patterns (the actor includes fallback logic when needed)

- **Dataset Structure**
  - ✅ JSON array of records pushed via `await Actor.push_data(results)`
  - Records include: `keyword`, `title`, `description`, `url`, `email`

- **Rate Limits & Performance**
  - ⚠️ Performance varies based on network conditions and proxy routing, since the actor makes HTTP requests per keyword/domain combination.

- **Limitations**
  - ❌ Only extracts emails that match your `customDomains` filters
  - ❌ Emails are sourced only from publicly available content that contains email-like strings matching the domain filter

***

### FAQ

#### Can I scrape Patreon emails for multiple keywords at once?

✅ Yes. You can provide multiple items in the `keywords` array, and the actor loops through each keyword while collecting matching emails, producing a combined JSON dataset.

#### How do I control which email addresses get collected?

✅ Use `customDomains`. The actor filters extracted email-like strings so only addresses that match the domains you provide are included in results (for example `@gmail.com`).

#### What does the `platform` input do?

✅ The actor includes a `platform` selector, currently set to `Patreon`. It’s used to keep the run explicitly scoped to Patreon-based data harvesting.

#### Do you support proxies?

✅ Yes. You can pass `proxyConfiguration` to control proxy behavior. The actor also supports fallback behavior when a keyword run returns no emails.

#### What fields will I get in the output dataset?

✅ Each output record includes `keyword`, `title`, `description`, `url`, and `email`. These fields provide both the extracted email and contextual details from the result item where it was found.

#### Is this suitable for Patreon email list builder and outreach use?

✅ It’s designed for list-building workflows like *Patreon subscriber email extractor* and *Patreon outreach email scraper* use cases, where you want structured JSON output that can be imported into downstream tools.

#### Are there any legal or compliance considerations?

✅ Yes. The actor works with **publicly accessible sources**, but it’s your responsibility to comply with applicable laws and platform policies (including GDPR/CCPA considerations, spam regulations, and website terms).

#### Can I request data removal?

✅ If you need data removal related to results, contact <dataforleads@gmail.com>.

***

### Support & feature requests

If you’re using **Patreon Email Scraper** for lead generation or research, feedback is always welcome. 💡

- 💡 **Feature Requests**: Want enhancements like additional export formats, more filtering options, or better output enrichment for your *Patreon email list builder* workflow? Tell us what you need.
- 📧 **Contact**: Reach out at <dataforleads@gmail.com>.

Your feedback helps shape the roadmap for improving this **Patreon Email Scraper**.

***

### Closing CTA / Final thoughts

*Get the most comprehensive Patreon email scraping workflow for your next outreach or research batch—built for speed, clarity, and structured results.*\
**Patreon Email Scraper** is your go-to option for scrape Patreon emails without manual copy-pasting. 🚀

***

### Disclaimer

**This tool accesses publicly accessible sources only.** It does not access private profiles, authenticated data, or password-protected pages.

You are responsible for ensuring your use complies with applicable laws and regulations (including GDPR/CCPA where relevant), spam regulations, and platform terms of service. Please use the **Patreon Email Scraper** responsibly, ethically, and for legitimate purposes only.

For data removal requests, contact <dataforleads@gmail.com>.

# Actor input Schema

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

A list of keywords to search for.

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

Location to filter search results.

## `platform` (type: `string`):

Select platform.

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

List of custom email domains

## `proxyConfiguration` (type: `object`):

Configure proxies for this Actor.

## Actor input object example

```json
{
  "keywords": [
    "john",
    "marketing"
  ],
  "location": "",
  "platform": "Patreon",
  "customDomains": [
    "@gmail.com"
  ]
}
```

# 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": [
        "john",
        "marketing"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("solid-scraper/patreon-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": [
        "john",
        "marketing",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,solid-scraper/patreon-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/ms8HT2dim3sqCD0Qp/builds/NyWCML5j1uUGeSPYf/openapi.json