PocketPass connects to the tools you already use to reach customers. There are three ways in: your customer list, Zapier, and your own software.
Start where the effort is lowest. If your customers already live in a CRM, connect it - that unlocks the most with the least work.
Connect your CRM
PocketPass connects to one customer list at a time: Klaviyo, Mailchimp, or Me&u Connect. You pick one on the Integrations hub.
Connecting a CRM is the fast path to passes at scale. It gives you:
- A Customers directory at /dashboard/customers, populated from your contacts.
- Passes created from customer records - each contact gets a personal install link, and the pass is created the moment they click it (nothing is issued for people who never install).
- Personalised passes - bind template fields to a customer's data so their name, tier, or balance is already filled in.
- Writeback - PocketPass writes the install link, the Apple and Google Wallet links, and an "installed" flag back onto each contact, so your CRM shows exactly who is holding a pass.
Pick your provider:
Then read Passes from your CRM for how enrollment works end to end.
HubSpot is coming soon. You'll see it on the Integrations hub, but it can't be connected yet.
Zapier
Zapier connects PocketPass to thousands of apps with no code, and it's available today. Describe the automation in a sentence - "when someone installs a pass, post in Slack" - and you can usually build it in minutes.
Triggers (things that start a Zap):
- New Pass Created
- Pass Installed
- Pass Updated
- Pass Removed
Actions (things a Zap does):
- Create or Update Pass
- Update Pass Fields
- Send Push Notification
- Deactivate Pass
- Find Pass by External ID
See Zapier to connect your account and build a first Zap.
Your own software
Everything in the dashboard is backed by a public REST API and outbound webhooks - the same ones Zapier runs on.
- REST API - create and update passes, send notifications, and manage templates programmatically.
- Webhooks - get notified when a pass is created, installed, updated, or removed, so your systems can react in real time.
If a Zap outgrows what it can express, drop down to the API - same events, no migration.
Which should I use?
These aren't exclusive. Connect a CRM for the customer list and writeback, use Zapier to glue in the odd app, and reach for the API when you need control. A CRM connection plus webhooks covers most teams without a line of code.