Triggers tell your rule when it should start executing. You can think of a trigger as a “if” statement, in programming terms. There are many different triggers that you can use in Aitum, such as when a new person subscribes to your Twitch channel. Some triggers even allow you to be more granular through optional parameters, and create triggers such as “when this specific person subscribes to my channel”.
When you add a new trigger, you'll first be asked to choose a device that you have available. Then, you can select any of the “message types” that we support for that device. For example, if we picked Twitch as a device, we can pick “Follow” as a trigger. Once you select a message type that you wish to use, you can then fill in any of the required or optional fields. Keeping with our example, the “Follow” message type for Twitch has no required fields, so it could be used as-is. Or, we could specify a Twitch username that must follow us for the trigger to activate, and thus execute the rule.
Rules can have multiple triggers. The rule will then execute if any of its triggers happen. A rule without triggers is valid but will never execute unless manually triggered through our Elgato Stream Deck plugin, or public API. If your rule isn't working, a good first troubleshooting step is checking if your triggers are setup correctly.
You can duplicate a trigger by clicking the Duplicate button at the top right of the trigger. You can remove a trigger using the Delete button next to it.
The input fields inside triggers let you narrow down the incoming trigger data. For most triggers, these fields are optional, and the trigger would work without specifying any additional parameters. If you leave a field blank, the trigger will fire no matter what the value of that field is in the incoming data. If you do fill in a value the rule will only trigger if the value of the field in the incoming data matches value you entered.
Most trigger fields have a button with a gear icon to its left. Clicking this button will open additional settings for the field, noted below.
If the type of the field is Whole Number or Decimal, you can change the Input Mode from Normal to Range. If you select the Range mode, you can set a minimum and maximum value for the field, instead of an absolute value. This is useful when you have a trigger such as “Incoming Raid” from Twitch, as it allows you to set a range for the amount of viewers that would activate the trigger.
If you fill out the "At least" field, the trigger will only go through if the value is at least the one you set. The "At most" field works similarly, only triggering the rule if the value is at most the one set. You have the option of setting either one of the fields on their own, or combine them to only have the Rule execute if the incoming value of the field is between the two values set.
If a field is available as a local variable, you will be able to set a fallback value for the field. For example, if you use the field's local variable later on in the rule, but the rule is triggered by another trigger that doesn't have the field, it will use the fallback value. If you do not set a fallback value, an internal fallback value is used. This internal value is displayed in the field if you don't have a fallback value set.