Meetup & Lu.ma Event Finder by City, Group & Calendar

Meetup and Lu.ma host two very different event ecosystems. This actor reads both from one input shape: search by keyword and city, browse a group or calendar, open a specific event URL, or discover what is happening around a city — with pagination, filters, and rich event details.

What this actor does

• One actor, two platforms — set platform to meetup or luma and reuse the same fields
• Eight intent modes — keyword search, event lookup, group profile, group/calendar event lists, nearby discovery, trending discovery, and URL auto-routing
• Full result pages — Meetup cursor pagination and Lu.ma cursor pagination, not just the first page
• Useful filters — dates, event format, radius, minimum attendance, free-only, category, and sort order
• Rich records — venue and coordinates, group size, topics, hosts, prices, ticket tiers, and RSVP/guest counts
• Optional enrichment — Meetup attendee names/photos and Lu.ma event descriptions/ticket tiers/featured guests, both off by default
• Monitoring — onlyNewSinceLastRun remembers IDs for the same input and skips them next time
• Clean data — empty fields are omitted at every depth; no null, "", [], or {}

No login, cookie, API key, or browser is required.

Modes

Mode	Meetup	Lu.ma
searchEvents	Keyword search with location, dates, type, radius, category, attendance	Keyword search, city feed, or category feed
byEvent	Event URL, group/eventId URL, or numeric event ID	Event URL (lu.ma or luma.com), slug, or evt-... ID
byGroup	Group profile and stats	Calendar/community profile
groupEvents	Group's upcoming or past events	Calendar's upcoming or past events
byCalendar	Alias for groupEvents	Calendar profile plus its events
discoverNearby	Recommended events near a location/category	City or nearest featured city feed
discoverTrending	Recommended events by category/location	Featured city/category feeds
byUrl	Auto-routes event and group URLs	Auto-routes event and calendar URLs

Output per Meetup event

