Platform · Alerts & Rules
Nobody watches a dashboard at three in the morning
Data that nothing reacts to is just history. Thinger.io rules watch every reading around the clock and act the moment a condition is met: an email, a webhook, an action on the device.
The problem
The data was on screen. Nobody saw it.
At 03:14 the tank is out of range and the dashboard says so, to an empty room. The rule is what tells somebody.
How it works
Anatomy of a rule
Every rule reads the same way: what to watch, when to fire, what to do about it.
The trigger: what it watches
FIG. 01Rules read live device resources or data already stored in buckets and properties. This one follows the level of Tank T-2.
The condition: when it fires
FIG. 02Confirmation keeps one noisy reading from waking anyone: the rule waits for a sequence of matches or a condition that holds. Each rule also sets a severity, from Critical to None.
The action: what happens next
FIG. 03Notifications go out through endpoint profiles you define once. Reminders repeat them while the alarm stays active, and normalization clears it once its clear conditions are met.
Actions
Where the reaction lands
Endpoints are the platform's outgoing integrations: named destinations that rules, geofences and devices can call.
Email, sent by the platform
The platform sends the message itself: your recipients, your subject, your body, with live device data filled in through template variables. No mail server to run.
- Recipients
- Subject
- Templated body
Telegram, in the team chat
A preconfigured endpoint posts straight to a Telegram bot, so alerts land in the group chat your team already has open on their phones.
- Preconfigured endpoint
- Telegram bot
Slack or Discord, in the channel
Point an HTTP endpoint at a Slack or Discord incoming webhook and alerts post to the channel your team already works in. The message is a template, so it carries the device, the value and the severity.
- Incoming webhook
- Templated message
HTTP, to any web service
A generic HTTP endpoint calls any web service: your backend, IFTTT, an SMS gateway or a device on another account. The request body is a template, so the payload arrives in the shape the receiver expects.
- Any web service
- Templated payload
Back on the hardware
The reaction can land back on hardware. Endpoints can call devices, and REST API calls or a Node-RED flow can write values to a connected device, so the answer to a burst is closing the valve, not just reporting it.
- Endpoint to device
- REST API
- Node-RED
THE NIGHT SHIFT, COVERED
In the field
What teams automate
Watch a signal, decide when it matters, tell someone. These are the rules the teams on our solution pages actually run.
Smart Water
Night flow that stays high
Leaks surface in the small hours, when legitimate use is at its lowest. The water team hears about it before the morning shift clocks in.
Smart Water solutionSmart Building
Hot water below the Legionella line
Legionella control comes down to keeping hot water hot. A loop that drifts is flagged the same day, not at the next monthly round.
Smart Building solutionSmart City
Technical rooms with nobody inside
Lamclima watches the technical rooms of Chile’s state railway network under its own brand. A failing climate unit rarely trips a breaker: it drifts, and the drift is the alarm.
Read the Lamclima storyFleet Tracking
Geofences around depots and routes
Zones drawn around depots, routes and restricted areas catch every entry and exit. An off-route vehicle is a notification, not a surprise at the end of the day.
Fleet Tracking solutionIndustrial IoT
Condition thresholds on the line
Condition rules catch failures while they are still trends. A disconnection rule does the humbler job: flagging the gateway that went silent before a whole line goes dark.
Industrial IoT solutionAgroTech
Frost nights and empty tanks
A frost alert reaches the grower while there is still time to act. The same rules warn before a tank runs dry and can pause irrigation when it rains.
AgroTech solutionBeyond thresholds
Node-RED for everything a rule cannot say
Some reactions are flows, not comparisons: correlate two devices before deciding, compute a derived value first, run a sequence of steps.
Platform events in
Start a flow when something happens, such as a device going offline.
Plant data in
Poll Modbus registers or subscribe to OPC UA servers.
Your logic
Correlate, derive a value, then decide with a switch.
Back to the platform
Store the result in a bucket and act on the device.
Out to other systems
Endpoint calls reach webhooks, email, SCADA, MES or ERP.
Thinger.io ships its own Node-RED nodes
Read and write devices, buckets and properties, listen to server events and call endpoints. Node-RED installs in one click from the plugins marketplace.
- server events
- device read
- device write
- device stream
- bucket read
- bucket write
- property read
- property write
- endpoint call
Put the platform on watch
Rules run on every dedicated Thinger.io instance, from the smallest plan up. Connect a device and write your first rule in minutes, and your team can stop staring at dashboards.