Skip to main content

Automation Manager Overview

Learn about Automations and how to create Automation Definitions

Ryder Catonio avatar
Written by Ryder Catonio
Updated yesterday

Overview

Automation Manager allows you to automatically trigger actions based on specific events in the system. When a defined trigger occurs, the automation executes actions such as sending notifications, creating work orders, or making an API call. This helps reduce manual work and ensures important events are handled consistently and in real time.

Note: Ensure the feature is enabled before continuing. Navigate to Permission Manager and enable the Automation Manager page under Menus → Manager → Automation Manager.

Understanding Automation Components

First, begin by navigating to Manage from the left-hand navigation bar. From there, select Automation Manager.

Once on the Automation Manager page, you will see the Automation Manager navigation panel on the left-hand side. From this panel, you can create either Automation folders (to help organize your automations) or a new Automation Definition.

To create an automation definition click the + button in the automation manager navigation panel

The General section contains the basic details of the automation:

  • Automation Title – The name of the automation for easy identification.

  • Folder – Used to organize automations within Automation Manager.

  • Notes – Optional details describing the purpose or behaviour of the automation.

The Trigger defines what event starts the automation. First, select the trigger category:

  • Assets

  • Tasks

  • Work Orders

  • Users

  • Geofences

Next, select the corresponding type:

  • Asset Definition (for Assets)

  • Task Definition (for Tasks)

  • Work Order Template (for Work Orders)

  • Permission Group (for Users)

  • Geofence Definition (for Geofences)

You will then choose the specific trigger type (for example, created, updated, entered, exited, etc.)

The Rules section allows you to filter when the automation should execute. The automation will only run if the defined conditions evaluate as true.

Rules can be based on header-level data (such as Project or Created Date) or specific element fields associated with the selected trigger type. This ensures automations only run under the exact conditions you define.

Lastly, the Action section defines what happens when the trigger and rules are satisfied. Available actions include:

  • Send Notification – Notify recipients by adding Nektar users or email addresses. For each Nektar user, you can choose whether they receive SMS messages, emails, or in-app messages (Message Center).

  • Create Work Order – Automatically generate a work order using a selected work order template.

  • API Call – Send data to an external system by specifying a URL endpoint (requires involvement from Nektar support)

Additional action customization can be found within Advanced Settings

Did this answer your question?