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

Patreon Email Scraper SD - Patreon Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Patreon results by keyword, location and email domain - Patreon email extractor.

- **URL**: https://apify.com/leads-scraper/patreon-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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

### Patreon Email Scraper

### Patreon Email Scraper — extract public creator contact emails from Patreon

The **Patreon Email Scraper** collects publicly indexed business and contact emails belonging to Patreon creators — podcasters, artists, writers, game developers, YouTubers and educators who run a membership page.

You supply keywords, an optional location and a list of email domains. The Patreon Email Scraper builds domain-scoped Google queries against `patreon.com`, parses the search results, and extracts every matching address into a structured dataset.

There is no login, no Patreon API, no headless browser and no cookies. This Patreon email extractor reads only what Google has already indexed publicly.

Sponsorship teams, brand partnership managers, creator-economy tools and agency scouts use the Patreon Email Scraper for contact discovery at a scale that manual browsing cannot match.

***

### Features of the Patreon Email Scraper

Everything listed here is implemented in the Patreon Email Scraper today, with no roadmap items and no aspirational claims.

| Feature | What it means in practice |
|---|---|
| Google `site:` search automation | Every query is scoped to `patreon.com`, so results stay on-platform |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier |
| Creator-tuned modifiers | Defaults include `email`, `contact`, `business inquiries`, `collab`, `booking`, `dm` |
| Domain-filtered extraction | Only emails on your `customDomains` list are kept |
| Global deduplication | Each unique email reaches the dataset exactly once across all queries and pages |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com` |
| Unicode normalisation | Handles zero-width characters and the full-width `＠` sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Discards a hit that is only the tail of another email in the same result block |
| Concurrency control | An `asyncio` worker pool runs queries in parallel with a shared stop signal on `maxEmails` |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, never scored as empty |
| Resumable state | Progress is persisted in the key-value store, keyed by a hash of your input |
| Structural parsing | Result blocks are found via the `<h3>` title, not by Google's CSS class names |
| Fallback parser | A markup change degrades to "emails without account details", not "no emails" |
| Streaming dataset writes | Leads appear in the dataset immediately, so exports can start mid-run |

***

### How the Patreon Email Scraper works

The Patreon Email Scraper is a search-results crawler. It never opens patreon.com and never sees a paywalled post.

**1. Read input.** Keywords, location, email domains, page caps and concurrency are validated.

**2. Build queries.** Queries use the `site:` operator, for example:
`site:patreon.com podcast "@gmail.com" "Los Angeles"`.

**3. Expand queries.** With `expandQueries` on, each keyword × domain pair is issued as a base query, a quoted variant, an `intitle:` variant and one variant per entry in `queryModifiers`. Base queries always run first.

**4. Fetch pages.** The Patreon Email Scraper fetches result pages asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy, using proxy rotation and pagination up to `maxPagesPerQuery`.

**5. Parse result blocks.** The parser locates the `<h3>` title and then the smallest surrounding block, keeping titles, snippets and site labels attached to the correct record.

**6. Extract and normalise emails.** A domain-filtered regex pulls candidates from the block text, normalises them, and removes junk, tails and boundary mismatches.

**7. Deduplicate and store.** The Patreon Email Scraper deduplicates every new email globally and pushes it straight into the Apify dataset as structured data.

The Patreon Email Scraper re-queues blocked or failed queries once at the end of the run, and the run summary logs pages fetched, blocked pages, retries and emails per page.

***

### What data does the Patreon Email Scraper extract?

Every row the Patreon Email Scraper writes is a single email paired with the account metadata Google exposed alongside it.

You receive the address, the matched domain, the account label, a parsed creator name, a handle and profile URL where Patreon exposes one, a cleaned page-description snippet, and full provenance.

Provenance is the underrated part. The `keyword` and `query` fields tell you which niche phrasing surfaced this creator, which is exactly what you need to tune the next lead-generation run.

***

### Input schema

Every Patreon Email Scraper input field is listed below with the exact name, type and default taken from the Actor input schema.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["creator", "artist"]` | Search terms describing the Patreon accounts you want (niche, job title, industry) |
| `location` | string | `""` | Optional location phrase added to every query, e.g. `"New York"` |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails ending with one of these domains are collected; leading `@` optional |
| `maxEmails` | integer 1–10000 | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (US, GB, DE…). Empty for any |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair with several phrasings |
| `queryModifiers` | array | `["email", "contact", "business inquiries", "collab", "booking", "dm"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1–50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1–20 | `5` | How many queries run in parallel |

#### Input example for the Patreon Email Scraper

```json
{
  "keywords": ["true crime podcast", "indie game developer", "webcomic artist"],
  "location": "",
  "customDomains": ["@gmail.com", "@protonmail.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business inquiries", "collab", "booking", "dm"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output schema

Every dataset item produced by the Patreon Email Scraper carries all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when Patreon exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct Patreon link when exposed, else the profile URL |
| `description` | Page or bio snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, e.g. `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

#### Output example

```json
{
  "network": "Patreon",
  "keyword": "true crime podcast",
  "query": "site:patreon.com true crime podcast \"@gmail.com\" business inquiries",
  "title": "Coldfile Podcast | creating true crime episodes | Patreon",
  "accountName": "coldfilepodcast",
  "fullName": "Coldfile Podcast",
  "username": "coldfilepodcast",
  "profileUrl": "https://www.patreon.com/coldfilepodcast",
  "url": "https://www.patreon.com/coldfilepodcast",
  "description": "Weekly investigative true crime episodes, early access and bonus files. Business inquiries: coldfile.pod@gmail.com",
  "email": "coldfile.pod@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T10:02:47.884Z"
}
```

The Patreon Email Scraper dataset exports as JSON, CSV, Excel or XML from the Apify console, or streams through the Apify API into your CRM, ATS or outreach tool.

***

### How to use the Patreon Email Scraper

**Step 1 — describe the membership niche, not the person.** Patreon page titles read like `creating weekly D&D actual play`. Keywords such as `actual play`, `ASMR`, `knitting patterns` or `historical fiction` match that language.

**Step 2 — pick sensible email domains.** Independent creators publish `@gmail.com` far more than anything else. Add others only when you have a reason.

**Step 3 — start small.** Run with `maxEmails` at 20–50 to confirm the keywords surface the right creator tier, then scale up.

**Step 4 — keep the creator-tuned modifiers.** `business inquiries`, `collab` and `booking` are the phrases sponsorship-friendly creators actually put on their pages.

**Step 5 — add `location` only when geography matters.** Many Patreon pages never mention a city, so a location phrase can shrink recall sharply.

**Step 6 - clean before you send.** Filter out rows where `possiblyTruncated` is `true`, then put the remaining Patreon Email Scraper results through your normal email-verification step before any outreach.

***

### Use cases for the Patreon Email Scraper

| Use case | Who runs it | Typical keywords |
|---|---|---|
| Brand sponsorship prospecting | Brand partnership and influencer teams | `podcast`, `youtube channel`, `fitness coach` |
| Creator-economy SaaS sales | Founders selling tools to creators | `newsletter`, `illustrator`, `game developer` |
| Podcast network recruiting | Network scouts and producers | `true crime podcast`, `history podcast`, `interview show` |
| Merch and print-on-demand partnerships | Merch platforms and suppliers | `webcomic artist`, `streamer`, `musician` |
| Collaboration and guest booking | Other creators and community managers | `writer`, `voice actor`, `animator` |
| Talent management scouting | Creator managers and agencies | `artist`, `creator`, `educator` |
| Market research on membership niches | Analysts studying the creator economy | any niche keyword, varied by `location` |
| Grant and residency outreach | Arts organisations and funds | `poet`, `documentary`, `printmaking` |

Patreon is a membership platform, so the population it surfaces skews toward creators who already monetise directly — a materially better sponsorship prospect list than raw follower counts elsewhere.

For creators whose primary surface is video or short-form, pair the Patreon Email Scraper with the [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper) or the [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper). Newsletter-first creators are better covered by the [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper).

***

### Why use this Patreon Email Scraper

Finding creator contacts by hand means searching, opening a page, scrolling the about section, copying an address and repeating. The Patreon Email Scraper automates that loop and hands back a deduplicated dataset.

Every row is auditable. The `query` and `keyword` fields show exactly how a lead was found, which makes it easy to prune keyword sets that produce noise.

The extraction layer is deliberately conservative. Junk filtering, boundary-correct domain matching and soft-wrap repair mean fewer garbage rows to clean up downstream.

Long Patreon Email Scraper runs also survive interruption: state persists in the key-value store, and saves fire on Apify PERSIST\_STATE, MIGRATING and ABORTING events.

***

### Limitations you should know before running

The Patreon Email Scraper is deliberately transparent about its boundaries. Read these before planning a large data collection run.

**Only publicly indexed emails.** The Patreon Email Scraper returns addresses that already appear in Google's index. Creators who keep contact behind Patreon's messaging will not surface.

**Google's per-query ceiling.** A single query caps out at roughly 300 results. Query expansion exists to work around that ceiling, which is why it defaults to on.

**`possiblyTruncated`.** When Google's snippet ellipsis touches an email, the field is `true` and the address may be incomplete. Verify before sending.

**Apify GOOGLE\_SERP proxy required.** The Patreon Email Scraper cannot run without Apify proxy credentials that include the GOOGLE\_SERP group.

**Free-plan cap.** Running the Patreon Email Scraper on a free Apify plan means results are limited to 100 emails per run. Paid plans are uncapped.

**Handle availability.** `username` and `profileUrl` are populated only when Google's result exposes a Patreon handle. Some rows will have `accountName` and `fullName` but an empty `username` and `profileUrl` — a Google limitation, not a bug.

**No guaranteed volume.** Yield varies with keywords, domains and location. No result count is promised.

The Patreon Email Scraper is not affiliated with, endorsed by or officially supported by Patreon.

***

### Related Actors

Every Actor below runs the same engine as the Patreon Email Scraper, with identical input fields and an identical output schema; only the target platform differs.

| Actor | What it collects |
|---|---|
| [Patreon Email and Phone Number Scraper](https://apify.com/leads-scraper/patreon-email-and-phone-number-scraper) | Emails and phone numbers from Patreon |
| [Patreon Phone Number Scraper](https://apify.com/leads-scraper/patreon-phone-number-scraper) | Public phone numbers from Patreon |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### Worked example: a podcast sponsorship shortlist

You sell a sleep-supplement brand and want 250 independent podcasters open to sponsorship.

Set `keywords` to `["true crime podcast", "history podcast", "comedy podcast"]`, `customDomains` to `["@gmail.com"]`, `countryCode` to `"US"` and `maxEmails` to `250`, leaving `expandQueries` on.

The Patreon Email Scraper issues base, quoted and `intitle:` variants plus one query per modifier, paginating each independently and streaming leads into the dataset as they are found.

Export the Patreon Email Scraper dataset to CSV, filter out `possiblyTruncated` rows, group by `keyword` to see which podcast genre yielded best, and load the rest into your sequencer.

***

### FAQ

#### What is the Patreon Email Scraper?

It is an Apify Actor that extracts publicly indexed contact emails for Patreon creators by running domain-scoped Google searches and parsing the resulting search results.

#### Does the Patreon Email Scraper log into Patreon?

No. The Patreon Email Scraper never logs in, never calls the Patreon API and never opens a browser, so there are no cookies and no authentication anywhere in the pipeline.

#### Can it read paywalled Patreon posts?

No. It only sees what Google has publicly indexed — page titles, descriptions and site labels.

#### Where do the emails come from?

The Patreon Email Scraper reads publicly indexed titles, snippets and site labels, typically bios where the account owner published a contact address themselves.

#### Why is `username` empty on some rows?

Google does not always print a handle in the result. Those rows still carry `accountName` and `fullName`, but `username` is `null` and `profileUrl` is empty.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before contacting anyone.

#### How many emails will one run return?

The Patreon Email Scraper accepts a `maxEmails` value between 1 and 10000, but free Apify plans are capped at 100 emails per run and paid plans are uncapped. Real volume depends on your keywords, domains and location.

#### Is a proxy required?

Yes. The Patreon Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### Should I leave `expandQueries` on?

Almost always. Google returns roughly 300 results per query, and expansion multiplies your reachable surface through base, quoted, `intitle:` and modifier variants.

#### Can I target a specific country?

Yes — set `countryCode` for the search proxy, and optionally add a `location` phrase. Note that many Patreon pages never mention a city.

#### What happens if my run is interrupted or migrated?

The Patreon Email Scraper persists state in the key-value store keyed by a hash of your input, with throttled saves plus saves on PERSIST\_STATE, MIGRATING and ABORTING, so an interrupted run resumes instead of restarting.

#### Can I email everyone in the dataset right away?

Treat the Patreon Email Scraper output as raw lead data. Deduplication is automatic, but verification, consent and compliance with GDPR, CAN-SPAM and Patreon terms of service remain your responsibility.

***

### Leave a review

If the Patreon Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions about the Patreon Email Scraper, bug reports or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

Search terms describing the Patreon accounts you want (niche, job title, industry).

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

Optional location phrase added to every query (e.g. "New York").

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

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

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

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Patreon.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "creator",
    "artist"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Patreon Email Scraper, stored in the run's default dataset.

# 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": [
        "creator",
        "artist"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-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": [
        "creator",
        "artist",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-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": [
    "creator",
    "artist"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ]
}' |
apify call leads-scraper/patreon-email-scraper --silent --output-dataset

```

## MCP server setup

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