Hi y’all, Carolina from support here again!!
Today’s tip is for you who want instant automations when specific device variables arrive? Use an Action of type “Trigger by Variable.” When an incoming variable meets your condition (e.g., temperature > 95, status = “alarm”, battery between 20–30), TagoIO fires your chosen action automatically, for example: send an email/SMS, publish to MQTT, or run an Analysis for custom logic.
Pick the right scope!
-
Single device watches one device and is the only mode that supports Trigger Unlock (great for hysteresis: trigger high, unlock low).
-
Multiple devices listen to a fleet using tag-based selection, ideal for scalable monitoring. Multiple conditions use OR logic and still execute the action only once per event batch, clean and predictable behavior.
Use Trigger Unlock to stop unnecessary repeating alerts. After the first trigger, the action locks and won’t fire again until your unlock rule is met. Example: Trigger when temperature > 95; unlock when temperature < 90. This pattern delivers one alert per “overheat episode” and is only available for a single device.
Need richer rules? Point your Action to “Run Analysis” and handle scenarios, routing, or multi-device workflows in code. You can attach up to 10 Analyses; they run in parallel, and your Analysis receives context fields like _action_id, _action_type, _action_state, and _device_id (when device-triggered). Source: Running Analysis via Action
Practical ideas:
-
Safety: status = “alarm” → send SMS and email.
-
Maintenance: battery between 15–25 (by tags) → publish MQTT notification.
-
Control: temp > 95 → run Analysis to enqueue a device command.
I hope this tip helps some members of our community 
Cheers,