> ## 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.

> ## Agent Instructions
> These are the public docs of Meridian for Shopify apps: hosting, billing (Plan Builder and the @the-meridian/sdk package), CRM, emails and automations for Shopify app developers.
> Start with these pages: Meridian MCP (https://help.the-meridian.ai/mcp-server.md) to connect a coding agent, AI coding agents (https://help.the-meridian.ai/ai-agents.md) for the agent skill, SDK quickstart (https://help.the-meridian.ai/sdk-quickstart.md), Running your app with the CLI (https://help.the-meridian.ai/cli-dev.md), Deployment (https://help.the-meridian.ai/deployment.md), and Errors (https://help.the-meridian.ai/errors.md) to look up an error code or message.
> Fetch one page at a time as Markdown (the page URL followed by .md), using the index in https://help.the-meridian.ai/llms.txt. llms-full.txt holds every page in one file of about 900 KB, so avoid loading it whole.
> With Meridian MCP connected, search these docs with docs_search and docs_get, and read live facts (feature and event keys, plan ids, environments, deployments, logs) from the MCP tools instead of guessing them.

# Automation trigger: store uninstalls your app

> The Store uninstalls app trigger (app.uninstalled): when Shopify's webhook fires it, why it can still email the store, and win-back flow ideas.

**Store uninstalls app** (`app.uninstalled`) fires when a store removes your app. Use it for a win-back email, to record the churn, or to notify your team.

## When it fires

From Shopify's `app/uninstalled` webhook, when Shopify tells Meridian the store removed your app. The store's install record moves to uninstalled and its access token is dead from that point.

The webhook can take a minute to reach Meridian, and a merchant who reinstalls right away can get there first. Meridian orders the two by Shopify's own timestamps: the uninstall still fires this trigger, but the store's record stays installed and keeps its token, and [Reinstalled](https://help.the-meridian.ai/reinstalled.md) fires right after for the return.

## The one trigger that still emails an uninstalled store

Meridian normally refuses to send an automation email to a store that has uninstalled, because the address is usually stale and the mail is unwanted. **This trigger is the deliberate exception**, because off-boarding email is the entire point of it. Every other trigger that arrives for an uninstalled store skips its send steps.

A [Send email](https://help.the-meridian.ai/send-email.md) step addressed to *specific people* is unaffected either way: it goes to your own list, not to the store.

## What it carries

The store's own [variables](https://help.the-meridian.ai/automation-variables.md): its plan, revenue and how long it was active are exactly what a win-back email wants. No event-specific variables.

## Building on it

* Email the merchant asking why, with a way to reply.
* Branch on a [segment](https://help.the-meridian.ai/condition-segment.md) so only paying stores get the win-back, not free-plan churn.
* Write a churn reason or date to a [custom field](https://help.the-meridian.ai/populate-custom-field.md) for your own reporting.

> [!NOTE]
>
> The trigger is "uninstalled", not "deleted". It's about a store removing your app, and it pairs with [Reinstalled](https://help.the-meridian.ai/reinstalled.md) for the ones who come back.


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