Flow's Collection updated trigger and the collection triggers of this app
What Shopify Flow's Collection updated trigger can watch, including products added or removed, and which collection triggers carry the old title and handle.
Flow's Collection updated trigger starts a workflow when one of up to five fields of a collection changes. Shopify's help page: "The Collection updated trigger provides only the current values of the collection." and "The previous values of the fields that changed aren't available in the workflow."
This app has four collection triggers. Three of them fire for one kind of change, title, handle or description, and carry the value before and after. This page shows which trigger fits which job, including the one job where Flow's trigger is the better choice.
What Collection updated can watch
The fields of Shopify's help page, as of November 20, 2026: descriptionHtml, handle, image, metafield.value, sortOrder, templateSuffix, title and products.
What Shopify's page adds:
- You select at least one field and at most five. A metafield definition or a whole namespace counts as one of the five.
- If you monitor
products, adding a product to the collection or removing one starts the workflow. The Product variable is available only then, and it can be empty, for example when a deleted product is removed from the collection. Shopify recommends a condition that checks it first. - For a new or a deleted collection, Shopify points to the Collection created and Collection deleted triggers.
Field by field
| What changed | Flow's Collection updated | Trigger of this app | Before and after |
|---|---|---|---|
| Handle | handle, new value only |
Collection Handle Changed | oldHandle, newHandle, ready for a URL redirect |
| Title | title, new value only |
Collection Title Changed | oldTitle, newTitle |
| Description | descriptionHtml, new value only |
Collection Description Changed | oldDescription, newDescription |
| Collection metafield | metafield.value, new value only |
Metafield Update for collections | metafield.value, metafield.previousValue |
| Title, handle and description in one workflow | three of your five fields | Collection Update with Send old and new values | collection.changes.fields and collection.changes.items with field, oldValue, newValue |
| Product added to or removed from the collection | products, with the product |
Collection Update fires when Shopify reports the update, but does not name the product | |
| Image, sort order, theme template | image, sortOrder, templateSuffix |
Collection Update fires on these updates. No trigger of this app carries their old value |
For products added to or removed from a collection, Flow's trigger is the better choice: it hands the workflow the product.
What we saw when a collection changed quickly
In our test on November 20, 2026, a collection was changed three times within two seconds. Collection updated started three runs, and all three showed the final title and handle, because a run reads the collection when it starts. The values in between were never seen by a workflow.
The triggers of this app compare each update with the last values they stored, so an event names the title or handle before the change and after it. That is what a redirect needs: the handle the collection had, not only the one it has now.
Workflows that need the value before
Redirect the old URL when a collection handle changes. A renamed handle breaks every link, ad and bookmark that points to the old address. Collection Handle Changed carries oldHandle and newHandle, so one Create redirect URL action sends the old address to the new one. With the new handle alone there is nothing to redirect from. Ready to use: Redirect old collection URLs when a collection handle changes.
Review SEO when a title or description changes. Collection Title Changed and Collection Description Changed carry the text before and after, so the message to the SEO or content team shows exactly what was rewritten.
Tell marketing when a campaign label changes. A collection metafield such as a campaign label is set, changed or removed: the metafield trigger carries the value before and after. See Collection metafield trigger.
Notice when the rules of an automated collection are touched. The collection that comes with every collection trigger includes its rule set, so a workflow can report which conditions an automated collection has after an update.

Does Collection updated give the previous handle or title?
No. Shopify's help page says the trigger provides only the current values of the collection. Collection Handle Changed and Collection Title Changed carry the value before and after.
Can I run a workflow when a product is added to a collection?
Yes, with Flow's Collection updated trigger and its products field. It starts when a product is added or removed and hands the workflow the product. This app has no trigger that names the product.
How do I create a redirect when a collection is renamed?
Use Collection Handle Changed with the Create redirect URL action, from the old handle to the new one. The template Redirect old collection URLs when a collection handle changes is ready to install.
Can both run on the same store?
Yes. They do not interfere. A common split: Flow's trigger for products added or removed, this app for handle, title and description changes that need the old value.
Next steps
- Collection triggers, step by step - every collection trigger with an example.
- Old and new values: what a workflow can do with them - all values before and after, by trigger.
- Flow's updated triggers and Workflow Trigger Extensions - the overview of all nine updated triggers.
