> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation.md).
# Automation
Run pass updates and wallet notifications on a schedule or in response to an event, so campaigns continue without manual intervention.
A wallet pass earns attention when it changes at the right moment. Doing that by hand does not scale: a loyalty programme with a hundred thousand passes cannot have someone press a button each time a balance moves, a benefit expires, or an event draws near. Automation covers the mechanisms The Wallet Crew uses to make those changes happen on their own, so that a campaign designed once keeps running.
Real-world examples
* A retailer refreshes the points balance on every loyalty pass overnight, so the figure a customer sees in the morning matches the till.
* A show organiser reminds every ticket holder the day before the event, timed from the event date carried on each pass.
* A brand welcomes a customer with a single message the first time the pass is installed, and never sends it again.
* A membership programme announces renewal a month before the expiry date recorded on the pass.
## What automation covers
Two things happen automatically once a pass is in a wallet. The pass content itself can be refreshed, so that the values printed on the card follow the customer's real state. Separately, a notification can be delivered to the device, so that the customer is told something changed rather than discovering it later.
The two are related but distinct, and it is worth deciding which one a campaign needs. Refreshing a balance without a notification keeps the pass accurate and stays quiet. Sending a notification without a reason to look at the pass spends attention for nothing. Most programmes use both, but not on the same cadence.
Automated work is configured per tenant as scheduled tasks, each pairing an action with a rule that decides when it runs. Some rules repeat on a schedule, some fire once at a set moment, some fire at an offset from a date carried on each individual pass, and some react to something the customer does, such as installing the pass for the first time. A rule that reads a date from the pass can only work if the pass template carries that date as a field.
{% hint style="info" %}
Google Wallet limits pushes to three updates per pass every 24 hours. A refresh cadence tighter than that will not reach the device more often, so plan the schedule around the limit rather than against it.
{% endhint %}
## Pages in this section
* [Push notifications](/guides-animation/engage-and-animate/automatisation/push-notifications.md) compares how Apple Wallet and Google Wallet deliver notifications, what triggers them, and which limits apply.
* [How to send push notifications to Apple and Google Wallet](/guides-animation/engage-and-animate/automatisation/push-notifications/how-to-send-push-notifications-to-apple-and-google-wallet.md) walks through creating, targeting, scheduling and verifying a notification.
* [Consents and GDPR compliance](/guides-animation/engage-and-animate/automatisation/push-notifications/consents-and-gdpr-compliance.md) separates transactional from marketing messages and explains what consent each one needs.
## FAQ
Does refreshing a pass always notify the customer?
No. Updating the data on a pass and alerting the customer are separate decisions. A silent refresh keeps the pass accurate without interrupting anyone, which is the right choice for routine changes such as a points balance moving by a small amount.
What happens to scheduled messages if a customer removes the pass?
A pass that is no longer installed cannot receive a notification. Removal is reported as a wallet event, so a programme that cares about reachable audience size should track installation status rather than assume every issued pass is still in a wallet.
Is consent required before sending a wallet notification?
It depends on what the message does. A message about something the customer already has, such as a ticket time changing, is transactional. A message promoting an offer is marketing and needs the consent the programme collected for that purpose. [Consents and GDPR compliance](/guides-animation/engage-and-animate/automatisation/push-notifications/consents-and-gdpr-compliance.md) sets out the distinction.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.