Extract public Meetup event listings and event details by URL, keyword, or location.
Use this Actor when you need repeatable public Meetup data for event discovery, community research, lead generation, competitor monitoring, local-market research, or event dashboards. Results can be downloaded as CSV, JSON, Excel, XML, RSS, or used through the Apify Dataset API.
At a glance
- Meetup search and URL input: scrape public Meetup find pages, group pages, event pages, keywords, and locations.
- Event details: save titles, dates, descriptions, venues, online flags, groups, organizers, images, RSVP counts, and event URLs.
- Keyword and location workflows: build search URLs from
keywordsandlocationwhen you do not have a Meetup URL yet. - Detail enrichment: open event pages for richer public fields when
includeDetails=true. - Monitoring ready: schedule recurring event searches and export new rows to spreadsheets, CRMs, or alerts.
What can it do?
Meetup Events Scraper turns public Meetup searches and event URLs into structured event rows.
- Export Meetup event data by keyword, location, group URL, find URL, or event URL.
- Collect event and organizer fields such as title, description, start/end dates, online status, venue, group, organizer, images, and RSVP counts.
- Discover local communities around topics, companies, conferences, meetups, and interest groups.
- Build event monitors by scheduling recurring keyword/location searches.
- Use it as a Meetup events API workflow for CSV, JSON, Excel, or direct Dataset API exports.
Common workflows
- Event discovery: find public meetups around a keyword, city, or topic.
- Community research: map active groups, organizers, venues, and event patterns.
- Lead generation: collect event URLs and organizer/group context for outreach.
- Competitive monitoring: track events hosted by competitors, partners, or local communities.
- Local-market research: monitor meetups by city, category, or professional niche.
- Content planning: find events and communities to support newsletter or campaign calendars.
What data can you collect?
Each dataset row represents one public Meetup event.
| Field | Description |
|---|---|
eventId |
Meetup event ID when visible |
eventUrl |
Canonical public event URL |
title |
Event title |
description |
Public event description |
startDate |
Event start date/time |
endDate |
Event end date/time |
timezone |
Date offset when available |
isOnline |
Whether the event is online or mixed |
venueName |
Public venue name |
address |
Public formatted address |
city |
City from public address data |
country |
Country from public address data |
groupName |
Meetup group or organizer name |
groupUrl |
Meetup group URL |
organizerName |
Organizer/group name from public event data |
imageUrl |
Event image URL |
attendanceCount |
Public attendance/capacity when visible |
rsvpCount |
Public RSVP count when visible |
scrapedAt |
Timestamp when the row was saved |
Example input
{
"keywords": ["data"],
"location": "Berlin, Germany",
"maxItems": 25,
"includeDetails": true,
"proxyConfiguration": { "useApifyProxy": false }
}
Example output
{
"eventId": "315065428",
"eventUrl": "https://www.meetup.com/jug-nurnberg/events/315065428/",
"title": "Backend Performance Meetup",
"description": "Public event description...",
"startDate": "2026-06-18T18:00:00+02:00",
"endDate": "2026-06-18T21:00:00+02:00",
"timezone": "+02:00",
"isOnline": true,
"venueName": "Example Office",
"address": "Nurnberg, Germany",
"city": "Nurnberg",
"country": "Germany",
"groupName": "Java User Group Nurnberg",
"groupUrl": "https://www.meetup.com/jug-nurnberg/",
"organizerName": "Java User Group Nurnberg",
"imageUrl": "https://secure-content.meetupstatic.com/...jpg",
"rsvpCount": null,
"scrapedAt": "2026-07-03T12:00:00.000Z"
}
Tips for best results
- Use focused keywords: specific topics produce cleaner event datasets.
- Add a location: city-level searches are usually more useful than global broad keywords.
- Use group URLs for stable monitoring: group event pages change less than general search pages.
- Keep detail enrichment on when quality matters:
includeDetails=trueusually gives richer fields. - Schedule recurring runs: event discovery works well as a weekly monitoring workflow.
Limits and caveats
- The Actor extracts publicly visible Meetup data only.
- It does not access private groups, member lists, attendee-only details, logged-in pages, or messages.
- Event fields vary by group, event type, location, and Meetup page layout.
- Dates, RSVP counts, venues, and availability can change after scraping.
API usage
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~meetup-events-scraper/runs?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"keywords":["data"],"location":"Berlin, Germany","maxItems":25,"includeDetails":true}'
MCP and AI agents
This Actor can be used through the official Apify MCP server at https://mcp.apify.com.
For a focused single-Actor tool setup, use:
https://mcp.apify.com?tools=fetch_cat/meetup-events-scraper
Use the same JSON keys shown in the input configuration table, such as startUrls, keywords, location, maxItems, includeDetails, and proxyConfiguration.
Support
If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.
Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.