Meetup
SchedulingRead Meetup data inside agent workflows: look up your member profile and groups, list a group's upcoming events, retrieve full event details, and reach any other field via raw GraphQL queries.
What This Integration Enables
Community programs run on attention, and attention does not scale by adding browser tabs. Whether you run a developer relations program across a dozen city groups or track the ecosystem events your team should show up to, the work is the same: watch groups, notice new events, track RSVP momentum, and get details into calendars and reports. This connector puts Meetup's GraphQL API inside FlowRunner flows, with dedicated actions for the common reads and a raw query escape hatch for everything else the schema exposes. - Sync upcoming events per group into sheets, calendars, and CRM records - Alert channels when a group publishes a new event - Track going counts over time for capacity and momentum reporting - Enumerate a member's groups and iterate across all of them - Reach any other GraphQL field or operation via raw queries Community work resists dashboards because the value lives in timing: the event you promote this week fills, the same promotion next week apologizes. That is why the right architecture is a watching agent rather than a weekly report. FlowRunner agents hold the vigil across every group at once, surface the moments that reward action while they are still actionable, and route them to the person who owns the relationship. The [human-in-the-loop](/concepts/human-in-the-loop) boundary keeps the division clean: agents never speak to the community, and the community manager never has to refresh eight group pages to know what is happening.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The devrel calendar that maintains itself
The developer relations team sponsors groups in eight cities. A nightly agent walks List My Groups, pulls each group's upcoming events with List Group Events, and creates or updates entries in [Google Calendar](/integrations/google-calendar) via Get Event details, venue and start time included. New events post to [Slack](/integrations/slack) tagged by city. When the Berlin group publishes its quarterly event, the team knows at breakfast, and travel planning starts three weeks earlier than it used to.
RSVP momentum as a spreadsheet, not a feeling
Every morning an agent logs each tracked event's going count to [Google Sheets](/integrations/google-sheets). The resulting curves tell the community manager which events are filling fast enough to need a bigger room and which need a promotion push this week, not the day before. When an event's count jumps past the venue's capacity threshold, the flow flags it immediately with the event URL and the trend attached.
The ecosystem watch beyond the dedicated actions
The team wants fields the standard actions do not surface. Run GraphQL Query sends the exact document: upcoming events across a set of topics with fee information and host details, or a group's membership stats pulled with the metadata the schema exposes. Results land in the weekly ecosystem report alongside the tracked-group digest. When Meetup ships new GraphQL fields, the flow uses them the same day, no connector update required.
Human-in-Loop Highlight
Run GraphQL Query is the one action on this page that can change things, because it executes mutations as readily as queries against api.meetup.com/gql. Every dedicated action here is a read; the escape hatch is where an agent could announce, edit, or cancel through whatever mutations the token's permissions allow, in front of a community of real members who chose to trust the group. A cancellation notice or a botched event edit reaches every RSVP instantly and reads as the organizer speaking. So FlowRunner flows split the escape hatch by verb: query documents run freely in reporting flows, while any document containing a mutation stops for the community manager, who sees the exact GraphQL and its variables before it executes. The same discipline covers the downstream sends built on this connector's reads: the agent that drafts the venue-and-RSVP email from Get Event hands it to a person before it reaches members' inboxes. Watching the community is automated. Speaking to it is not.
Agent Capabilities
6 actionsAccount
1- Get Self Retrieves the authenticated member's profile: id, name, and email. The connection check that confirms the token is valid and identifies which member the flows act as.
Groups
2- Get Group Retrieves a group by its URL name, the slug from its meetup.com address, returning id, name, description, member count, and public metadata. The enrichment step for group-level reporting.
- List My Groups Lists the groups the authenticated member belongs to, with id, name, and URL name. The iteration root for flows that watch a whole portfolio of groups.
Events
2- List Group Events Lists a group's events by URL name, filtered by status: upcoming, past, cancelled, or draft. Returns id, title, start time, event URL, and going count. The backbone of digests and RSVP tracking.
- Get Event Retrieves one event's full details by numeric id: title, description, start time, venue location, and current going count. The detail pull behind calendar entries and outreach drafts.
Advanced
1- Run GraphQL Query Executes an arbitrary GraphQL query or mutation with variables against Meetup's endpoint. The escape hatch for fields and operations the dedicated actions do not cover, and the operation this page's human gate governs whenever the document mutates.
Frequently Asked Questions
What can FlowRunner do with Meetup?
FlowRunner agents can run Get Self, Get Group, and List Group Events in Meetup, plus 3 more actions.
Does connecting Meetup to FlowRunner require OAuth?
No. Meetup connects to FlowRunner with an API key, no OAuth flow required.
Can Meetup trigger a FlowRunner workflow automatically?
Meetup doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Meetup
$100 in credits. No card required. Connect in minutes.