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 — delete 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 report — Generates report files by capturing target dashboard with specific configuration.
- generator — generates messages at configurable time intervals using a custom script function.
- gps geofencing events — Produces incoming messages by GPS based parameters.
- integration downlink — Forwards Message to selected Integration as downlink message.
- 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 — The rule node applies math function and saves the result into the message and/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 messages from the edge instance to the cloud platform.
- push to edge — Sends messages from the cloud platform to an edge instance.
- remove from group — removes the message originator entity from an entity group found by group name pattern.
- rest call reply — Sends reply to REST API call that was originally sent to rule engine.
- rpc call reply — Sends response to the RPC Call originator.
- rpc call request — Sends RPC requests to the Device and routing response to the next Rule nodes.
- save attributes — Stores the incoming message payload as attribute data of the message originator.
- save time series — Stores the incoming message payload as time series data of the message originator.
- save to custom table — Node stores data from incoming Message payload to the Cassandra database into the predefined custom table that should have cs_tb_ prefix, to avoid the data insertion to the common TB tables.
- unassign from customer — unassigns the message originator from a customer.