---
title: Shopify Flow trigger when a specific tag is added or removed
description: >-
  Start a Shopify Flow workflow once when one tag is added to an order,
  customer or product, and again when it is removed. With the tags that
  changed.
source_url:
  html: >-
    https://docs.workflow-trigger-extensions.app/specific-tag-added-or-removed
  md: >-
    https://docs.workflow-trigger-extensions.app/specific-tag-added-or-removed.md
---

# Run a workflow when one specific tag is added or removed

Starting a process with a tag is the most common job of this app. Staff tag an order `hold`, a fraud app tags it `review`, a subscription app tags a customer `vip`. The workflow should act **once**, when that tag appears, and often a second workflow should act when the tag is taken off again.

This page shows how to build both, and how the tag triggers of this app differ from Flow's own **Order updated**, **Customer updated** and **Product updated** triggers with the `tags` field.

## What each trigger knows about a tag change

| | Flow's updated trigger watching `tags` | Tags Added and Tags Removed in this app |
| --- | --- | --- |
| Starts a workflow | on every change to the tag list, whichever tag was added or removed | Tags Added when at least one tag is added, Tags Removed when at least one is removed |
| What the workflow gets | the tag list after the change | `addedTags`, `removedTags`, `previousTags`, `currentTags` |
| "Was my tag just added?" | cannot be answered: the tag is on the list, since now or since last month | `addedTags` includes it |
| "Was my tag just removed?" | cannot be answered: the tag is not on the list, like on every record that never had it | `removedTags` includes it |
| Several tags written in one go | one run per write | one event that lists all of them |

## What happened in our test

One order on a development store, November 20, 2026. A workflow on Flow's Order updated and the tag triggers of this app ran side by side and wrote down what they saw. For each run we then checked the condition a tag workflow would use: on Flow's trigger the only one it can have, "the order's tags include `exp-vip`", and on Order Tags Added "`addedTags` includes `exp-vip`".

| Step | Flow's Order updated | Order Tags Added |
| --- | --- | --- |
| Tag `exp-vip` added | runs, the tags include it: **condition true** | fires with `addedTags` = `exp-vip`: **condition true** |
| Tag `exp-other` added later | runs again, the tags still include `exp-vip`: **true again** | fires with `addedTags` = `exp-other`: false |
| Tag `exp-other` removed | runs again: **true again** | does not fire (Order Tags Removed does) |
| Three more tags added within one second | 3 runs: **true three more times** | 1 event with the three tags: false |
| Tag `exp-vip` removed | runs, the tag is gone: false, and nothing says that it was just removed | Order Tags Removed fires with `removedTags` = `exp-vip` |

One tag, added once: the workflow on Flow's trigger would have acted **six** times, the one on Order Tags Added **once**. If the action is an email to the customer, a hold on the fulfillment or a call to another system, that difference is the whole point.

## Build it: act once when a tag is added

1. In Shopify Flow choose **Select a trigger**, open **Workflow Trigger Extensions** and pick **Order Tags Added**.
2. Add a **Condition**: `addedTags` **Includes** `hold`.
3. Add your action, for example **Hold fulfillment order** inside a **For each** over the order's fulfillment orders.
4. Turn the workflow on. Turning it on also switches the trigger on in the app.

The workflow runs when the tag `hold` is added. It does not run when another tag is added to an order that already has `hold`, when a tag is removed, or when anything else on the order changes.

> [!NOTE]
> **Good to know**
> - `addedTags` is text: the added tags, separated by commas. **Includes** `hold` is also true for a tag such as `on-hold`. Pick tag names that are not part of another tag, or use **Equal to** when your process only ever adds one tag at a time.
> - Tags that Flow adds fire this trigger as well. Make sure a workflow does not add the very tag it listens for.
> - A tag that is removed and added again fires Tags Added again. That is usually what you want for a process that can be restarted.

