Learn how to define specific trigger conditions based on custom event grammar.
order.created
order.item.added
order.payment-method.confirmed
order.shipping-method.added
order.complete
expect
an order.complete
eventafter
an order.created
eventfor_each
user iduser_id
as a parameter to the deployment.
expect
and after
fields accept a set
of event names, so you can specify multiple events for each condition.Similarly, the for_each
field accepts a set
of resource ids.user_id_1
creates and then completes an order, triggering a run of our deployment.user_id_2
creates an order, but no completed event is emitted so no deployment is triggered.