Automation

Automation rules let you trigger actions automatically when conditions are met. Notification actions (email, Discord, Slack, Telegram, webhooks) are available on all plans. Device commands and multi-condition rules require the Business plan or higher.

Creating a Rule

1. Go to Dashboard > Automation
2. Click New Rule
3. Configure the trigger conditions, actions, and cooldown
4. Click Create Rule

Trigger Conditions

Condition-Based

Fires when a device’s telemetry data matches one or more conditions.

Setting	Description
Device	The device to monitor
Field	The telemetry field to check (e.g., “temperature”)
Operator	Greater than, less than, equals, not equals, changed, etc.
Value	The threshold value

Example: “When temperature on Sensor A is greater than 38”

Multi-Condition Rules (Business+)

Business and Scale plan users can add multiple conditions with AND/OR logic:

• All conditions (AND) - Rule fires only when every condition is true
• Any condition (OR) - Rule fires when at least one condition is true

Free and Starter users are limited to a single condition per rule.

Action Types

Each rule can have multiple actions that execute simultaneously when triggered.

Notification Actions (All Plans)

Action	Description	Setup
Email	Sends alert to your account email	Automatic
Discord	Posts to a Discord channel	Webhook URL
Slack	Posts to a Slack channel	Webhook URL
Telegram	Sends message via Telegram bot	Bot token + chat ID
Custom Webhook	HTTP POST to any URL	Endpoint URL

See Alert Integrations for detailed setup guides for each channel.

SMS (Business+)

Sends an SMS to your verified phone number. Requires a Business plan or higher with SMS alerts enabled. Monthly limits: Business (100/mo), Scale (200/mo).

Send Command (Business+)

Sends a command to a device via MQTT. Configure:

• Target device - Which device receives the command
• Command name - The command identifier (e.g., “relay_on”)
• Value - The command value (e.g., “true”)

The command is published to the device’s command topic (d/{device_id}/c).

Automation Webhook (Business+)

Makes an HTTP POST request to a URL with the full trigger data as JSON body. Useful for integrating with external automation platforms like n8n, Node-RED, or Zapier.

Cooldown

The cooldown period prevents a rule from firing repeatedly. After a rule triggers, it will not trigger again until the cooldown expires.

Default: 300 seconds (5 minutes). Range: 10 seconds to 86,400 seconds (24 hours).

Managing Rules

Enable/Disable

Toggle the switch next to any rule to enable or disable it. Disabled rules are not evaluated.

Execution History

View the history tab to see when rules fired, which conditions matched, and which actions executed. Each entry shows success or failure status with timestamps.

Acknowledge Events

Mark triggered events as acknowledged to track which ones have been reviewed.

Edit & Delete

Use the edit and delete icons on each rule card.

Example Use Cases

Trigger	Action	Use Case
Temperature > 35C	Email + Discord notification	Critical temperature alert
Soil moisture < 30%	Send “valve_open” command	Irrigation control
Vibration > threshold	Webhook to maintenance system	Predictive maintenance
Power > 5kW	Send “reduce_load” command	Energy management
Humidity changed	Telegram notification	Environmental monitoring
Temperature > 40C AND humidity < 20%	SMS + email + command	Multi-condition safety alert

Plans & Availability

Feature	Free/Starter	Business	Scale	Enterprise
Single condition rules	Yes	Yes	Yes	Yes
Multi-condition (AND/OR)	-	Yes	Yes	Yes
Email notifications	Yes	Yes	Yes	Yes
Discord/Slack/Telegram	Yes	Yes	Yes	Yes
Custom webhooks	Yes	Yes	Yes	Yes
SMS notifications	-	Yes (100/mo)	Yes (200/mo)	Yes
Device commands	-	Yes	Yes	Yes
AI-suggested rules	-	-	Yes	Yes

Next Steps

• Alert Integrations - Setup guides for Discord, Slack, Telegram, webhooks
• Analytics & AI - Anomaly detection and forecasting
• Device Sharing - Share devices with your team