Action nodes are the execution components of ThingsBoard’s rule engine that perform concrete operations and side effects based on the messages flowing through the rule chain.
These nodes can automate various system operations like persisting time series and attributes to the database, managing alarms, controlling device commands and modifying system state.
Action nodes allow you to automate your workflows by executing operations based on your data without requiring manual interaction.
- assign to customer — assigns the message originator to a specified customer.
- add to group — adds the message originator to the entity group found by group name pattern.
- calculated fields — triggers calculated field processing for time series or attribute data without persisting the original data to the database.
- change owner — changes the ownership of the message originator to a specified tenant or customer.
- clear alarm — clears existing active alarms for the message originator.
- copy to view — replicates attribute changes from assets/devices to their associated entity views.
- create alarm — creates new alarms or updates existing active alarms for the message originator.
- create relation — creates relation between the message originator and a specified target entity with configurable direction and type.
- delay (deprecated) — delays incoming messages for a configurable period before forwarding them to the next rule node.
- delete attributes — deletes specified attributes from message originator.
- delete relation — deletes the relation from the selected entity to originator of the message by type and direction.
- device profile — evaluates incoming messages against alarm rules defined in the device profile of the message originator and creates, updates, or clears alarms based on the evaluation results.
- device state — sends device connectivity events for the message originator.
- generate dashboard report — generates a screenshot of a dashboard with specific configuration applied.
- generate report — generates a report based on a report template and sends notifications to configured targets.
- generator — generates messages at configurable time intervals using a custom script function.
- gps geofencing events — monitors GPS coordinates against polygon or circle geofences and routes messages based on entry, exit, and presence duration events.
- integration downlink — pushes the incoming message as a downlink message to a selected integration.
- log — executes a user-defined script to transform message data, metadata, and type into a custom formatted string and logs that string to the ThingsBoard log file.
- math function — performs mathematical operations on numeric data retrieved from multiple sources (constants, message, metadata, attributes, or time series) and saves results to the message or database.
- message count — counts incoming messages over a specified time interval and outputs a message containing the count for each interval.
- push to cloud — sends the incoming message from ThingsBoard Edge instance to cloud ThinsBoard instance for further processing.
- push to edge — sends the incoming message from cloud ThingsBoard instance to ThinsBoard Edge instance for further processing on Edge.
- remove from group — removes the message originator entity from an entity group found by group name pattern.
- rest call reply — sends the incoming message data as an HTTP response to a REST API call made to the rule engine.
- rpc call reply — sends the incoming message data as a reply to a Remote Procedure Call (RPC) from a device.
- rpc call request — sends an RPC to a device, returning the device’s response as outgoing message data.
- save attributes — stores the incoming message data as attribute data of the message originator.
- save time series — stores the incoming message data as time series data of the message originator.
- save to custom table — stores the incoming message data in a custom Cassandra table.
- unassign from customer — unassigns the message originator from a customer.