Passmint
TemplatesDocsPricingBlog
Log inGet started
Passmint

Apple and Google Wallet passes from one API. Built for people who ship.

Product
  • Pass Designer
  • Developers
  • Distribution
  • Analytics
  • Templates
  • Pricing
Developers
  • Documentation
  • API reference
  • Node SDK
  • Webhooks
Company
  • Changelog
  • About
  • Contact
  • Support
  • Security
  • Terms
  • Privacy
Social
  • GitHub
  • X

© 2026 Passmint. Built for indie makers.

Apple Wallet & Google Wallet, one API.

Events & ticketing

Give Meetup RSVPs a wallet pass

Run a recurring community group on Meetup and let every RSVP become a branded Apple/Google Wallet pass for that event — QR included, issued automatically, no code.

Start freeRead the docs →
Apple & Google WalletNo-code via ZapierFree to start
Meetup
New RSVP
via Zapier
Passmint
Create Pass
Event ticket

What you can do

A few ways teams put Meetup and Passmint to work together.

Meetup groups move venues constantly. Add a Find Pass step (by member email) and an Update Pass step on a change: update venue or event_date and Passmint pushes the new spot to the pass already in each member's wallet — no group announcement chase needed.
Add a Zap on Meetup's RSVP-removed or 'not going' trigger with Find Pass (by member email) → Void Pass. The wallet pass goes invalid, so your headcount scan stays accurate.

Set it up

One Zap links the two — live in a few minutes, no code involved.

  • A Passmint account and an API key (pmk_live… or pmk_test…), from Developers → API Keys.
  • A Passmint event-ticket template for the pass you're issuing. Note its field names (e.g. event_name, event_date, venue): they must match the values you map from Meetup.
  • A Zapier account (the free plan is enough to build and test this).
  • A Meetup account that organizes the group you want to issue passes for.

In Zapier, add Passmint as a connected app and paste your API key when prompted. Zapier verifies it against your account immediately, so you'll know the connection works before building the rest of the Zap. Use a pmk_test… key while you're setting things up.

Create a new Zap and choose Meetup as the trigger app. Pick the trigger that fires when a member RSVPs to an event, select your group, and send a test so Zapier can read a sample RSVP and learn the member and event fields.

TODO(verify): Confirm the exact Meetup trigger label for a new RSVP and whether it scopes to a group or a single event. Note the field labels for the member's email and name, and where the event name, date, and venue appear (and whether member email is exposed at all).

Add an action step, choose Passmint, and select Create Pass. Pick your event-ticket template from the dropdown — Zapier loads your templates automatically. Then map Holder Email and Holder Name from the member fields on the Meetup RSVP.

In Field Values, map the event name, date, and venue from the RSVP to your template's field names (e.g. event_name, event_date, venue). The key on the left must exactly match a field defined in your Passmint template, or that value is dropped. Run the Zap with your test RSVP, open the resulting pass on a phone to check the QR scans, then switch to a pmk_live… key and turn it on.

TODO(verify): Confirm, on a real template, that the Field Values keys exist as field names, and confirm which Meetup fields carry the event name, date, and venue — and whether member email is available (Meetup often withholds it).

Questions

The details teams check before switching the Zap on.

Yes. Each pass carries a scannable QR rendered from your template, so any QR scanner or check-in app that reads the value you encode can log arrivals. Pick the QR content (an RSVP reference or member ID) when you build the template.
Yes. The Zap fires per RSVP, so each new RSVP issues a pass for that specific event with its own date and venue. Members who come back every week get a new wallet pass for each session, always showing the right details.
Meetup often withholds member email. The pass is still created — holder email is optional in Passmint — but without it you lose automatic delivery and per-holder analytics, so you'll share the returned pass URL another way (a group message or the event page). Map whatever name field is available so the pass is still personalized.
Zapier is perfect for getting this live today. When your group runs many events a week, you need passes issued the instant someone RSVPs without per-task costs, or you want headcount scans wired into your own tooling, call the Passmint API directly — POST /v1/passes, or the @passmint/node SDK. Same wallet passes, same live updates, full control.

Related integrations

Eventbrite

Turn every Eventbrite registration into an Apple/Google Wallet ticket.

Ticket Tailor

Turn Ticket Tailor orders into Apple & Google Wallet tickets.

Luma

Turn Luma registrations into Apple & Google Wallet tickets.

Issue your first pass from Meetup today

Free for your first passes. No Apple or Google certificates to manage, no code to write.

Start freeExplore the API →