> 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

Build an automation in the admin console: when it runs, which passes it concerns, what it changes, when it stops, and how to send a notification.

An automation is a rule that updates wallet passes on its own. Once it is switched on, it picks the right passes at the right moment and changes them: a new look for a campaign, a reward, a message on the lock screen. It saves the team from updating thousands of passes by hand, and every customer receives the change at the right time, even customers who install their pass weeks after the campaign started.

<details>

<summary><strong>Real-world examples</strong></summary>

* A fashion brand gives every loyalty card a Black Friday look on launch morning, announces the sale with a notification, and restores the usual look when the campaign ends.
* A beauty brand greets each customer with a welcome message a few minutes after the pass lands in their wallet, and never sends it twice.
* A retailer switches a customer's pass to the Gold look the moment the customer reaches the Gold tier.
* A gift card program reminds holders the day before their card expires.
* A brand moves every pass from an old pass template to a new one, silently, without reissuing a single pass.

</details>

## How an automation is built

Every automation answers the same five questions, always in the same order. The editor shows them as five stacked blocks, so reading an automation from top to bottom is enough to know what it does.

| Block        | Question          | What it holds                                                                                         |
| ------------ | ----------------- | ----------------------------------------------------------------------------------------------------- |
| **Start**    | When does it run? | A date, a repeating schedule, a date carried on each pass, or a customer action.                      |
| **Audience** | Which passes?     | Filters on the pass template, its theme, its data, and whether it is installed.                       |
| **Actions**  | What changes?     | A benefit, new data, a new pass template, a theme, a notification.                                    |
| **End**      | Until when?       | After a single run, on a fixed date, when the benefit template ends, or when someone switches it off. |
| **Settings** | How fast?         | On/off switch, sending pace, and data refresh.                                                        |

From the trigger to the phone, every run follows the same path:

```mermaid
flowchart LR
    S["Start<br/>date, schedule or event"] --> A["Audience<br/>passes that match"]
    A --> X["Actions<br/>applied to each pass in the order shown"]
    X --> P["Pass pushed to the device once"]
    P --> W["Apple Wallet and Google Wallet<br/>show the updated pass"]
    P -. "only with Send a notification" .-> N["Message on the lock screen"]
```

Three ideas help when building one:

* **One trigger per automation.** Two different moments, such as "on install" and "on the birthday", need two automations.
* **All actions land together.** Every action is applied to the pass first, then the pass is sent to the phone once. The customer never sees a half-updated pass.
* **A refresh is silent; a notification is not.** Changing the data, the pass template or the theme updates the pass quietly. Only the **Send a notification** action makes the phone show a message.

### Find the automations and open the editor

Automations are in the admin console under **Engagement → Automations**. The list shows each automation with its actions, its schedule in plain words and its status. Click a row, or **Add new**, to open the editor.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-7509337ddde95b0a2776b395067fb96276c84e83%2Fautomations-list-active-native.png?alt=media" alt="Automations list in the admin console, with Active, Inactive, Expired and All tabs and the Add new button"><figcaption><p>The tabs at the top filter automations by state, and the Status column shows whether each one is waiting for an event, watching for new passes, expired or disabled.</p></figcaption></figure>

The left column of the editor shows the automation block by block; clicking a block opens its settings in the right-hand panel. The **Active** switch and the **Save** button sit at the top right.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-31fd6908c2d2534f0ec2b69a9861457b6243bcb5%2Fautomation-editor-start-trigger-native.png?alt=media" alt="Automation editor with the summary sentence at the top, the blocks in the left column and the Start settings on the right"><figcaption><p>The left column reads Start, Audience, actions, End and Settings from top to bottom; the right-hand panel shows the settings of the selected block.</p></figcaption></figure>

Under the name, a summary sentence rewrites the whole automation in plain English and updates as the automation is built. It is the best check before saving: if the sentence does not describe the intended behavior, adjust the automation.

## Start: when it runs

