Automations
Flows that watch your equipment and act: alert someone, switch something, call another system. Built on a canvas, step by step.
Create one
Each device has its own flow. Open Automations in the sidebar and choose New automation to pick a device, or open a device and use its Automations tab. Start from a blank canvas or a template, add steps with +, connect them, and save. A flow runs only while it is switched on.
Templates
- High reading alert, without the flood
- Device offline alert
- Tank pump control with hysteresis
- Daily report at 08:00
- Webhook controls a device
- Out-of-hours escalation
- Store only meaningful changes
Triggers
| Trigger | Starts the flow when |
|---|---|
| When pin reports | A datastream on the device reports a value |
| On a schedule | A set time arrives, in the time zone you choose |
| When device goes offline | A device stops reporting, or comes back |
| When a webhook is called | Another system calls the flow's own URL |
| Run manually | You press Test |
| When called by another automation | A Run automation on device step on another device starts it |
Steps
| Group | Steps |
|---|---|
| Logic | If, Compare, Threshold, Route by value, Time window, Merge |
| Data | Calculate, Set fields, Set variable, Counter, Write to datastream |
| Flow control | Rate limit, Debounce, Only on change, Wait, Timer |
| Actions | Set pin, Send alert, Send email, Call a phone, Send a text, HTTP request, Call webhook, Run automation on device |
| Integrations | Telegram, Slack, Discord, WhatsApp |
| Advanced | Code, Debug |
Set pin can switch this device or another device of yours. Send email goes to the account owner. Call a phone and Send a text reach only phone numbers verified on your account. Code runs your JavaScript in a sealed sandbox with short time and memory limits.
Using values in steps
Text fields can include values from the run:
{{ value }}: the value that reached this step.{{ json.field }}: a field of structured data, such as a webhook body or an HTTP response.{{ vars.name }}: a variable saved by Set variable, kept between runs.
Test, then switch on
Test runs the saved flow from any trigger, with a value or a JSON body you type. Test runs do not change live variables or counters. When it does what you expect, switch the flow on.
See why it ran, or did not
The Runs panel lists every run with each step it took, and replays the path on the canvas. A step that stopped the flow says why, for example 18.4 is not > 40. That sentence is usually the whole investigation.
Credentials for other services
Bot tokens and webhook secrets for Telegram, Slack, Discord and WhatsApp are saved once as credentials and picked by name in a step. They are stored sealed and never shown again, not even to you.
Run history
Successful runs are kept for 7 days and failed runs for 90 days. Run counts and durations behind the charts are kept much longer, so history charts do not change when old runs are cleared.
Something unclear or out of date on this page? Tell support.
