Swap the PDF-in-an-email for a real Apple Wallet or Google Wallet ticket — attendee name, event, date, venue, and a scannable QR for the door — issued automatically the moment someone registers.
A few ways teams put Eventbrite and Passmint to work together.
One Zap links the two — live in a few minutes, no code involved.
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 Eventbrite as the trigger app. Pick the trigger that fires when someone new registers for (or buys a ticket to) your event, connect your Eventbrite account, and select the specific event Passmint should watch. Send a test so Zapier can pull a sample attendee and learn the available fields — name, email, order, ticket type, and the event's date and venue.
TODO(verify): Confirm the exact Eventbrite trigger label for a new registration/attendee and that it lets you scope to a single event. Confirm which fields the sample exposes for attendee name and email vs. event-level name/date/venue, and whether ticket type and order number come through on the attendee record.
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 attendee's email and name on the Eventbrite trigger, so the ticket is delivered to the right person and shows their name.
In Field Values, map the event onto the pass. The key on the left must exactly match a field name in your Passmint event-ticket template (e.g. event_name, event_date, venue, ticket_type, order_number); the value on the right is the matching Eventbrite field — event title, start date/time, venue name, the attendee's ticket type, and their order number. These are what render on the face of the wallet ticket. Anything you don't map is simply left off.
TODO(verify): On a real template, confirm the Field Values keys you reference exist as field names in that event-ticket template (mismatched keys are silently ignored). Confirm the Eventbrite date field's format is one your template renders cleanly, and which Eventbrite field holds the venue.
Create Pass returns a Pass URL — a page where the attendee taps Add to Apple Wallet or Save to Google Wallet. Map that URL into your Eventbrite order confirmation email or attendee email so registering and getting the wallet ticket are one step. The QR/barcode for check-in lives on the pass itself, so there's nothing else to attach.
TODO(verify): Confirm where Eventbrite lets you insert a custom link or merge field into the confirmation/attendee email, or whether you'll send the wallet link via a separate email/SMS Zap step instead.
Run the Zap with your test attendee and check that a ticket is created in Passmint and the Pass URL comes back. Add it to a phone, confirm the name, event, date, and venue read correctly, and scan its QR with your check-in tool to make sure the door flow works end to end. Then switch your API key to pmk_live…, turn the Zap on, and take a real registration for a live run.
The details teams check before switching the Zap on.
Free for your first passes. No Apple or Google certificates to manage, no code to write.