Every Webflow form submission or store order becomes a branded Apple Wallet or Google Wallet pass — issued automatically, straight from your site, no code.
A few ways teams put Webflow 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, choose Webflow as the trigger app, and pick the trigger for a new form submission (or, for a store, a new Ecommerce order). Connect your site and select the specific form, then send a test so Zapier can read a sample submission and learn its fields.
TODO(verify): Confirm the exact Webflow trigger labels for a form submission and for a new Ecommerce order, that you can pick a specific form, and which plan tier exposes each (Ecommerce triggers require a paid site plan). Note that form fields come from the form's own field names.
Add an action step, choose Passmint, and select Create Pass. Pick your template from the dropdown — Zapier loads your templates automatically. Then map Holder Email and Holder Name from the email and name fields on the Webflow submission or order.
In Field Values, map the Webflow fields you want on the pass to your template's field names. The key on the left must exactly match a field defined in your Passmint template, or the value is dropped. Run the Zap with your test submission, open the pass on a phone, then switch to a pmk_live… key and turn it on.
TODO(verify): Confirm, on a real test, the Webflow field names for email and name (form fields carry whatever names you gave them in the Designer) and that the Field Values keys you reference exist in your template.
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.