Skip to main content

Configuring Automation Actions

Learn how to customize automation actions to control what happens when your automations run.

Written by Ryder Catonio
Updated today

Overview

When an automation's trigger fires and all rules are satisfied, the defined action is executed. There are three action types available:

  • Send Notification – Notify users and contacts via email, SMS, or in-app messages

  • Create Work Order – Automatically generate a work order from a template

  • API Call – Send data to an external system via a URL endpoint

Each action type has its own configuration options and advanced settings described below.

Send Notification

The Send Notification action allows you to send a message to one or more recipients when the automation is triggered.

Message

Use the text editor to compose your notification message. You can format text, add links, and insert replacement tokens.

Replacement Tokens

Replacement tokens allow you to include dynamic values in your message that are automatically replaced with actual data when the notification is sent. For example, you could write "This asset was created by {Created By} on {Created Date}" and each recipient would see the real values when the message is sent.

To insert a replacement token:

  1. Type { in the message editor

  2. A dropdown will appear showing available tokens

  3. Select a token to insert it

Tokens are organized into two groups:

  • Headers – Standard fields such as Created By, Created Date, Project Name, or Asset Number (available fields vary by automation type)

  • Elements – Fields specific to the selected asset or task definition (only available for asset and task automations)

Inserted tokens appear as highlighted text in the editor. If you change the asset or task definition after inserting element tokens, any tokens that no longer match the new definition will be highlighted in red and must be removed or replaced before saving.

Recipients

Click Add Recipient to select Nektar users or enter external email addresses. For each recipient, you can enable or disable three notification channels:

  • SMS – Send a text message (only available for Nektar users, and requires SMS to be enabled in Company Settings)

  • Notification – Send an in-app message to the recipient's Message Center (only available for Nektar users)

  • Email – Send an email notification

Note: If SMS is enabled for any recipient, the message is limited to 500 characters.

Advanced Settings

Expand the Advanced Settings section to access additional options. Available settings vary by automation type:

Setting

Description

Available For

Add Originator to Recipients

Adds the user who triggered the event (e.g., the user who created the asset or task) to the recipient list.

Asset, Task, Work Order, User

Include Details in Email

Includes the full asset or task details in the email body.

Asset and Task

Include Trigger Details in Message

Includes generic information about the trigger event in the message.

All types

Note: Include Details in Email is only available when at least one recipient has email enabled.


Create Work Order

The Create Work Order action automatically generates a new work order when the automation is triggered.

Work Order Template

Select the work order template to use when creating the work order. The template defines the structure, fields, and default values of the generated work order.

Advanced Settings

Setting

Description

Available For

Add Originator to Follow List

Automatically adds the user who triggered the event as a follower on the created work order

Asset, Task, Work Order

Originator as Work Order Creator

Sets the user who triggered the event as the creator of the work order

Asset, Task, Work Order

API Call

The API Call action sends data to an external system by making a request to a specified URL endpoint when the automation is triggered.

URL

Enter the full URL of the external endpoint that should receive the data.

Note: Configuring API Call actions may require assistance from Nektar support to ensure proper setup and integration with external systems.

For an overview of how actions fit within the broader automation workflow, see Automation Manager Overview.

Did this answer your question?