Skip to content
Automation

Workflow engine for pass updates after each event

When a pass is installed, scanned, or its balance changes, the workflow engine can create, update, void, retag, or switch the template — through the API, without a separate app.

  • Reacts to install, scan, balance, tier, and consent events
  • Can update, void, reactivate, or retag a pass
  • Runs through the API on your account's data
Works on:
Apple WalletApple WalletGoogle WalletGoogle Wallet
Overview

The workflow engine listens for pass events such as an install, a removal, a scan, a points or balance change, a tier change, or a consent update. A workflow can then create a pass, change its fields, void it, reactivate it, move it to another template, or add and remove tags and segments.

You connect those actions through the API. The engine acts on passes in your account only. It does not run a public no-code canvas in the marketing site, and it does not call external systems on its own beyond the pass actions you configure.

Capabilities

What you launch with in production

01

Event-driven pass actions

Trigger pass create, field update, void, reactivate, template switch, and tag or segment changes from install, scan, balance, tier, and consent events.

02

Bounded retries

Failed workflow runs can retry with a delay and a timeout so a single failed action does not loop forever.

03

Wallet pass API

Create, update, and revoke passes programmatically with a REST API and webhooks for install, update, and redemption events.

04

QR codes and download links

Distribute passes through hosted Add to Wallet pages, QR codes, email delivery, or POS workflows — customers save in one tap, no app required.

05

Wallet-specific pass updates

Update pass data through the API. Apple Wallet may show configured field change messages; Google Wallet controls its built-in notifications.

06

Location relevance

Configure relevant locations for supported wallet features. Availability, display timing, and required permissions depend on the wallet and customer settings.

07

Dates, expiry, and lifecycle

Set relevant dates and expiration, extend validity on scan, and manage the full pass lifecycle from issue to revoke.

08

Analytics and tracking

Track installs, removals, scans, and redemptions per pass and cohort, with CSV and API exports for your own reporting.

FAQ

Frequently asked questions

What can the workflow engine change on a pass?

It can create a pass, update fields, void or reactivate it, switch its template, and add or remove tags and segments when a configured event fires.

Which events can start a workflow?

Install, removal, scan, points update, tier change, balance change, inactivity, and consent opt-in or opt-out.

Does this replace the REST API?

No. The workflow engine runs pass actions inside Passinstance. Your own systems still use the REST API and webhooks when you want to push changes in from outside.

Automate the pass change that follows each event

Start free, then connect workflow actions to the installs, scans, and balance changes you already track.