Actions

When triggered, automation actions run to implement an appropriate notification or response action. Examples of automation actions include creating alerts, defining metrics, performing device operations, updating the device database and sending email notifications.

Automation actions respond to initiation by triggers and utilize the trigger context as parameters to tailor the action's execution.

Action Types

Type	Description
Builder Alert	Create an alert in the Builder account
Builder Metric	Create a metric in the Builder account
Database	Create, update or remove an item in the device database
Device	Perform a device operation: release or reboot
Manager Alert	Create an alert in the device manager account
Manager Metric	Define a device metric
HTTP	Invoke a HTTP REST API
Email*	Send an email message
Lambda*	Invoke a Lambda
MQTT Message*	Send an MQTT message
EventBridge*	Send an EventBridge event

The Email, Lambda, MQTT and EventBridge actions require a dedicated device cloud.

Some actions are configured with specific parameters. For example, an email action defines the email recipients, whereas an HTTP action defines the HTTP method, URL and HTTP headers. The action parameters are combined with the trigger parameters when the action is run.

Rearming Delay

After a trigger has been activated and an associated action has been run, it can be useful to suppress further actions for a period of time. The rearm delay can be one or more minutes to suppress further triggers from activating.

Enable

Actions can be enabled or disabled at any time.