---
title: "Install and set up"
description: "Install Workflow Trigger Extensions, grant the optional data permissions your workflows need, and build your first Shopify Flow workflow."
canonical: "https://docs.workflow-trigger-extensions.app/install-and-set-up"
---

# Install and set up

Getting from a fresh install to a working workflow takes about five minutes.

## Step 1: Install the app

Install Workflow Trigger Extensions from the [Shopify App Store](https://apps.shopify.com/flow-trigger-extensions). After install you land on the
app's **Home** page, which shows a setup checklist, your usage for the current period,
and recent trigger activity.

## Step 2: Grant the data access you need

The app ships with **no data access by default**. Every resource it can read is opt-in,
so you grant only what your workflows actually use.

1. Open **Permissions** in the app navigation.
2. Find the card for the data you need, for example **Order Data Access** or
   **Discount Data Access**.
3. Click **Grant**. Shopify shows its own confirmation dialog.

Each card lists exactly which triggers that permission unlocks, so you can work
backwards from the trigger you want. There are 12 permissions in total.

> [!WARNING]
> A trigger whose permission has not been granted will not appear in the Shopify Flow
> trigger picker, or will appear but never fire. If a trigger seems missing, check
> **Permissions** first. See [Permissions and data access](https://docs.workflow-trigger-extensions.app/permissions-and-data-access.md).

## Step 3: Build a workflow in Shopify Flow

1. Open **Shopify Flow** and click **Create workflow**.
2. Click **Select a trigger** and search for the trigger by name, for example
   `Product Variant Price Changed`.
3. Triggers from this app are labelled **Workflow Trigger Extensions** in the picker.
4. Add your conditions and actions, then **Turn on** the workflow.

## Step 4: Let the trigger switch itself on

When you turn on a workflow that uses one of our triggers, the app notices and does the
setup for you:

- it flips that trigger's setting on, and
- for a change-detection trigger, it queues a **baseline sync** of the matching
  resource.

The baseline matters. Change detection works by comparison, so the app needs to know
the current state of your catalog before it can tell you what changed. Until the sync
finishes, the trigger is on but has nothing to compare against.

> [!NOTE]
> **How long does the baseline sync take?** Seconds for a small store, up to 20 minutes
> or so for a catalog above 100,000 items. The Settings tab shows a loading indicator
> while it runs. You do not have to wait around; the workflow simply starts firing once
> it completes.

## Step 5: Confirm it fired

Make the change you are automating, then open **Event History** in the app. Each row
shows the trigger, the resource, the timestamp, and whether the Flow trigger was
delivered successfully. See [Event history and troubleshooting](https://docs.workflow-trigger-extensions.app/event-history-and-troubleshooting.md).

## What if a trigger has no setting?

A few triggers are configured per definition rather than per store:

- **Metafield Update** - configured on the **Metafield Triggers** page, one entry per
  metafield definition you want to watch. See [Metafield triggers](https://docs.workflow-trigger-extensions.app/metafield-triggers.md).
- **Metaobject entry updated** - configured on the **Metaobject Triggers** page, one
  entry per metaobject definition. See [Metaobject triggers](https://docs.workflow-trigger-extensions.app/metaobject-triggers.md).

And the broad `... Update` triggers (Order Update, Product Update, Customer Update, and
so on) are **on by default** once their permission is granted. You suppress the ones
you do not want on **Settings > Trigger Settings**. See [Settings and trigger toggles](https://docs.workflow-trigger-extensions.app/settings-and-toggles.md).