1. Help Center
  2. Automate workflow

Creating rules

How do I create notifications, alerts, tickets in CRM etc.?

Rules are made up of two components in DevicePilot:

  • A Trigger condition that needs to be met
  • An Action that will be performed

Trigger

Triggers can be either a Device Condition where a specific conditional statement is tested on each device (such as temperature greater than 5, or last seen more than 1 hour ago), or the trigger can be based on a KPI being evaluated (like Uptime per region is less than 90%, or average daily room temperature is less than 15)

Device Condition Triggers

Triggers can be simple condition such as

Temperature > 5

or they can be more complex and include multiple conditions, timeouts, etc.

RuleTrigger-1

You can add multiple conditions, and combine them with AND or OR.

The options are the same as Filters and in fact, you can copy an existing filter to make your condition.

Advanced: If you need more complex logic, switching to advanced mode will allow you to write the expression yourself.

DevicePilot creates two events: one for the trigger becoming true, and one for it returning to false, and you can attach actions to each of these.

KPI Triggers

You can also use a KPI to trigger actions. In this case, we will run the KPI periodically, and create an action for any row in the KPI result that meets a condition. For example, we might like to trigger whenever the uptime in a particular region falls below 90%.

To do this, we first build (or copy) the KPI we want, in the same way as we do in Cohort.

We then Run the KPI to get a preview of the results:

Based on these results, we can setup the trigger:

If run immediately, this would create a single action, for the Gujarat region.

Action

Actions are a single activity that can be performed, like sending a notification or creating a ticket in a CRM. DevicePilot has a number of built-in integrations, and further integrations can be built using our configurable webhook.

RuleAction