> ## 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 installs your app

> The Store installs app trigger (app.installed): when it fires once per store, which variables and recipient email it carries, and what to build on it.

**Store installs app** (`app.installed`) fires the first time a store installs your app. It's the trigger for a welcome email, an onboarding sequence, or an internal notification that a new merchant arrived.

## When it fires

On the store's first successful authentication with your app: the OAuth handshake that creates its install record. It fires **once per store**, not on every sign-in.

There's one subtlety worth knowing: a store can already have a CRM row without ever having installed (the CRM creates one to hang a manually added contact on). Meridian goes by what it has actually recorded, not by the row merely existing, so that store's first real install still fires this trigger.

A store that had the app before and comes back doesn't fire this. That's [Reinstalled](https://help.the-meridian.ai/reinstalled.md).

## What it carries

The store's own [variables](https://help.the-meridian.ai/automation-variables.md): name, domain, plan, currency, revenue, install date. No event-specific variables: nothing happened beyond the install itself.

The recipient for a downstream [Send email](https://help.the-meridian.ai/send-email.md) is the email on the store's install record. For an app hosted on Meridian, that's the address Meridian reads from Shopify during the install, unless your app sends its own `email` to [`identify`](https://help.the-meridian.ai/sdk-identify), which Meridian keeps over Shopify's. For an app [hosted elsewhere](https://help.the-meridian.ai/sdk-hosting.md), the SDK's [`afterAuth`](https://help.the-meridian.ai/sdk-app#afterauth) reads it from Shopify and sends it with the install report itself (SDK 2.10.0 and later), so it is on record before this trigger's first step runs, with no Wait needed. On an older SDK your app has to pass it as `email` to [`identify`](https://help.the-meridian.ai/sdk-identify) or `mintShopToken`, and that call can land after this trigger fires: the email step reads the address when it runs, so put a [Wait](https://help.the-meridian.ai/wait.md) of a few minutes before it and a late address still reaches the merchant.

## Building on it

Pick **Store installs app** as the trigger, then add the action to run. Common shapes:

* Send a welcome email straight away.
* Branch on a [segment](https://help.the-meridian.ai/condition-segment.md) first, so a store that arrives on a paid plan gets a different email from one on the free plan.
* Set an onboarding stage with [Populate custom field](https://help.the-meridian.ai/populate-custom-field.md), so the rest of Meridian can see where each new store is.


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