Triggers are actions which compares the content of a field from an incoming event with predefined rules, when the rules match, an event emit is triggered. Triggers in Tines are your automation's starting point, the digital equivalent of saying "when this happens, do that."
Some common use-cases for the Trigger Action include:
Ignoring Events that don't require processing
Send Events downstream for additional analysis
Further process events that are sent from a particular application
Multiple rules
A trigger with multiple rules acts in an AND fashion. All rules must be satisfied for the action to work. You can use “must match” in an individual trigger action to specify “OR” For example, using must match 1 acts as an OR.
If you have multiple rules as part of a Trigger action, they are not checked in any particular order. By default, all rules must match for the action to emit an event. If you wish to match only a subset of the rules, for example, two of three rules, you can set that value in must_match.
No match
If instead of halting the story run you'd like to redirect it depending on a rule, you can use the no match branch to send the story in a different direction depending on the result. This is a useful pattern, equivalent to an "if/else" flow in a software language.
👉 Learn more about triggers here.