Skip to main content
All CollectionsAutomations
Automations Overview
Automations Overview

Each automation has three key sections

Martin Sawicki avatar
Written by Martin Sawicki
Updated over a week ago
  • Feature: Trigger actions for asset or task definitions.

  • Use: Improve productivity, avoid errors, and focus on high-value tasks.

What is an automation?

It's a process that runs without user input whenever data is created or updated.

Prerequisites

Users must have proper group-level permissions. To enable this feature, go to the side menu and select Manage > Permission Manager. Go to Menus > Web Menu > Manage and check the Automation Manager box.

Understanding automation components

Each automation has three main sections: trigger, rule, and action.

  • Triggers are changes to an element in an asset or task definition. The change can be new data created (e.g. a new task recorded) or existing data updated (e.g. a value in a field).

  • Rules (an optional but useful part of an automation) create conditions that must be true before the trigger generates an action. For example, if the fuel volume falls below 100 litres in a storage tank, the automation sends a notification to one or more users. If you have two or more rules, all the conditions must be true before the trigger generates an action.

  • An action is the outcome of an automation. There are three action types: send a notification, generate a work order, or call a webhook endpoint, which requires involvement from Nektar support.


Related articles

Did this answer your question?