How automations work

Last updated: October 8, 2026

3-minute video tutorial

Automations connect something that happens outside WalletPassBuilder - a form submission, a payment, a booking - to something that should happen inside it, like creating a pass and emailing it. Every automation is a visual flow: a trigger, then any number of conditions and actions.

The trigger

Every automation starts from a trigger. Pick a preset for the tool you use - Jotform, Typeform, Stripe Checkout, Square or WooCommerce - or a Custom event for anything else.

Click the event name on the trigger to open Edit event. It shows the automation's own webhook URL: paste it into your tool's webhook settings and each request it sends runs this automation, with what it sends available as event.data. No API key or relay (like Zapier) is needed. Click Listen for a test request, then submit your form or make a test purchase, to see every field that arrives - copy a field's path into any step, or save the request as test data.

For Stripe, Square, Typeform and WooCommerce, also paste in the tool's signing secret. Then only requests that tool really signed run the automation, so someone who learns the URL can't fake an event. Keep the URL private either way, and use Regenerate URL if it's ever exposed.

To send events from your own code instead, choose Custom event: Edit event also shows ready-to-copy code (Node.js, Ruby, PHP, Python, Go, Rust and Java) for POST /v1/events with your API key, an event name and a data payload. If other active automations already listen for the same event name, it tells you - one event starts every automation listening for it.

Conditions and actions

Click the + under any step to branch on a condition (true or false, based on a field in the event's data) or add an action:

Create pass - personalize one of your variable passes from the event. Every variable needs a value.

Update pass - choose the fields to change (any field on the pass, as few as one) and set each to a value or an event field.

Email pass - send the pass to someone, with a preview of the pass and Add to Apple Wallet / Google Wallet buttons.

Send notification - message everyone who has already added a pass.

Archive pass, Call webhook and Delay.

Open a step to set it up. A value can be typed as-is, use the event's data with placeholders like {{name}}, or be a field on its own, like event.data.email. A step after Create pass can use createdPass.passId and createdPass.passUrl for the pass it just made.

Emailing a pass

The Email pass card holds who it's from (From name and Reply-to) and who it goes to. Click Edit email template to set the subject, heading, message, link text and accent color, and to turn the pass preview and logo on or off - with a live preview of the email beside the form.

Emails are free to send while this is new - we're not charging pass credits for delivery yet. Texting a pass is coming soon.

Calling your own webhook

Call webhook POSTs JSON to your URL: the triggering event, plus createdPass (the pass's id and link) when a Create pass step ran earlier. The step shows the exact body your endpoint will receive. Every request carries an X-WalletPassBuilder-Signature header (HMAC-SHA256 of the body, using the step's signing secret) so you can confirm it's genuine. Reply with any 2xx within 8 seconds; otherwise it's retried after 1 minute and then 5 minutes. The URL must be a public internet address, and redirects aren't followed.

Testing

Click the play button on the trigger to run the automation once with test data you enter - it's pre-filled with the fields your steps use and remembered for next time. The run plays out on the canvas: each step shows a spinner, then a tick or an error. Hover a result to see what it did, such as the pass link created or who was emailed. Test runs are real: they create passes and send emails, so use your own email address.

Turning it on

An automation only runs while it's Active - click Start in the canvas header once every step is set up. Every run appears on the Runs tab with each step's result and any error message, and the Metrics tab tracks completed, failed and quota-exceeded runs over time.

Was this article helpful?

Still need help?

Our team is here to answer your questions.

Contact us

Be on the lock screen in a few minutes.

Your first pass is quick to make. Pick a template, add your logo, and share the link.