Actions

When the conditions of a rule are met and an event is generated, one or more Actions can be taken to notify people, update systems or initiate processes.

Actions are highly flexible. You can use them to send alerts, push data into third-party services, or automate workflows.

How Actions Work

1. Asset Data Evaluated
   A rule evaluates incoming data or conditions.

2. Rule Matches
   If the conditions are satisfied, the rule generates an event.

3. Actions Taken
   The configured actions for the rule execute in order.

You can configure multiple actions for a single rule, and each action can be individually enabled or disabled.

Action Types

We provide a variety of built-in action types to cover common use cases:

• Email – Send a notification email to one or more recipients.

• SMS – Deliver a text message alert.

• Slack – Post a message into a Slack channel or direct message.

• Microsoft Teams – Post a message into a Teams channel.

• Webhook – Send a JSON payload to an external HTTP endpoint.

• Custom – Run a custom script or integration for advanced scenarios.

💡 Tip: You can add multiple action types to the same rule. For example, you might send an email to your operations team and post to a Slack channel at the same time.

Configuring an Action

Each action type comes with its own configuration options. For example:

• Email

  • Recipients (To)

  • Subject and body template

• SMS

  • Recipients

  • Message body

• Slack

  • Target channel or user

  • Message text

• Webhook

  • URL endpoint

  • HTTP method (POST, PUT, etc.)

  • Headers and payload

Advanced Options

Advanced options can be configured at the bottom of an action.

• Run When
  Each action supports an optional formula that determines whether it runs. For example, you might only send an SMS if the device temperature exceeds 100°F (see example image below)

  • If the formula evaluates to true, the action executes.

  • If it evaluates to false, the action is skipped.