1.) Yes, the flow works whenever the event occures.
2.) Yes, the workflow works when something is true.
3.) You can use the below workflow available on SS
4.) Yes, the flow will only apply for future inventory and all the apps works similarly because we can’t be able to check the events happened in the past.
Additonally, the flow doesn’t gets stop working automatically. There must be some reason to to get deactivated.
@QDD Whenever Product is created, the flow checks if collection title is equals to Best Collection ever and if it is equals than the Product tag is added FlowSucks
@QDD Yes, it will apply to new inventory. As I said the code can’t be able to check the past events. I hope you understand. There is no history available for the flow to run it.
@QDD Can you please confirm the Product created means whenever product is added? Like there are various things like Varient is added or Product is back in stock. I just want to confirm.
Im all for letting experts flex their muscles and show everyone what they know, but time and time again the experts change the game and answer a question they know the answer to. I’m not trying to argue or make anyone look foolish.
I’m trying to give you a chance to show people what you know.
@QDD I didn’t understood. I think the flow works according to your requirement right? The only thing you need to change is includes instead of is. I hope you understood what I was saying.
Check to see if it meets the criteria for this collection, “Best Collection Ever” – If you won’t add the collection manually? Why it would check that the product exist in Best Collection Ever if you won’t add it to any collection?
Or, you can use a scheduled time trigger, which can run your workflow on a single or recurring schedule. WIth that, you would need to use “Get product data” or “Get product variant data” to fetch the resources you care about.
There are templates available in Flow’s template library that show these patterns.