• id, name, url — event identity and link
• startAt, endAt, timezone — scheduling (timezone falls back to the group's timezone)
• description — full description from the event payload
• eventType, rsvpState, status, waitlistMode — event state
• imageUrl, imageId — event photo
• guestCount, attendeeCount, waitlistCount, capacity — attendance and capacity
• isFree, feeAmount, feeCurrency, feeAccepts, feeRequired — pricing
• group, groupName, groupUrlname, groupMemberCount, groupCategory — group summary
• venueName, venueAddress, city, state, country, postalCode, latitude, longitude, googleMapsUrl — venue
• topics[] — topic id, name, and urlkey
• hosts[] — host name and photo
• attendees[] — optional public RSVP names/photos when includeAttendees is on (capped at 250)
• seriesId, seriesName — recurring series, when present
• recordType, platform, siteName, scrapedAt — record metadata

Output per Meetup group

• id, name, urlname, url, timezone, description, photoUrl
• foundedDate, city, state, country, latitude, longitude
• memberCount, rating, ratingCount, isNewGroup
• category, categoryId, categoryUrlkey, topics[]
• organizer, socials — organizer profile and linked social accounts
• upcomingEventCount, pastEventCount
• memberSample[] — optional public members when includeMembers is on

Output per Lu.ma event

• id, name, url, slug, startAt, endAt, timezone
• description — full ProseMirror text on detail/enrichment
• imageUrl, eventType, locationType, waitlistActive, hideRsvp
• guestCount, ticketCount, isFree, feeAmount, maxFeeAmount, currency
• ticketTiers[] — tier name, price, currency, type, spots remaining, registration count
• isSoldOut, requireApproval, isNearCapacity, spotsRemaining, registrationAvailability
• venues and location fields — venueName, fullAddress, venueAddress, city, state, country, latitude, longitude
• hosts[], organizerName, featuredGuests[]
• calendar, calendarName — calendar identity, socials, website, and location
• categories[], featuredCity
• recordType, platform, siteName, scrapedAt

Output per Lu.ma calendar

• id, name, slug, url, description
• avatarUrl, coverImageUrl
• instagram, linkedin, twitter, website, socials
• timezone, city, state, country
• eventCount, subscriberCount, upcomingEventCount, pastEventCount
• recordType (calendar or city), platform, siteName, scrapedAt

Output per error record

If a specific URL, slug, or event ID cannot be fetched or parsed, the actor emits an error record rather than silently dropping it:

• recordType — error
• platform, reason, source, httpStatus
• url, slug, eventId, or groupUrlname — the identifier that failed
• scrapedAt

Input

Field	Type	Default	Description
platform	select, required	meetup	meetup or luma
mode	select, required	searchEvents	One of the eight modes above
query	string	–	Keyword; required for Meetup search unless a category is supplied
location	string	–	City or region used to resolve the search area
lat, lng	number	–	Explicit coordinates; bypasses geocoding
country	select	–	Optional Meetup country hint
meetupCategory	select	–	Live Meetup topic category (all plus 20 current topics)
lumaCategory	select	–	Lu.ma category feed (needs a city or coordinates)
eventType	select	any	Meetup: any, physical, online, hybrid
sortBy	select	relevance	relevance, dateAsc, or dateDesc
dateFrom, dateTo	string	–	Inclusive date bounds (YYYY-MM-DD or ISO date-time)
radiusKm	integer	–	Meetup search radius, 1–500 km
minAttendees	integer	–	Minimum RSVPs/guests, 0–100000
freeOnly	boolean	false	Drop events known to charge
eventPeriod	select	upcoming	upcoming, past, or all for group/calendar modes
urls	array	[]	Meetup or Lu.ma event/group/calendar URLs
slugs	array	[]	Meetup group urlnames or Lu.ma slugs
eventIds	array	[]	Numeric Meetup event IDs (alone or paired with slugs) or Lu.ma evt-... ids
lumaCity	select	–	Any of the 87 live Lu.ma featured cities
maxItems	integer	50	Hard cap on records, 1–1000
includeAttendees	boolean	false	Meetup: add public RSVP names/photos
includeMembers	boolean	false	Meetup groups: add a public member sample
enrichDetails	boolean	false	Lu.ma: fetch detail for descriptions, tiers, featured guests
onlyNewSinceLastRun	boolean	false	Skip IDs already emitted for this exact input

Examples

Search Meetup events in a city

{
  "platform": "meetup",
  "mode": "searchEvents",
  "query": "tech",
  "location": "san francisco",
  "dateFrom": "2026-11-01",
  "eventType": "physical",
  "maxItems": 50
}

Browse a Lu.ma city feed with more than one page

{
  "platform": "luma",
  "mode": "discoverNearby",
  "lumaCity": "sf",
  "maxItems": 100
}

Read a Meetup group's past events

{
  "platform": "meetup",
  "mode": "groupEvents",
  "slugs": ["real-time-analytics-and-ai"],
  "eventPeriod": "past",
  "maxItems": 30
}

Auto-route mixed Meetup and Lu.ma URLs

{
  "platform": "meetup",
  "mode": "byUrl",
  "urls": [
    "https://www.meetup.com/real-time-analytics-and-ai/events/316657797/",
    "https://luma.com/fireworks-8kmc"
  ],
  "includeAttendees": true
}

Use cases

• Build a combined Meetup + Lu.ma event feed for a city or topic
• Track a community group's or calendar's upcoming and past schedule
• Research venues, prices, hosts, and attendance before attending
• Monitor new events for a saved search with onlyNewSinceLastRun
• Compare how a topic is represented across both platforms

FAQ

Is this affiliated with Meetup or Lu.ma? No. This is an independent actor that reads publicly available data from both platforms and is not operated by or affiliated with either.

Do I need an account, cookie, or API key? No. Every supported path works anonymously and cookielessly; nothing is required beyond the input fields.

Why does a Lu.ma keyword search stop at 50 results? Lu.ma's public keyword search is capped at 50 results per query. For more coverage, split the keyword into narrower terms or use a city or category feed, which supports cursor pagination.

Can I get past events? Yes for Meetup groups (groupEvents with eventPeriod: "past") and Lu.ma calendars (byCalendar, groupEvents, or eventPeriod). Meetup keyword search and Lu.ma city/category feeds do not expose past events.

Why are Lu.ma attendee names missing? Lu.ma only publishes counts, featured guests, and first-name previews. The full guest list requires a signed-in user with access to the event, so this actor returns counts and featured guests only.

Are Meetup attendee names public? On many events the public RSVP list is visible and can be included with includeAttendees. Some organizers hide it; in that case the field is omitted. Attendee data is opt-in and never part of the small default run.

Why are some prices or venues missing? Hosts can hide prices, and some events are online-only or use an obfuscated address. The actor reports only what the platform discloses; it never invents a price or address.

What happens if a request is blocked? The actor retries politely and, only after a real block, makes one automatic proxy retry. There is no proxy field to configure.

How many records can one run return? Up to maxItems (maximum 1000). Coverage depends on what the platform publishes for the query, city, group, or calendar.