Meetup Scraper — Events, Groups & Organizer Leads

Extract complete Meetup.com data — events (start/end times, venue geo, going/waitlist RSVP counts, ticket price, hosts and topics), the groups behind them (member counts, category, founded date, organizer), and every organizer as a ready-to-contact B2B lead with a lead score. Search by keyword + city, scrape a group or event URL, or run monitor mode for only newly listed items.

No login, no cookies — fast JSON straight from Meetup's own internal API.

Why this Meetup scraper?

Most Meetup scrapers only parse the public event card and return null for the fields that actually matter. This actor reads Meetup's internal API directly and ships events plus the groups and organizers behind them — one clean table per entity, no empty columns.

Data	Typical scrapers	This actor
Event title, date/time, URL	✅	✅
In-person vs online + exact venue geo (lat/lng, address)	partial	✅
Going / waitlist RSVP counts	❌	✅
Ticket price & currency (free vs paid)	❌	✅
Full description, topics/tags	partial	✅
Event hosts (B2B leads) + speaker details	❌	✅
Group profile: member count, category, founded date	❌	✅
Organizer leads with profile, bio, location & lead score	❌	✅
Search by keyword + any city, or scrape a group/event URL	partial	✅
Monitor mode — only new items since last run	❌	✅

Use cases

• Lead generation — Meetup organizers run communities of hundreds to tens of thousands of members and buy venues, catering, AV, sponsorship and tools. Score them by audience size and number of groups run, then reach them via their profile.
• Event discovery & aggregation — feed calendars, newsletters and apps with structured Meetup data (date, venue, price, RSVP counts) for any city.
• Community & market research — track which topics draw crowds, which groups are growing, and who is hosting, across an entire city or category.
• Sponsorship & partnership prospecting — find active groups by topic, audience size and city, then pitch the organizer with verified context.
• Recruiting & sales intelligence — use topics, group categories and RSVP counts as in-market intent signals.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the Meetup Scraper, fill in the inputs you need, and click Start.
3. Watch results stream into the dataset table as each record is parsed.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
    "outputType": "all",
    "searchQueries": ["ai", "startup networking"],
    "locations": ["New York, NY", "Austin, TX"],
    "eventType": "any",
    "minAttendees": 10,
    "enrichEvents": true,
    "includeOrganizerLeads": true,
    "maxResults": 200
}

