Create an alerting rule
Rules watch a device tag and fire actions when a condition is met.
- Open Rules → New rule.
- Under Fire this rule when…, keep A reading crosses a threshold.
- Pick a device + tag, an operator (
gt,lt,gte,lte,eq) and a threshold. - Choose a severity and a cooldown (minutes) to avoid alert storms.
- Add one or more actions: in-app, email, webhook, or MQTT.
A rule can also fire on an event rather than a reading — when a job finishes, or a gateway drops offline. See rules that fire on an event.
Which action types you can use, and how many rules and monthly action-fires you get, depend on your plan. See plans & limits.
A rule can only do what you could do yourself
Creating, editing or switching on a rule needs Create rules / Edit rules / Toggle rules and the permission for each action the rule takes:
| Action in the rule | Also needs |
|---|---|
| Command a device or control an actuator | Command devices |
| Run a macro | Run macros |
| Fire a saved user action | Trigger actions |
| Start or end a job | Start/end jobs |
| In-app, email or push notification · webhook · MQTT | nothing extra |
So a member who can't send a device command can't write a rule that sends one for them either. Anyone with Toggle rules can always switch a rule off. An AI agent can only switch on a rule whose actions are all notifications (in-app, email, push); anything else has to be switched on by a person.