You can send a wallet push straight from a CRM automation - when a customer earns points, books a table, or hits any condition your flow can detect. It's the same push as a manual notification, just fired by your CRM instead of by you clicking send.
The request
Every provider does the same thing: a webhook step that POSTs to PocketPass.
POST https://<your-domain>/api/v1/passes/notify
Authorization: Bearer pk_live_YOUR_API_KEY
Content-Type: application/json
{
"id": "<pass-id merge tag>",
"message": "Your points were updated"
}
Create the API key first at /dashboard/settings/api-keys - see API authentication for how keys work and how to keep them safe. The id is the customer's PocketPass pass ID, supplied as a merge tag so it resolves per contact when the flow runs. The message is the text that appears on their locked device.
The pass-ID merge tag per provider
The only thing that changes between providers is the merge tag you put in id.
Klaviyo - {{ person.PocketPassID }}, sent from a Webhook action in a Flow.
Mailchimp - *|PPID|*, sent from a webhook step in an automation.
Me&u Connect - {{contact.pocketpassId}}.
The exact endpoint URL, header, and body are copy-pasteable in the dashboard. Go to Notifications → New notification → (your CRM) and it shows the request pre-filled for your domain and your CRM's merge tag.
It only fires for installed passes
A push has to land on a device that holds the pass, so this only works for customers who have installed theirs - they're the ones who have a PocketPass ID to send. Contacts who never added their pass have no ID, so the merge tag is empty and nothing sends. That's expected, not an error.
If you want those customers to receive pushes, get them to install first - see Turn customers into passes for adding install buttons to your emails.
Guard the trigger so it only runs for contacts who hold a pass. A flow that POSTs for every contact will make a lot of empty-ID calls that do nothing. Where your CRM allows it, gate the webhook step on the "installed" flag PocketPass writes back.
Same push, different trigger
What arrives on the device is identical to a manual notification sent from /dashboard/notifications - a live wallet update with your message. The difference is only what fires it: your CRM's logic instead of a person. Everything else - delivery, how it shows on the lock screen, who can receive it - is the same.
Because it's the same push, the audience rules still apply per pass: one call updates one customer's pass. To message a whole group at once, use a notification with an audience instead.
Where to go next
- Sending a notification - the manual version of the same push.
- Choosing an audience - targeting a group rather than one pass.
- API authentication - creating and securing the key.