> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Templates

Templates are starter flows built from the triggers, conditions and actions available in the automation builder. Open **Automations → Templates** to search the gallery or filter it by **Onboarding**, **Retention**, **Engagement**, **Lifecycle** or **Operations**. Each card shows a preview of the flow and its trigger and action counts. Open a card to inspect the full flow before copying it.

## What is in the gallery

The gallery includes flows for every current trigger:

| Event | Starter flows |
| - | - |
| Store installs, uninstalls or reinstalls the app | Install welcome sequence, uninstall follow-up, reinstall welcome back |
| Store closes, pauses or reopens | Slack alerts for your team |
| Store access token stops working | Slack connection alert |
| App first identifies a store | Onboarding email or custom field tagging |
| Subscription activates, cancels, freezes, unfreezes, upgrades, downgrades or reactivates | Confirmation, recovery, onboarding and win-back emails |
| Subscription charge is declined or expires | Billing recovery emails |
| Trial is ending or has ended | Trial reminder and follow-up |
| One-time charge activates | Purchase thank-you |
| Subscription approaches its capped amount | Usage limit heads-up |
| Custom field changes | Segment-based Slack alert |
| Custom event is tracked | Slack alert for a live store |
| Usage view crosses a threshold | Usage milestone email |

Some flows show how to use **Wait**, **Store is in segment**, **Variable matches a value** and **Populate custom field**. For example, the install welcome sequence sends an email, waits two days, then sends a follow-up. The segment-based subscriber flow only follows the Yes branch for a segment you choose. The live store activity alert branches on whether the store is a test store.

## Use a template

Click **Use this template** to copy the flow into your app. The copy starts **inactive**. If it has a **Send Email** step, Meridian creates a separate editable email for each such step and attaches it to the copied flow. The email has a subject, preview text and body, so the action does not point at an empty email. You need both **Create automations** and **Edit emails** permissions to use an email flow. A flow without email only needs **Create automations**.

Review the copy before activating it. The starter emails use variables such as `{{store_name}}` and `{{subscription_plan}}`. Edit their wording to fit your app. For a Slack flow, connect a workspace in app settings and choose a channel. A segment condition needs one of your app's segments. A custom field action needs a target field. The usage view threshold flow needs a view and a threshold. Templates leave these app-specific choices open.

Once copied, the automation and emails belong to your app. You can edit them freely. Later gallery changes do not change your copies. Nothing runs until you activate the automation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.