Why don't have "product updated" trigger?

That’s a real question; I’d like to understand why this trigger doesn’t already exist in Shopify Flow. It’s sorely missed in some cases.

Hi @Diego_Alves,

While we can’t discuss internal platform design decisions publicly, I can confirm that this is expected behaviour that the products/update event is not available as a Shopify Flow trigger.

I do know that this is a commonly requested feature, and I will be submitting feedback on your behalf as well that you would like to see this trigger available in the Shopify Flow app in the future. While we can’t guarantee when or if it will be added, I can assure you our developers and product managers do take all of our merchant and partner feedback into great value when determining future updates and changes to the platform.

In the meantime, I may recommend utilizing Webhooks to get notified of product updates, with the products/update webhook topic.

Alternatively, there are some other Shopify Flow triggers that may help with your workflows:

1 Like

If you don’t mind using third-party apps, the Flow Companion app provides a set of triggers that start when a product is updated: Product tags added, Product tags removed, Product field changed, Product variant field changed, Product metafield changed, Product variant metafield changed.

For these triggers to work, you need to configure the fields whose value changes you want to track in the app settings.

1 Like

Hi @Diego_Alves,

As @Yuri_K mentioned above 3rd party apps would definitely work to add this trigger as well, with existing apps like the Flow Companion app shared, or you can create your own Shopify Flow Extension app to add any triggers you like.

2 Likes

That’s really a significant limitation.

I guess, the most obvious reason is to avoid infinite’ish loops without proper planning.
Product updated → do something to product → product updated again.
Say, price updated → add a tag → product updated fires again.

For slow tasks you can work around by using scheduled flow and action “get products” updated since the last run.

2 Likes

You understand my question hahaha I know how bypass this problem, but the reason is obscure for me and your point make sense. But in N8N we have this trigger and works very well.

1 Like

I guess if we had some kind of “terminate running flow” or “Limit execution time for flow”, that would be really helpful.

1 Like

You can use “scheduled time” as the trigger with a recurring schedule, and pair that with “Get product data” or “Get product variant data”. That limits the impact of infinite loops and high volume.

2 Likes