# Meetup Email Scraper (`leads-scraper/meetup-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/meetup-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

### Meetup Email Scraper — public organiser and group contact emails

The **Meetup Email Scraper** pulls publicly indexed contact emails off `meetup.com` pages and writes them to an Apify dataset, filtered by keyword, location and email domain.

It works through Google's `site:` operator over the Apify GOOGLE_SERP proxy. There is no login, no Meetup API and no browser.

**One thing to understand up front.** Meetup indexes **group and event pages**, not member profiles. So the rows this Actor returns usually identify a **group** rather than a person.

When a handle is present it is normally the group's URL name — the slug in `meetup.com/<group>/` — so `accountName` and `profileUrl` describe a community, not an individual. Plenty of rows carry a real email with `username: null` and `profileUrl: ""` because Google's result exposed no slug at all.

That is exactly what makes the Meetup Email Scraper useful for **community, sponsorship and event outreach**, and a poor fit if you wanted a list of named individuals with personal addresses.

***

### Quick start with the Meetup Email Scraper

1. Open the Meetup Email Scraper on Apify and enter two or three community topics as keywords.
2. Set `location` to the city you care about, and `countryCode` to match it.
3. Add every email domain you are willing to accept to `customDomains`.
4. Start the run and export the dataset as CSV, JSON or Excel.

The Meetup Email Scraper streams rows into the dataset as it finds them, so the first handful tells you whether the topic and city combination is productive.

If nothing comes back, broaden the topic before you broaden the geography.

***

### What the Meetup Email Scraper actually does

The Meetup Email Scraper does **not** log into Meetup, does not use a Meetup API, and does not open the Meetup website. No browser, no JavaScript rendering, no authentication, no cookies.

Every field comes from **publicly indexed Google search results**: the title, the site label and the snippet. Meetup's own tools deliberately hide member email addresses, and this Actor does not touch them.

A generated query looks like `site:meetup.com organizer contact "@gmail.com" "Berlin"`. Result pages are fetched asynchronously with `aiohttp` through the search proxy.

The Meetup Email Scraper locates each result block **structurally** — it finds the `<h3>` title and then the smallest surrounding block — instead of depending on Google's CSS class names.

***

### Key features of the Meetup Email Scraper

