Meetup Events Scraper

Extract public Meetup event data from Meetup search pages, group pages, event URLs, keywords, and locations. The Actor returns event records for event discovery, market research, community monitoring, and local event lead generation.

What you can scrape

• Meetup keyword searches for public events
• Meetup location searches for public events
• Public Meetup group pages
• Public Meetup event detail pages
• Upcoming community events visible on public Meetup pages
• Event pages with organizer, group, venue, date, and attendance signals when available

Who is it for

Meetup Events Scraper is useful for teams that need structured public event data without manually checking Meetup pages.

Common users include:

• Event marketers building lead lists
• Community managers tracking local meetups
• Recruiters monitoring technology and professional events
• Analysts measuring event density by topic or city
• Agencies creating city calendars or campaign lists
• Sales teams looking for relevant public gatherings

Input recipes

Search for data events near Berlin:

{
  "keywords": ["data"],
  "location": "Berlin, Germany",
  "maxItems": 10,
  "includeDetails": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Scrape from a Meetup URL:

{
  "startUrls": [{ "url": "https://www.meetup.com/find/?keywords=data&source=EVENTS" }],
  "maxItems": 10,
  "includeDetails": true
}

Collect a small sample first:

{
  "keywords": ["startup"],
  "location": "New York, NY",
  "maxItems": 5,
  "includeDetails": false
}

Input fields

• startUrls - public Meetup find, group, or event URLs.
• keywords - terms used to build Meetup event searches.
• location - optional Meetup search location, such as Berlin, Germany.
• maxItems - maximum number of event records to save.
• includeDetails - opens event detail pages for richer public fields.
• resumeStartUrls - URLs preserved from a previous checkpoint.
• proxyConfiguration - optional Apify Proxy settings.

Output data

Each dataset item represents one public Meetup event and includes public event fields when available.

Typical fields include:

• eventId
• eventUrl
• title
• description
• startDate
• endDate
• timezone
• isOnline
• venueName
• address
• city
• country
• groupName
• groupUrl
• organizerName
• imageUrl
• attendanceCount
• rsvpCount
• scrapedAt

Example inputs

Use the keyword recipe to monitor event topics in a city, or pass a public Meetup group URL to collect upcoming events for one community. Start with a small maxItems value, inspect the dataset, then increase the limit for larger exports.

API usage

You can run the Actor from the Apify API, Apify client libraries, or Apify Console. Send the same JSON input shown above and read results from the default dataset after the run succeeds.

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/meetup-events-scraper').call({
  keywords: ['data'],
  location: 'Berlin, Germany',
  maxItems: 10,
  includeDetails: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/meetup-events-scraper').call(run_input={
    'keywords': ['data'],
    'location': 'Berlin, Germany',
    'maxItems': 10,
    'includeDetails': True,
})

items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~meetup-events-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"keywords":["data"],"location":"Berlin, Germany","maxItems":10,"includeDetails":true}'

MCP

Use this Actor through Apify integrations or MCP-compatible workflows when you want an agent to collect public Meetup event data and pass the dataset into downstream analysis, enrichment, or notification steps.

Add the Apify MCP server to Claude Desktop or another compatible client, for example:

$claude mcp add apify -- npx -y @apify/actors-mcp-server --actors fetch_cat/meetup-events-scraper

Example MCP configuration:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server", "--actors", "fetch_cat/meetup-events-scraper"],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

Example prompts:

• "Find public Meetup events about data in Berlin and return the titles, URLs, and dates."
• "Collect startup Meetup events in New York and summarize the groups organizing them."
• "Run the Meetup Events Scraper for this public Meetup URL and save the dataset for my next step."

Pricing and limits

The Actor uses pay-per-event pricing with a small start charge and a per-result charge. Set maxItems to control run size and cost. For current rates, open the live Apify Pricing tab: https://apify.com/fetch_cat/meetup-events-scraper/pricing

Data freshness

Results reflect public Meetup pages at run time. Event details can change when organizers update their Meetup event pages.

Proxy guidance

Direct connections often work for small public searches. If Meetup blocks a direct connection, enable Apify Proxy in the input.

Deduplication

When multiple inputs point to the same public event, the Actor keeps one dataset item for that event URL. This helps combine keyword, location, and URL inputs without creating duplicate rows.

Run strategy

For new searches, start with maxItems between 5 and 20. After confirming that the query returns the event type you need, increase maxItems for production exports.

FAQ

Why did I get fewer events than maxItems?

Meetup may show fewer public events for the selected keyword, location, or group than your requested limit.

Can I scrape private Meetup content?

No. This Actor is intended for publicly available Meetup event information only.

Should I enable detail pages?

Use includeDetails: true when you need richer event fields. Use includeDetails: false for faster sampling from search results.

Support

If a run does not return expected public events, include the input and run URL when opening an Apify issue so the problem can be reproduced.

Related actors

Use this Actor with other event, venue, or local-business scrapers when building market maps, community calendars, or lead lists.