![The Flow trigger events block on a customer page: a note added and the tag VIP added](https://cdn-dev.eu.codecreationlabs.cloud/crm-tool/uploads/SjJ78gKLnLlocopCui3Cs62dJbGZ7F1n/d7d0b4ea2622b9a6.png)
*The events block on a customer's page in the Shopify admin names the tag that was added.*

## Build it: act when a tag is removed

1. Pick **Order Tags Removed** as the trigger.
2. Add a **Condition**: `removedTags` **Includes** `hold`.
3. Add the action that undoes the first workflow, for example **Release fulfillment order hold** inside a **For each** over the order's fulfillment orders.
4. Turn the workflow on.

This is the case an updated trigger cannot cover on its own. After a tag was removed, the record looks exactly like a record that never had the tag. A workflow that only sees the current tag list has nothing to tell the two apart.

## The same for products, customers and draft orders

| Record | Added | Removed |
| --- | --- | --- |
| Order | Order Tags Added | Order Tags Removed |
| Product | Product Tags Added | Product Tags Removed |
| Draft order | Draft Order Tags Added | Draft Order Tags Removed |
| Customer | Customer Tags Added | Customer Tags Removed |

All eight send the same four values: `addedTags`, `removedTags`, `previousTags` and `currentTags`. [Order triggers, step by step](https://docs.workflow-trigger-extensions.app/order-trigger-tutorials.md), [Product triggers, step by step](https://docs.workflow-trigger-extensions.app/product-trigger-tutorials.md), [Draft order triggers, step by step](https://docs.workflow-trigger-extensions.app/draft-order-trigger-tutorials.md) and [Customer triggers, step by step](https://docs.workflow-trigger-extensions.app/customer-trigger-tutorials.md) have a worked example for each.

For customers, Flow also has its own **Customer tags added** and **Customer tags removed** triggers, which list the tags that were added or removed. For orders, products and draft orders Flow has no such trigger: there the tag triggers of this app are the way to react to one tag.

## If you use Flow's updated trigger for tags

Flow's Order updated, Customer updated and Product updated can watch `tags` too, and for a simple alert ("tell me when the tags of an order change") that is all you need. To keep such a workflow from acting again and again on one tag, the usual pattern is a marker:

1. Condition: the tags include `hold` **and** do not include `hold-done`.
2. Do the work.
3. Last step: add the tag `hold-done`.

It works, with three things to keep in mind. Every workflow needs its own marker tag, and the tags of your records fill up with them. The workflow starts once more for its own marker tag and stops at the condition. And when `hold` is removed and added again, nothing happens until someone removes the marker as well. Acting on a **removed** tag is not possible this way.

### Why does my workflow run several times for one tag?

A workflow on a Flow updated trigger with the tags field runs on every change to the tag list. As long as your tag is on the record, every other tag that is added or removed makes the condition true again. Use the Tags Added trigger of this app with a condition on `addedTags`, or the marker pattern described above.

### Can I start a workflow for one specific tag only?

Yes. Use the Tags Added trigger for the record type and add the condition `addedTags` **Includes** your tag. For removal use Tags Removed with `removedTags`.

### What happens when an app adds several tags at once?

The trigger fires once and `addedTags` lists all of them. In our test three tags written within one second arrived as one event with the three tags.

### Does Shopify Flow have a trigger for a tag that was added or removed?

For customers, yes: Customer tags added and Customer tags removed. For orders, products and draft orders a tag can only be watched with the tags field of an updated trigger, which shows the list after the change and not what was added or removed. Order Tags Added, Order Tags Removed, Product Tags Added, Product Tags Removed and the two draft order triggers of this app name the tags.

### Can I see which tags were on the record before?

Yes. `previousTags` holds the list before the change and `currentTags` the list after it, on all eight tag triggers.

## Next steps

- [Flow's updated triggers and Workflow Trigger Extensions](https://docs.workflow-trigger-extensions.app/flow-updated-triggers-compared.md) - the overview of Flow's updated triggers and this app.
- [Old and new values: what a workflow can do with them](https://docs.workflow-trigger-extensions.app/old-and-new-values.md) - what else a workflow can do with the value before a change.
- [Event history and troubleshooting](https://docs.workflow-trigger-extensions.app/event-history-and-troubleshooting.md) - see every tag event and what it carried.
