Meetup Events Scraper

Collect public Meetup event records from search, group, or event URLs, or build searches with keywords and a location. Meetup Events Scraper saves titles, dates, venue details, organizer labels and RSVP counts when available, ready for CSV, Excel or JSON export.

Results depend on what Meetup exposes publicly. Searches can include recommendations outside your requested topic or location. This is not a complete event calendar or an attendee directory.

Quick start

1. Open the input form and choose a public Meetup URL or keyword search.
2. Set a small maxItems limit and start the Actor.
3. Inspect event titles and cities in the dataset, then export the records you need.

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

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Meetup group event calendars from public URLs
• Find public Meetup events by keyword and city

What you get

One event row with its public event URL, available title, date strings, venue information and organizer labels. RSVP counts and capacity signals remain distinct. Optional enrichment can add public descriptions, while missing fields stay null and summary source counts can understate rows saved before a source fails.

Who is it for?

• Community researchers reviewing available events for chosen public searches.
• Calendar editors selecting source-linked events after checking relevance and dates.
• Partnership researchers following public group and organizer references.
• Data teams comparing their own event datasets without claiming complete calendars.

How you can use the data

• Review a small Berlin data-event sample. Use the existing data keyword, Berlin location and five-event cap with details off. Check title and city in the result before selecting events, since Meetup recommendations may fall outside requested topics or places.
• Enrich a useful shortlist deliberately. Enable details for the same small input when descriptions or public venue fields matter. Keep source event URLs and date strings with offsets rather than inventing a named time zone or assuming every optional field is complete.
• Keep supplied URLs' scope separate. Known public search, group and event URLs can be combined with keywords under one cap. Location changes generated keyword searches, not pasted URLs. A group URL does not guarantee a complete calendar.
• Compare and continue work in your own workflow. Join event URLs across retained datasets and inspect source statuses and pending URLs. Submit pending sources as start URLs in a new run, rather than the unused legacy resume field. A failed source count may omit rows already saved, so inspect the dataset itself.

Input settings

Provide startUrls, keywords, or both. Location alone is not a complete input. Combined usable sources must be between 1 and 100.

Setting	API key	Purpose
Start URLs	startUrls	Public Meetup find, group or event URLs.
Keywords	keywords	Terms used to build event search URLs.
Location	location	Location text for keyword searches. Does not alter supplied URLs.
Maximum events	maxItems	Shared result ceiling, 1–10,000. Form default 10. Set it explicitly in API calls.
Open detail pages	includeDetails	Optional public enrichment, enabled by default.
Resume start URLs	resumeStartUrls	Accepted legacy field, currently unused. Submit pending URLs through startUrls instead.
Proxy configuration	proxyConfiguration	Optional connection settings. See field help for behavior and costs.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each saved row describes one event URL. Unavailable values are null. This synthetic shape-only example illustrates the field names, not an observed event:

{
  "eventId": null,
  "eventUrl": "https://www.meetup.com/example-group/events/000000000/",
  "title": null,
  "description": null,
  "startDate": null,
  "endDate": null,
  "timezone": null,
  "isOnline": null,
  "venueName": null,
  "address": null,
  "city": null,
  "country": null,
  "groupName": null,
  "groupUrl": null,
  "organizerName": null,
  "imageUrl": null,
  "attendanceCount": null,
  "rsvpCount": null,
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}

Fields	Meaning
eventId, eventUrl, title, description	Event identity, public URL, name and description. Descriptions can retain markup.
startDate, endDate, timezone	Source date strings and the trailing UTC offset or Z, not a named timezone.
isOnline	True for online or mixed attendance. May be unknown.
venueName, address, city, country	Available public venue details.
groupName, organizerName, groupUrl	Public organizer labels and URL. The two names use the same source value.
imageUrl	First available public image URL.
attendanceCount	Capacity signal: maximum or remaining capacity, not actual attendance.
rsvpCount	Reported RSVP or attendee count when supplied.
scrapedAt	Collection timestamp in UTC.

The run's key-value store also contains RUN_SUMMARY with source statuses, saved counts and pending URLs. It is a diagnostic summary, not an automatic resume checkpoint. If a source fails after saving some events, its source-level count can understate those saved rows. Inspect the dataset itself.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after initial input validation. The result event applies to each saved event row. A failed run can still have its start charge and charges for already saved events, while diagnostic summaries are not result rows.