| Feature | What it means in practice |
|---|---|
| Google `site:` targeting | Every query is scoped to `meetup.com` |
| Location targeting | The `location` phrase is appended to every query — the single most valuable input for local groups |
| Query expansion | Base, quoted and `intitle:` phrasings plus one variant per modifier; base queries run first |
| Community modifiers | Defaults include `organizer`, `sponsor` and `partnership` |
| Domain filtering | Only emails on your `customDomains` list survive |
| Global deduplication | Each unique address is pushed to the dataset once |
| Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another address in the same block |
| Async concurrency | `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries | Up to 3 attempts per page, exponential backoff, fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty |
| Re-queue | Blocked or failed queries are retried once at the end of the run |
| Resumable state | Key-value store state keyed by a hash of the input; saves fire on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Whole-page fallback parser | A Google markup change degrades to "emails without account details", not "no emails" |
| Truncation flag | `possiblyTruncated` marks addresses touched by Google's snippet ellipsis |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

***

### How the Meetup Email Scraper works

1. Reads your input: keywords, location, allowed email domains and run limits.
2. Builds Google queries with `site:meetup.com`, one per keyword × domain × phrasing, with the location phrase attached.
3. Fetches result pages through the Apify GOOGLE_SERP proxy.
4. Locates each result block structurally and extracts the title, group label and snippet.
5. Applies the domain-filtered regex, normalisation and junk filtering.
6. Deduplicates globally and pushes each lead to the dataset immediately.

Rows appear while the Meetup Email Scraper is still running, so you can check the first few and abort if the keyword is off target.

***

### Input reference for the Meetup Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["organizer", "networking"]` | Search terms (community topic, group type, industry) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; `@` optional |
| `maxEmails` | integer 1–10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain in several phrasings |
| `queryModifiers` | array | `["email","contact","organizer","sponsor","partnership"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1–50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1–20 | `5` | Parallel queries |

#### Example input

```json
{
  "keywords": ["startup founders", "python developers", "product management"],
  "location": "Berlin",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com"],
  "maxEmails": 150,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "organizer", "sponsor", "partnership"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Setting `location` and `countryCode` together is the strongest configuration for the Meetup Email Scraper, because groups are inherently local.

***

### Output fields from the Meetup Email Scraper

Every dataset item produced by the Meetup Email Scraper has all fourteen fields.

| 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 — on Meetup usually a group name |
| `fullName` | Display name parsed from a profile-style title; empty for event and group titles |
| `username` | URL-safe handle when Meetup exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, e.g. `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output

The first row shows the honest case — an organiser address printed on an event page, with no slug in Google's result.

```json
[
  {
    "network": "Meetup",
    "keyword": "startup founders",
    "query": "site:meetup.com startup founders organizer \"@gmail.com\" \"Berlin\"",
    "title": "Founders Coffee #42 — Berlin | Meetup",
    "accountName": "Meetup",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "... Doors 18:30. Sponsorship and speaker enquiries: berlinfounderscoffee@gmail.com ...",
    "email": "berlinfounderscoffee@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T11:22:07.401Z"
  },
  {
    "network": "Meetup",
    "keyword": "python developers",
    "query": "site:meetup.com intitle:\"python developers\" contact \"@gmail.com\" \"Berlin\"",
    "title": "Berlin Python Developers | Meetup",
    "accountName": "berlin-python-developers",
    "fullName": "",
    "username": "berlin-python-developers",
    "profileUrl": "https://www.meetup.com/berlin-python-developers/",
    "url": "https://www.meetup.com/berlin-python-developers/",
    "description": "Monthly talks for Python developers in Berlin. Talk proposals: bpd.organisers@gmail.com",
    "email": "bpd.organisers@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T11:22:35.118Z"
  }
]
```

Notice that even in the second row the handle is a **group slug**, not a person. That is the normal shape of Meetup Email Scraper output.

***

### Use cases for the Meetup Email Scraper

| Use case | How the Meetup Email Scraper helps |
|---|---|
| Event sponsorship outreach | Group and event pages often print a sponsorship contact address |
| Speaking slot pitches | Snippets frequently name a talk-proposal address |
| Community partnership building | Find adjacent groups in the same city and topic |
| Venue and catering sales | Combine a topic keyword with a `location` phrase |
| Developer relations and evangelism | Map the local groups in your technology's ecosystem |
| Local recruitment marketing | Reach technical communities where your hiring pool gathers |
| Conference audience development | Identify feeder communities before a regional event |
| Market research on a local scene | The `description` snippet summarises what a group does |

Because Meetup Email Scraper rows describe groups, the natural message is a group-level proposal — sponsorship, a speaker, a venue, a partnership — rather than personal cold email. Treat every address as personal data under **GDPR** and equivalent laws: identify yourself, keep it relevant to that community, and honour opt-outs immediately.

If your outreach also covers course creators and educators, the **Outschool Email Scraper** and the [Teachable Email Scraper](https://apify.com/neuro-scraper/teachable-email-scraper) sit in the same family, and the [Linktree Email Scraper](https://apify.com/leads-scraper/linktree-email-scraper) often catches the personal contact page an organiser links from their group.

***

### Getting more out of the Meetup Email Scraper

Always set `location`. Meetup is a local product, and an unlocated Meetup Email Scraper query wastes most of its result budget on the wrong continent.

Use topic keywords, not job titles, in the Meetup Email Scraper. `organizer` on its own is weak; `board games`, `UX research` or `climate tech` finds real groups.

Keep `expandQueries` on. Google caps a single query at roughly 300 results, and the modifier variants are how the Meetup Email Scraper reaches past that.

Widen `customDomains` if Meetup Email Scraper yield is thin. Organisers commonly use a dedicated group Gmail address, but plenty use a business domain instead.

***

### Limitations of the Meetup Email Scraper

- **Meetup indexes group and event pages rather than member profiles, so rows usually identify a group rather than a person.** When a handle exists it is normally a group slug.
- The Meetup Email Scraper only finds addresses that are **publicly visible in Google's index**. Meetup deliberately does not expose member emails, and this Actor does not attempt to reach them.
- Google caps a single query at roughly **300 results** — the reason query expansion exists.
- `username` and `profileUrl` are populated only when Google's result exposes a handle; otherwise they are `null` and empty. That is a Google limitation, not a bug.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the address — verify before sending.
- Requires the **Apify GOOGLE_SERP proxy**. The Meetup Email Scraper cannot run without Apify proxy credentials.
- **Free Apify plans are capped at 100 emails per run.** Paid plans are uncapped.
- Results vary with keywords, domains and location. No volume is guaranteed.

***

### Meetup Email Scraper FAQ

#### How many results should I expect from the Meetup Email Scraper?

No volume is guaranteed. Yield tracks how many groups in your topic and city publish an address on an indexed page — a large city with a busy tech scene produces far more than a niche topic in a small town. Set `maxEmails` as your ceiling and read the actual count as the honest supply.

#### Why are `username` and `profileUrl` often empty?

Because many indexed Meetup results are event pages that expose no group slug in Google's output. Rather than fabricating a URL, the Meetup Email Scraper writes `username: null` and `profileUrl: ""` and keeps the email and snippet.

#### Do I get individual members' email addresses?

No. Meetup hides member contact details by design, and the Meetup Email Scraper only reads publicly indexed pages. What you get is the address a group or event page chose to publish.

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

No. It does not log in, use a Meetup API, or open the Meetup website. It reads Google search results only.

#### How important is the `location` field?

Very. Meetup groups are geographically bound, so `location` plus `countryCode` is the difference between a focused Meetup Email Scraper run and a scattered one.

#### What does `possiblyTruncated` mean?

The Meetup Email Scraper sets that flag when Google's ellipsis cut the snippet where the address was, so the captured string may be incomplete. Verify those rows separately.

#### Do I need Apify proxy credentials?

Yes. The GOOGLE_SERP proxy is required, and the Meetup Email Scraper cannot run without it.

#### Why is `expandQueries` on by default?

Because a single Google query returns about 300 results at most. Expansion adds quoted, `intitle:` and modifier phrasings so the Meetup Email Scraper covers more of the index.

#### Can a run resume after a migration?

Yes. The Meetup Email Scraper keeps state in the key-value store keyed by a hash of your input, with saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.

#### What happens if Google changes its layout?

The Meetup Email Scraper parses structurally with a whole-page fallback, so the run degrades to "emails without account details" rather than returning nothing.

#### Is this compliant with privacy law?

The Meetup Email Scraper reads only public pages, but the addresses are still personal data. Under GDPR and similar regimes you need a lawful basis, clear identification and a working opt-out.

#### Can I export the results?

Yes. The Meetup Email Scraper dataset exports to JSON, CSV, Excel and the other Apify formats, and is reachable through the Apify API.

***

### Related Actors

| Actor | What it collects |
|---|---|
| [Meetup Email and Phone Number Scraper](https://apify.com/neuro-scraper/meetup-email-and-phone-number-scraper) | Emails and phone numbers from Meetup |
| [Meetup Phone Number Scraper](https://apify.com/neuro-scraper/meetup-phone-number-scraper) | Public phone numbers from Meetup |
| [Academia.edu Email Scraper](https://apify.com/neuro-scraper/academia-edu-email-scraper) | Public contact emails from Academia.edu |
| [Buy Me a Coffee Email Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-scraper) | Public contact emails from Buy Me a Coffee |
| [Carrd Email Scraper](https://apify.com/neuro-scraper/carrd-email-scraper) | Public contact emails from Carrd |
| [Domestika Email Scraper](https://apify.com/neuro-scraper/domestika-email-scraper) | Public contact emails from Domestika |
| [edX Email Scraper](https://apify.com/leads-scraper/edx-email-scraper) | Public contact emails from edX |
| [Gumroad Email Scraper](https://apify.com/leads-scraper/gumroad-email-scraper) | Public contact emails from Gumroad |
| [Kaggle Email Scraper](https://apify.com/neuro-scraper/kaggle-email-scraper) | Public contact emails from Kaggle |
| [Kajabi Email Scraper](https://apify.com/neuro-scraper/kajabi-email-scraper) | Public contact emails from Kajabi |
| [Ko-fi Email Scraper](https://apify.com/neuro-scraper/ko-fi-email-scraper) | Public contact emails from Ko-fi |
| [Linktree Email Scraper](https://apify.com/leads-scraper/linktree-email-scraper) | Public contact emails from Linktree |
| [MasterClass Email Scraper](https://apify.com/neuro-scraper/masterclass-email-scraper) | Public contact emails from MasterClass |
| [Pluralsight Email Scraper](https://apify.com/leads-scraper/pluralsight-email-scraper) | Public contact emails from Pluralsight |
| [Preply Email Scraper](https://apify.com/neuro-scraper/preply-email-scraper) | Public contact emails from Preply |
| [ResearchGate Email Scraper](https://apify.com/neuro-scraper/researchgate-email-scraper) | Public contact emails from ResearchGate |
| [Skillshare Email Scraper](https://apify.com/neuro-scraper/skillshare-email-scraper) | Public contact emails from Skillshare |
| [Teachable Email Scraper](https://apify.com/neuro-scraper/teachable-email-scraper) | Public contact emails from Teachable |
| [Udemy Email Scraper](https://apify.com/leads-scraper/udemy-email-scraper) | Public contact emails from Udemy |
| [Academia.edu Email and Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-email-and-phone-number-scraper) | Emails and phone numbers from Academia.edu |
| [Buy Me a Coffee Email and Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-and-phone-number-scraper) | Emails and phone numbers from Buy Me a Coffee |
| [Carrd Email and Phone Number Scraper](https://apify.com/neuro-scraper/carrd-email-and-phone-number-scraper) | Emails and phone numbers from Carrd |
| [Domestika Email and Phone Number Scraper](https://apify.com/neuro-scraper/domestika-email-and-phone-number-scraper) | Emails and phone numbers from Domestika |
| [edX Email and Phone Number Scraper](https://apify.com/neuro-scraper/edx-email-and-phone-number-scraper) | Emails and phone numbers from edX |
| [Gumroad Email and Phone Number Scraper](https://apify.com/leads-scraper/gumroad-email-and-phone-number-scraper) | Emails and phone numbers from Gumroad |
| [Kaggle Email and Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-email-and-phone-number-scraper) | Emails and phone numbers from Kaggle |
| [Kajabi Email and Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-email-and-phone-number-scraper) | Emails and phone numbers from Kajabi |
| [Ko-fi Email and Phone Number Scraper](https://apify.com/neuro-scraper/ko-fi-email-and-phone-number-scraper) | Emails and phone numbers from Ko-fi |
| [Linktree Email and Phone Number Scraper](https://apify.com/leads-scraper/linktree-email-and-phone-number-scraper) | Emails and phone numbers from Linktree |
| [MasterClass Email and Phone Number Scraper](https://apify.com/neuro-scraper/masterclass-email-and-phone-number-scraper) | Emails and phone numbers from MasterClass |
| [Pluralsight Email and Phone Number Scraper](https://apify.com/neuro-scraper/pluralsight-email-and-phone-number-scraper) | Emails and phone numbers from Pluralsight |
| [Preply Email and Phone Number Scraper](https://apify.com/neuro-scraper/preply-email-and-phone-number-scraper) | Emails and phone numbers from Preply |
| [ResearchGate Email and Phone Number Scraper](https://apify.com/neuro-scraper/researchgate-email-and-phone-number-scraper) | Emails and phone numbers from ResearchGate |
| [Skillshare Email and Phone Number Scraper](https://apify.com/neuro-scraper/skillshare-email-and-phone-number-scraper) | Emails and phone numbers from Skillshare |
| [Teachable Email and Phone Number Scraper](https://apify.com/neuro-scraper/teachable-email-and-phone-number-scraper) | Emails and phone numbers from Teachable |
| [Academia.edu Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-phone-number-scraper) | Public phone numbers from Academia.edu |
| [Buy Me a Coffee Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-phone-number-scraper) | Public phone numbers from Buy Me a Coffee |
| [Carrd Phone Number Scraper](https://apify.com/neuro-scraper/carrd-phone-number-scraper) | Public phone numbers from Carrd |
| [Domestika Phone Number Scraper](https://apify.com/neuro-scraper/domestika-phone-number-scraper) | Public phone numbers from Domestika |
| [edX Phone Number Scraper](https://apify.com/neuro-scraper/edx-phone-number-scraper) | Public phone numbers from edX |
| [Gumroad Phone Number Scraper](https://apify.com/leads-scraper/gumroad-phone-number-scraper) | Public phone numbers from Gumroad |
| [Kaggle Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-phone-number-scraper) | Public phone numbers from Kaggle |

### Leave a review

If the Meetup 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, bug reports or a custom build: email **neurodata.apify@gmail.com** with your keywords, location and domain list.

# Actor input Schema

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

Search terms describing the Meetup 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 Meetup.

## `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": [
    "organizer",
    "networking"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "organizer",
    "sponsor",
    "partnership"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Meetup 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": [
        "organizer",
        "networking"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "organizer",
        "sponsor",
        "partnership"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/meetup-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": [
        "organizer",
        "networking",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "organizer",
        "sponsor",
        "partnership",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/meetup-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": [
    "organizer",
    "networking"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "organizer",
    "sponsor",
    "partnership"
  ]
}' |
apify call leads-scraper/meetup-email-scraper --silent --output-dataset

```

## MCP server setup

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