If you look at marketing focused services you will see a rule such as this one being requested.
Checking if another message was sent to that customer already, or not, is a very powerful tool for marketing.
Having a way to categorize workflows too, and checking of that particular category ran for the customer/order… would further this concept.
Seconded; much-inferior Follow Up Email plugin allowed me to exclude other emails/flows, and that would be very helpful here for decision tree-esque logic.
The idea is you could set up two workflows, X and Y, that have completely different triggers (that have access to customer details).
For instance, Workflow X could be a workflow that awards 10 points to a customer for bought a for a Product A.
Workflow Y, on the other hand, could have the trigger Order Refunded. It could have this rule to check to see if Workflow X has ever run for this customer. If it has, it would deduct 10 points for the refunded Product A.
This would prevent points being deducted from customers who may have purchased Product A _before_ Workflow X was created.
If you look at marketing focused services you will see a rule such as this one being requested.
Checking if another message was sent to that customer already, or not, is a very powerful tool for marketing.
Having a way to categorize workflows too, and checking of that particular category ran for the customer/order… would further this concept.
Marcy Capron Vermillion: Thanks for the feedback and for voting!
Just leaving another comment in support of this! It’s a basic logic option in all similar products — but we prefer Automatewoo!
Seconded; much-inferior Follow Up Email plugin allowed me to exclude other emails/flows, and that would be very helpful here for decision tree-esque logic.
The idea is you could set up two workflows, X and Y, that have completely different triggers (that have access to customer details).
For instance, Workflow X could be a workflow that awards 10 points to a customer for bought a for a Product A.
Workflow Y, on the other hand, could have the trigger Order Refunded. It could have this rule to check to see if Workflow X has ever run for this customer. If it has, it would deduct 10 points for the refunded Product A.
This would prevent points being deducted from customers who may have purchased Product A _before_ Workflow X was created.