• outputType (default events) — events, groups, organizers, or all. A single type gives one clean, fully-populated table; all returns events + their groups + organizer leads together, each row tagged with a type.
• searchQueries — keywords to search Meetup for; each is combined with every location. Leave empty to browse a location with no keyword filter.
• locations — cities as free text (New York, NY, Austin, TX, San Francisco, London); resolved to coordinates automatically. Use online for online-only events.
• eventType (default any) — physical (in-person only) or online.
• dateFrom / dateTo — only events starting in this window (YYYY-MM-DD); defaults to upcoming events only.
• minAttendees (default 0) — only events with at least this many RSVPs; handy to skip tiny events when prospecting.
• radiusMiles (default 0) — search radius around each location (0 = Meetup's default).
• groupUrls / eventUrls / startUrls — scrape specific groups or events directly; accepts full URLs or bare urlnames/IDs (startUrls auto-detects and routes a mixed list).
• enrichEvents (default true) — open each event for hosts, topics, exact RSVP counts, full description, precise venue geo, price and speaker. Turn off for a faster, lighter run.
• includeOrganizerLeads (default true) — when scraping groups, emit one organizer-lead record per group.
• includeGroupEvents (default false) — also pull each group's upcoming events.
• maxResults (default 200) — cap on records output across the whole run (0 = no limit); keeps runs predictable.
• maxConcurrency (default 6) — maximum parallel API calls.
• proxyConfiguration — proxy settings; Apify Proxy datacenter (the default) works well for Meetup.

Output

By default you get one clean, dense table of events — every column applies to every row. Set outputType to groups or organizers for those tables, or all to combine everything (each row tagged with a type of event, group, or organizer).

An event record (type: "event"):

{
    "type": "event",
    "eventId": "314911336",
    "title": "ACM/IEEE Austin: June Tech Talks & Community Showcase",
    "eventUrl": "https://www.meetup.com/acm-austin/events/314911336/",
    "status": "active",
    "eventType": "physical",
    "isOnline": false,
    "dateTime": "2026-06-24T18:00:00-05:00",
    "endTime": "2026-06-24T20:00:00-05:00",
    "durationMinutes": 120,
    "description": "An evening of deep technical talks across AI, cloud-native systems and security…",
    "goingCount": 48,
    "waitlistCount": 0,
    "isFree": true,
    "feePrice": null,
    "feeCurrency": null,
    "topics": ["Artificial Intelligence", "Machine Learning", "Software Architecture"],
    "venueName": "CGCS, ACC Rio Campus Build #3000",
    "venueAddress": "1218 West Ave Bldg #3000",
    "city": "Austin",
    "state": "TX",
    "postalCode": "78701",
    "country": "US",
    "latitude": 30.277336,
    "longitude": -97.74849,
    "hostNames": ["Akshay Mittal"],
    "hostCount": 1,
    "groupId": "38035397",
    "groupName": "ACM Austin | Enterprise AI & Engineering",
    "groupUrlname": "acm-austin",
    "groupUrl": "https://www.meetup.com/acm-austin",
    "groupMembers": 1450,
    "timezone": "America/Chicago",
    "searchQuery": "ai",
    "searchLocation": "Austin, TX, USA",
    "scrapedAt": "2026-06-12T17:16:42.193Z"
}

A group record (type: "group") carries name, memberCount, category, topics, foundedDate, city/state/country, upcomingEventCount, the organizer* fields and a leadScore. An organizer record (type: "organizer") carries the organizer's name, bio, profileUrl, location, groupsRun, the group they run, isProOrganizer and a leadScore.

Meetup is organizer-entered data, so some fields are populated only when the organizer filled them in — a blank feePrice (free events), missing description or empty bio means the organizer didn't publish it, not that scraping failed. Nothing is dropped, and empty results are reported as success. Personal emails are not published by Meetup, so they aren't included.

Monitoring — get only new items

Turn on onlyNewItems to make every run output only events/groups you haven't received before. It remembers what it has delivered in a persistent store, so it pairs perfectly with Apify Schedules:

• Create a Schedule (e.g. daily) for your keyword + city, keep monitor mode on, and each run hands you just the newly listed items — ideal for newsletters, lead pipelines and Slack alerts.
• Monitor mode is a per-run "new items only" filter — it works alongside the Apify scheduler and never replaces or interferes with it.
• Use a different monitorStateKey per saved search so each schedule tracks its own "already seen" list independently.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it on a cron to keep your data fresh.
• Webhooks — trigger downstream actions the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/meetup-scraper').call({
    outputType: 'all',
    searchQueries: ['ai'],
    locations: ['Austin, TX'],
    enrichEvents: true,
    includeOrganizerLeads: true,
    maxResults: 200,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new records straight into your CRM or sheet.
• Slack — get notified when a run finds something new.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find AI meetups in Austin next month with their organizers" and let it run this scraper for you.

More scrapers from scrapesage

Build a complete event intelligence & lead-gen stack — scrape events, speakers, exhibitors and organizers across every major platform:

• Eventbrite Scraper — events plus organizer leads with contacts.
• Sched Conference Scraper — conference speakers, sessions, sponsors & leads.
• Whova Event Scraper — event sessions, speakers, sponsors & exhibitors.
• Swapcard Exhibitor Scraper — event exhibitors, speakers & contacts.
• Bark Listing Scraper — Bark.com service-provider directory listings.
• SAM.gov Scraper — US federal contract opportunities & contacts.
• Facebook Ad Library Scraper — competitor ad intelligence on Meta & Instagram.
• Google Ads Transparency Scraper — who's advertising what on Google.

Tips

• Pick a single outputType (Events / Groups / Organizer leads) for a clean, fully-populated table that's perfect for direct export. Use all when you want events plus the groups and organizers behind them in one dataset.
• Organizer leads: run with outputType: "all" or groups and keep includeOrganizerLeads on — it turns every group into a contactable community owner with a lead score.
• Prospecting filter: set minAttendees (e.g. 25+) to skip tiny events and focus on active, established groups.
• Big cities: split runs by keyword and/or dateFrom/dateTo windows to exhaust a large metro, and use maxResults to keep test runs cheap.
• Recurring monitoring: combine Schedules with onlyNewItems (and a distinct monitorStateKey per search) to capture only newly listed items each day.

FAQ

How do I scrape Meetup events for a specific city? Put the city in locations as plain text (Austin, TX, New York, NY, San Francisco) and add keywords in searchQueries. The city is resolved to coordinates automatically.

Does it need the Meetup API or a key? No. This actor reads the public data from Meetup's internal API that powers meetup.com — no key or login needed.

Can I scrape a single group or event? Yes — paste its URL into groupUrls or eventUrls (or a mixed list in startUrls). You can also pull a group's upcoming events with includeGroupEvents.

How do I get only new events on a schedule? Turn on monitor mode (onlyNewItems) and create a Schedule. Each run returns only items it hasn't delivered before, and it works alongside the scheduler.

Where do organizer leads come from? From each group's public organizer profile on Meetup (name, bio, location, how many groups they run). Personal emails are not published by Meetup, so they aren't included.

A field is empty — why? Some events don't publish a price (free events), some groups don't list a description, and some organizers didn't write a bio. Fields are blank only when the organizer didn't publish that data — never because the scraper skipped it.

Is scraping Meetup legal? This actor collects publicly available data only. You're responsible for using the data in compliance with applicable laws (e.g. GDPR/CCPA for personal data) and Meetup's terms.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.