---
title: "Plans and usage"
description: "Free, Starter, Grow and Unlimited plans, what counts as a trigger event, quota alerts at 80% and 100%, and how to reduce usage."
canonical: "https://docs.workflow-trigger-extensions.app/plans-and-usage"
---

# Plans and usage

Workflow Trigger Extensions is free to install. Paid plans raise the monthly event allowance.

## Plans

| Plan | Price | Trigger events per month |
| --- | --- | --- |
| Free | $0 | 5,000 |
| Starter | $25 | 25,000 |
| Grow | $50 | 75,000 |
| Unlimited | $100 | Unlimited |

**Every trigger is available on every plan, including Free.** Plans differ only in
volume.

## What counts as an event

One event is counted each time a trigger from this app fires and delivers to Shopify
Flow.

- Triggers from Shopify or from other apps are **not** counted. Only this app's
  triggers consume the allowance.
- A change that is detected but does not match an enabled trigger is not counted.
- The three typed metafield triggers (Order, Product, Customer Metafield Update) share
  a single event with the generic **Metafield Update** trigger, so they do not
  double-count.
- The allowance resets at the start of each billing period.

> [!NOTE]
> Your current usage is on the app's **Home** page, with a breakdown by trigger so you
> can see which one is consuming the allowance.

## Quota alerts

The app emails you when usage crosses **80%** and again at **100%** of the allowance.
Recipients and the 80% threshold are configurable in the app's notification settings;
the threshold can be set anywhere between 50% and 99%.

Each alert is sent once per billing period. Changing plan mid-period re-arms the alerts
against the new limit. Stores on Unlimited never receive quota emails.

## What happens at 100%

Once the allowance is used up, triggers stop firing until the period resets or you
upgrade. Your configuration is untouched: settings, permissions, and workflows are all
preserved, and firing resumes by itself the moment there is allowance again.

> [!CAUTION]
> **Events that occur while you are over the limit are lost, not queued.** They are not
> held back and delivered later. When you upgrade or the period resets, triggers resume
> from that moment onward, so there is a gap covering everything that happened while the
> quota was exhausted.

This is worth understanding precisely, because it is not recoverable:

- **Nothing is replayed.** There is no backlog to drain. An order that changed while you
  were over the limit does not fire when you upgrade.
- **The gap is invisible in Event History.** Blocked events never create a history row,
  so you cannot look back afterwards and see what you missed.
- **Change detection moves on regardless.** For a field-level trigger, the app still
  records the new value as its baseline even though the trigger did not fire. After you
  upgrade, the next change is compared against that newer value, so the missed change
  cannot resurface later.

A worked example. You are on Free (5,000) and hit the cap on the 20th:

1. On the 22nd a customer changes an order's shipping address. **Order Shipping Address
   Changed does not fire, and the event is gone.**
2. On the 23rd you upgrade to Starter. Triggers resume immediately.
3. On the 24th someone edits that same order's address again. This fires normally,
   comparing against the address from the 22nd.

The change on the 22nd is never delivered, in step 2 or at any later point.

> [!WARNING]
> If you are anywhere near your limit, upgrade **before** you exhaust it rather than after.
> Upgrading stops the loss going forward; it cannot recover what was already dropped. The
> 80% alert exists to give you that warning in time.

## Keeping usage down

If you are consuming more than you expect, the cause is almost always one of the broad
`... Update` triggers firing on every edit:

1. Open **Home** and look at the per-trigger breakdown.
2. Open **Settings > Trigger Settings** and suppress the broad `... Update` triggers
   your workflows do not use.
3. Prefer a narrow trigger over a broad one. **Product Variant Price Changed** fires far
   less often than **Product Update**.

> [!TIP]
> Suppressing a trigger stops it *before* it consumes quota, so this genuinely reduces
> usage rather than just hiding the events. See [Settings and trigger toggles](https://docs.workflow-trigger-extensions.app/settings-and-toggles.md).