The Start block decides the moment the automation goes into action. It has three tabs: **Schedule** for anything tied to the clock, **Event** for something that happens to a pass, and **External input**, which the editor marks as planned and which cannot be used yet.

### Schedule

The Schedule tab offers four options, from the simplest one-off to a reminder calculated pass by pass.

* **As soon as it is saved** runs once, about a minute after saving. It suits tests and urgent one-off changes, and concerns the passes that match at that moment.
* **At a specific date** runs once, at the chosen date and time, in the time zone of the browser (shown under the field). A second choice then decides who receives it. **Once, on the run date** works like a photograph: only the passes that match on that day are concerned. **Then keep watching** turns the date into a start date: passes that start matching later are also served, once each. See [Keep watching](#keep-watching).
* **On a repeating schedule** runs every hour, day, week, month or year at a chosen time. The audience is checked again at every run, so the same pass can be updated each time. This is ideal for keeping data up to date, and best kept away from notifications.
* **Relative to a date on the pass** runs pass by pass, a set time before or after a date stored on each pass, such as an expiry date or a birthday. The time can be pinned, for example "1 day before expiry, at 9:00". **Pin to specific time** sets a time of day in a time zone chosen next to it (the browser's by default). Every pass fires at that time in that zone, not in the holder's own time zone.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-03d3eb37bd06f2639f7e6db3433db0c9a68407d6%2Fautomations-14-repeating-retake.png?alt=media" alt="Start panel with On a repeating schedule selected, set to every day at 9:00"><figcaption><p>A repeating schedule: pick hour, day, week, month or year, then the time of the run.</p></figcaption></figure>

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-d5393df2be4ffd826fb9b255b741f9d43b6d31f9%2Fautomations-15-relative-retake.png?alt=media" alt="Start panel with Relative to a date on the pass selected, showing the metadata field, the direction and the offset"><figcaption><p>A date-based trigger: choose the date field, Before or After, the offset and its unit, and optionally pin a specific time of day.</p></figcaption></figure>

{% hint style="info" %}
**Relative to a date on the pass** only lists dates that the pass template exposes as date fields. If a birthday or an expiry date does not appear in the list, add it to the pass template, for example as metadata of type Date & time.
{% endhint %}

### Event

The Event tab makes the automation react to something that happens to a pass. It runs pass by pass, each time the event happens to a pass that belongs to the audience.

| Event                                    | Happens when                                                             | Options                                                                                                         |
| ---------------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| **Pass added**                           | The customer adds the pass to Apple Wallet or Google Wallet.             | **On the first add only** ignores re-installs and second phones; **On every add** counts each one.              |
| **A pass value changes**                 | A metadata of the pass gets a new value, such as points, tier or a date. | **Which metadata?** Without a delay, it goes out in the same update as the change.                              |
| **A benefit is used**                    | A benefit is redeemed, for example at the till.                          | Which benefit templates count. Optionally only when the pass has nothing left.                                  |
| **A benefit is credited**                | Value is added to a benefit: a stamp, a top-up, a refund.                | Which benefit templates count. Optionally only when the pass has nothing left.                                  |
| **A benefit’s balance moves either way** | A benefit is used or credited.                                           | Rarely needed; one of the two options above is usually clearer. Optionally only when the pass has nothing left. |

**Custom event**, an event sent by a connected system, is listed as planned and cannot be used yet.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-9e749ec2631c564828e95487e1fe04685964f64a%2Fautomations-08-event-pass-added-retake.png?alt=media" alt="Event tab with Pass added selected and the On the first add only condition"><figcaption><p>Pass added: the Condition switch chooses between the first install only and every install.</p></figcaption></figure>

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-769398500854ff4bf3052453be0e2465597be5ca%2Fautomations-10-event-benefit-used-retake.png?alt=media" alt="Event tab with A benefit is used selected and the benefit template picker"><figcaption><p>A benefit is used: pick one or more benefit templates, or leave the field empty to watch all of them. The delay option sits at the bottom.</p></figcaption></figure>

Every event can be followed by a delay, for example "3 hours after the benefit is used", so the message does not arrive while the customer is still at the till. Benefit events run at most once per pass.

## Audience: who receives it

The audience defines which passes the automation concerns. It is a list of conditions combined with AND: a pass must match all of them. To accept several values for the same field, such as "Gold or Platinum", the **In** operator takes a list.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-359cd17250f0a2bb469449ed1555edacc3c43ed9%2Fautomations-03-audience-retake.png?alt=media" alt="Audience panel with one condition and the estimated audience count"><figcaption><p>An audience with one condition, here the pass template. The estimated count at the bottom shows how many passes match today.</p></figcaption></figure>

Every new automation starts with the condition **Pass added · Any device**, which means "the pass is currently in a wallet". It is worth keeping: there is little point updating passes nobody has installed. It can be narrowed to **Apple** or **Google** only.

**Add a condition** offers five kinds of filter.

| Condition       | What it looks at                                                                           | Example                          |
| --------------- | ------------------------------------------------------------------------------------------ | -------------------------------- |
| **Template**    | The pass template the pass is built from.                                                  | Template equals the loyalty card |
| **Theme**       | The theme currently applied to the pass.                                                   | Theme equals "Summer sale"       |
| **Metadata**    | Values the pass makes searchable: tier, points, store, country, VIP status, dates.         | Metadata `tier` equals `gold`    |
| **Identifiers** | The customer's references in other systems, such as a CRM number or a loyalty card number. | Identifier equals `12345`        |
| **Pass added**  | Whether, and on which wallet, the pass is installed.                                       | Pass added on Apple              |

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-2c2b56afc38989413d5a339a2714bfedbe61965e%2Fautomations-16-condition-types-retake.png?alt=media" alt="Condition type list with Template, Theme, Metadata, Identifiers and Pass added"><figcaption><p>The five kinds of condition available under Add a condition.</p></figcaption></figure>

Each condition then needs an operator: **Equals**, **Not equals**, **In**, **Not in**, **Contains**, **Starts with**, **Ends with**, and for data fields **Is empty** or **Is not empty**. Numbers and dates can also be compared with greater than or less than.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-f13a1e3f4277fd5a7ecbed0ed6625215b4340973%2Fautomations-17-operators-retake.png?alt=media" alt="Operator list showing Equals, Not equals, In, Not in, Contains, Starts with and Ends with"><figcaption><p>The operators for a condition. In and Not in accept several values.</p></figcaption></figure>

{% hint style="warning" %}
**Prefer Equals for exact values.** Metadata and identifier conditions start on **Contains**. "gold" is contained in "rose-gold", so switch to **Equals** whenever an exact value is meant.
{% endhint %}

Under the conditions, the editor shows how many passes match today. The figure is calculated again when the automation actually runs. A count of zero is not an error: with **Keep watching**, an automation can start empty and serve passes as they become eligible. After changing a filter, **Refresh audience** in the **⋯** menu of the row in the automations list recalculates the figure.

## Actions: what changes on each pass

Actions are added with **Add an action**. Each type can be used once per automation. The notification comes last, so it only goes out when the pass already shows the new benefit, data, pass template and theme.

**Change the pass template** sits under **Advanced actions** in the **Add an action** window.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-57c7abc6c619e277f9e348e67f31abbdae3065ea%2Fautomations-11-add-action-retake.png?alt=media" alt="Add an action window listing Grant a benefit, Update the pass data, Apply a theme and Send a notification, with Change the pass template under Advanced actions"><figcaption><p>The five action types, in the order they are applied. An action already in the automation disappears from the list.</p></figcaption></figure>

### Grant a benefit

This action gives each pass of the audience a benefit, such as a discount, a free product or a reward, created from a [benefit template](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/benefit-templates.md). The validity and the stock come from the benefit template itself, not from the automation.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-5926db32da9136ec884dd4c5c897b74cb07071ab%2Fautomations-12-benefit-retake.png?alt=media" alt="Grant a benefit panel with the benefit template search field and list"><figcaption><p>Pick the benefit template in the searchable list; each line shows its type and how long it stays valid.</p></figcaption></figure>

### Update the pass data

This action writes new values onto the pass, as pairs of a key and a value: a tier, an offer code, a flag. It is only useful with keys the pass template already reads; a new key stays invisible until the template displays it.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-391f4769969a3fef33ea201a661837acef6ef30b%2Fautomations-09-updatedata-retake.png?alt=media" alt="Update the pass data panel with a key, a value and the Add additional data button"><figcaption><p>One row per key and value. Add additional data adds a row and the bin icon removes it.</p></figcaption></figure>

### Change the pass template

This action moves the pass to another pass template, with its own layout, fields and images. The customer's data, identifiers and installation are kept, so the pass simply changes in the wallet.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-38c4a198a9f6e9694c04c01a7eac06d7188ec6f7%2Fautomations-13-template-retake.png?alt=media" alt="Change the pass template panel with the template picker and a reminder that nothing switches it back"><figcaption><p>Choose the new template in the list. The reminder underneath is important: the change is permanent.</p></figcaption></figure>

{% hint style="warning" %}
**The change is permanent.** Nothing switches the pass template back on its own. A seasonal look needs a second automation to restore the original.
{% endhint %}

### Apply a theme

A theme is a skin on top of the pass template: colors, images, sometimes a title. The fields and the structure stay the same. Applying a theme replaces any theme already on the pass, and the switch **Remove the theme instead** sends the pass back to its normal look, which is the clean-up step at the end of a campaign. [Wallet pass themes](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/wallet-pass-themes.md) explains how themes are created and applied.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-6119666b3865ebef6406223cd27dce09a23f56f4%2Fautomations-04-theme-retake.png?alt=media" alt="Apply a theme panel with the Remove the theme instead switch and the list of themes"><figcaption><p>Themes appear as cards with their image and colors; the selected one is outlined. The switch at the top turns the action into a clean-up.</p></figcaption></figure>

### Send a notification

This action shows a message on the customer's lock screen. [Push notifications](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications.md) compares how Apple Wallet and Google Wallet handle it: Apple Wallet shows the configured message, while Google Wallet controls the lock-screen text and usually tells the customer that a new message is available.

The message has a **Default** text plus one text per language the pass supports. Each phone displays the version matching its language, falling back to Default. A **Recommended length** counter suggests staying around 120 characters so the message fits on screen. Longer text is allowed.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-5dc5fe5d9e1557b4de024de9d3b566291d8e30f8%2Fautomations-05-notification-retake.png?alt=media" alt="Send a notification panel with the language tabs, the message box and the length counter"><figcaption><p>The language tabs sit at the top right. Check that every language tab is filled in before saving.</p></figcaption></figure>

When the notification is the only action, the **Update pass data** switch decides whether the pass content is also refreshed at the same time. A notification stays visible for seven days by default, and recipients can read it on the back of the pass. The duration is set per template, in **Wallet → Templates →** the template **→ General → Advanced configuration → Notification settings** (**Duration** and **Unit**, see [Other options](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/general-tab.md#other-options)).

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2FlmfaayMrxqgmUYkOYYeI%2F08-template-notification-duration.png?alt=media&amp;token=21a904ab-53cc-4144-9525-d81c7a893247" alt="Template advanced configuration showing the notification Duration and Unit fields"><figcaption><p>The notification duration is set per template. The default is seven days.</p></figcaption></figure>

## End: when it stops

The End block decides how long the automation stays in action. The options depend on the trigger.

| Trigger                                   | End options                                                                                                                                           |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| As soon as saved, or specific date (once) | After its single run. Nothing to set.                                                                                                                 |
| Specific date, keep watching              | **I stop it by hand**, **A fixed date**, or **The benefit template ends** when the automation grants a benefit and the template has a fixed end date. |
| Repeating schedule                        | **I stop it by hand** or **A fixed date**.                                                                                                            |
| Date on the pass, or event                | Runs until someone switches it off.                                                                                                                   |

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-74813bcbc3d2009b0d1db45f4258b9b8f49692f4%2Fautomations-06-end-watching.png?alt=media" alt="End panel with the Keep watching until list: I stop it by hand, A fixed date, The benefit template ends"><figcaption><p>The end options of a watching automation. The last option is only available when the automation grants a benefit.</p></figcaption></figure>

An automation whose end has passed shows as **Expired** in the list. A one-off automation whose date is already past will not run, even if it is switched back on; duplicate it with a new date to run it again.

## Settings: how fast it runs

* **Active** is the on/off switch at the top right. An inactive automation does nothing and appears under the **Inactive** tab.
* **Throughput** sets how many passes are updated per second (12 by default). The slider goes up to 50, and values below 1 slow a long run down further. The panel also estimates how long the whole audience will take. A lower pace spreads the load on very large audiences. Increase it only when delivery must finish before a deadline, for example to send event access details before doors open. It is a request, not a limit: passes above the tenant's ceiling are postponed, never dropped.
* **Update metadata** recalculates the searchable values of the pass after the run. Switch it on when an action changes data that another automation filters on, for example when one automation sets the tier and another reacts to tier = gold.
* **Name and tags**: a name is required to save; tags help group automations, for example by campaign.

<figure><img src="https://content.gitbook.com/content/97ZAXMtqOjhvBBCfpmcE/blobs/k3oWvjUKrUWhJy2WRsIf/automations-07-settings.png" alt="Settings panel with the Throughput slider and the Update metadata switch"><figcaption><p>The Throughput slider shows the estimated duration for the current audience; the Update metadata switch sits underneath.</p></figcaption></figure>

## Keep watching

With **Once**, the automation takes a photograph of the audience on the run date and serves only those passes. With **Keep watching**, it serves that first group, then keeps looking for passes that start matching, and serves each of them once. It is the most useful option for campaigns.

A pass can start matching in three ways:

* **It is installed.** With the default **Pass added** condition, a pass installed after the start date is picked up within seconds.
* **Its data changes.** The CRM, an API call or another automation changes a tier or a segment, and the pass now matches. The data change must refresh the metadata (see **Update metadata** in Settings).
* **The audience is widened.** Editing the conditions serves every newly matching pass that was never served before.

A pass is never served twice by the same watching automation, even if it stops and starts matching again, or is installed on a second phone.

{% hint style="warning" %}
**Widening the audience acts immediately.** On a watching automation, changing "Gold" to "Gold or Silver" hands the actions to every existing Silver pass at once.
{% endhint %}

## Common automations

Each combination below lists what to set in every block.

| Need                               | Start                                                                     | Audience                                     | Actions                                                          | End                                            |
| ---------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------- |
| Seasonal look and announcement     | At a specific date, **Then keep watching**                                | Pass added, optionally one pass template     | Apply a theme, Send a notification                               | A fixed date                                   |
| Welcome on first install           | Event → Pass added → **On the first add only**, delay of about 10 minutes | Template equals the loyalty template         | Send a notification, optionally Update the pass data             | Runs until switched off                        |
| Tier upgrade                       | At a specific date (today), **Then keep watching**                        | Pass added and Metadata `tier` equals `gold` | Change the pass template (or Apply a theme), Send a notification | Stopped by hand                                |
| Expiry or birthday reminder        | Relative to a date on the pass, 1 day before, pinned at 9:00              | Pass added and one pass template             | Send a notification                                              | Runs until switched off                        |
| Follow-up after a reward is used   | Event → A benefit is used, delay of 3 hours                               | Pass added                                   | Send a notification                                              | Runs until switched off; at most once per pass |
| Move passes to a new pass template | At a specific date, **Then keep watching**                                | Template equals the old one                  | Change the pass template, without notification                   | Stopped by hand                                |
| Regular data refresh               | On a repeating schedule, every day at 6:00                                | Pass added and one pass template             | Update the pass data, without notification                       | **I stop it by hand** or **A fixed date**      |

Notes on the recipes:

* **Seasonal look.** Clean up with a second automation on the end date: audience Theme equals the campaign theme, action **Apply a theme** with **Remove the theme instead**, no notification.
* **Tier upgrade.** Whatever updates the tier (the CRM, the API or another automation) must refresh the metadata so the change is noticed. Each customer is congratulated once.
* **Move passes.** Leave out **Pass added** if uninstalled passes should move as well. Lower the throughput for very large audiences, and switch on **Update metadata** if the new pass template calculates different values.
* **Regular data refresh.** Never add a notification to a repeating automation: it would message the same customers at every run. See the Google Wallet notification limit in [Push notifications](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications.md#limits).

### Send a one-off notification

This recipe sends one message to a group of passes, for example the VIPs of one store.

1. Open **Engagement → Automations** and click **Add new**. Give the automation a name: it is internal and never shown to customers.
2. In **Start**, choose **At a specific date** with **Once, on the run date**, or **As soon as it is saved**.
3. In **Audience**, keep **Pass added** and add the conditions, for example Metadata `isVip` equals true and Metadata `storeId` equals the store concerned. Check the estimated audience.
4. Click **Add an action**, choose **Send a notification** and write the **Default** message, then one message per language.
5. In **End**, nothing to set for a single run. In **Settings**, keep the default **Throughput**, then read the summary sentence and click **Save**.

After the run, check the delivery on one pass: see [Check that it worked](#check-that-it-worked).

## Before switching it on

* The summary sentence describes exactly the intended behavior, and the estimated audience is in the expected range (or zero on purpose for a watching automation).
* Conditions use **Equals** wherever an exact value is meant, and every language tab of the notification is filled in.
* There is a plan to undo the change: theme removal, switch back to the previous pass template, or end date.
* The automation was first tried on a few test passes, filtered on an identifier, with an iPhone and an Android phone.

## Check that it worked

The most reliable check is the pass the automation was meant to change. In **Wallet → Passes**, open the pass and read its **Notifications** and **History** tabs (see [Pass details](https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-details.md)). If a message is listed in **Notifications** but the customer did not see it, the cause is on the phone, such as notifications turned off for the pass.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2FlizqMCCxpYJRrx4CI9z7%2Fautomations-19-pass-notifications.png?alt=media&amp;token=9a3cc3cc-ca85-4863-b83a-b405613a52cb" alt="Pass Notifications tab with a timeline of sent notifications per device"><figcaption><p>The Notifications tab: each message sent, with the wallet it went to and its text.</p></figcaption></figure>

### View the history of an automation

Each automation keeps a record of its runs. In the automations list, the **⋯** menu at the end of a row offers **View history**.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-013d8669b34cca274c15e4309248d0ef69331de5%2Fautomations-21-history-menu-retake.png?alt=media" alt="Row menu of an automation with Edit, View history and Delete"><figcaption><p>The ⋯ menu at the end of each row in the automations list. View history opens the list of runs.</p></figcaption></figure>

The **Execution history** page lists every run with its start date, its duration and its result in the **Success** column. A run that fails is tried again automatically, and the **Retry index** column shows which attempt is displayed. Runs are kept for the last 90 days.

<figure><img src="https://content.gitbook.com/content/97ZAXMtqOjhvBBCfpmcE/blobs/XlTRP7ZOujPicbwAnrx1/automations-22-execution-history.png" alt="Execution history page listing runs with their start date, duration, success status and retry index"><figcaption><p>Each line is one run. Check the start date and the Success column to confirm the automation ran as planned.</p></figcaption></figure>

The **⋯** menu of a run opens **View detail**, a technical log of every step of that run. Share the execution ID shown at the top when asking The Wallet Crew support to look into a run.

<figure><img src="https://content.gitbook.com/content/97ZAXMtqOjhvBBCfpmcE/blobs/JWZdrSit6bUXgfk5ZlEb/automations-23-execution-detail.png" alt="Execution detail page with the execution ID, start date, duration and the list of log entries"><figcaption><p>The detail of a run. The execution ID at the top is the reference to share with support.</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