Begin with a small explicit shared cap and details off when basic records suffice. See the live Pricing tab for current rates and discounts.

Tips for best results

• Set a small explicit cap. It is shared across sources and is not a promised event count.
• Review title and city before using recommendations. Requested keywords and location do not enforce exact relevance.
• Retain original date strings and offsets. The timezone field is an offset or Z rather than a named zone.
• Keep RSVP counts separate from capacity. AttendanceCount does not measure actual attendance.
• Inspect the dataset and source statuses together. Counts can understate records saved before a source failure.

Limits and caveats

Only public Meetup information is supported without login. Private groups, attendee identities, contact lists, ticket purchase and joining events are outside scope. This is an Apify collection workflow rather than official Meetup API access or a complete event calendar.

Supply public URLs, keywords or both, with one to one hundred usable combined sources. Location alone is insufficient. Location affects keyword searches rather than supplied URLs. The shared row cap is a ceiling, not a guaranteed total. Meetup can return recommendations outside requested topics or cities. There is no guaranteed topic enforcement, selectable ordering, date-range filter or exhaustive collection.

Public fields vary, descriptions can retain markup and missing values remain null. The timezone field is a trailing UTC offset or Z rather than a named zone. Organizer and group names use the same source value. AttendanceCount reflects maximum or remaining capacity, not actual attendance, while rsvpCount is the reported RSVP or attendee count when exposed.

Useful rows can remain despite isolated source failures, but a run with no collected events fails. Missing records or failed requests alone do not prove deletion or privacy. A failed run can retain paid saved rows. Duplicate event URLs are suppressed within a run, while a later run can collect them again.

RUN_SUMMARY includes source statuses and pending URLs, but is a diagnostic summary rather than automatic continuation. A source count can understate events saved before that source fails, so inspect the dataset. ResumeStartUrls is an accepted but unused legacy field. Submit pending URLs through startUrls in a new run, and maintain comparisons or alerts in your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~meetup-events-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "keywords": [
    "data"
  ],
  "location": "Berlin, Germany",
  "maxItems": 5,
  "includeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
JSON

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": 5,
  "includeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/meetup-events-scraper').call(run_input={'keywords': ['data'], 'location': 'Berlin, Germany', 'maxItems': 5, 'includeDetails': False, 'proxyConfiguration': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Meetup Events Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Meetup Events Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/meetup-events-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Meetup Events Scraper by Fetch Cat, or give it the identifier fetch_cat/meetup-events-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Meetup Events Scraper to collect up to 5 events for data in Berlin, Germany with details off and direct access. Keep event links, titles and cities, and flag recommendations that do not appear relevant rather than guaranteeing a city-topic match.”
• “Collect up to 5 events for data in Berlin, Germany with details enabled and direct access. Retain original date strings and offsets, available descriptions and venue fields, marking missing values without guessing a time zone.”
• “Retrieve up to 5 events for data in Berlin, Germany with details off and direct access. Keep RSVP counts separate from capacity signals and inspect source statuses and pending URLs without automatically starting a continuation.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export Meetup events to CSV or Excel?

Yes. Open the run's dataset and select CSV, Excel or JSON export. API clients can read the same dataset.

Is this a Meetup events API alternative?

It provides public event records through the Apify API, not official Meetup API access. It cannot access private content or guarantee the same coverage and filters as Meetup's own services.

Why are results unrelated, missing or fewer than requested?

Public availability and Meetup recommendations vary. maxItems is only a ceiling, and topic/location matching is not enforced. Try a specific public event URL when you need one known event, and inspect RUN_SUMMARY for source failures.

Does it collect attendee names or resume a previous run?

No attendee identities are exported. Automatic checkpoint continuation is not implemented. Submit pending source URLs through startUrls for a new run.

Related Actors

• Eventbrite Events Scraper — Discover public Eventbrite events.
• Facebook Events Scraper — Research public Facebook events.
• Luma Events Scraper — Collect public Luma event information.
• AllEvents Events Scraper — Explore another public event source.
• Google Maps Places Scraper — Research venues and nearby places.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