Actions effect

The Actions effect allows you to automatically run Actions when an automation triggers or recovers.

Configuration

To set up an Actions effect, begin by opening the automation configuration wizard. On the Effects page, add an Actions effect; this will take you to the Actions effect configuration page. One Action will already be added by default under Configured Actions and will be displayed as Unconfigured.

Starting with this unconfigured Action, you can begin configuring your Action. First, search and select the Action that you want to execute. The interface will display the parameters required by the selected Action, as shown in the image below. If the parameter type is supported, you can directly provide a value in the UI.

To add more Actions, select the Add Action button. This will add another tab allowing you to configure a new Action. Note that the execution sequence is not guaranteed when multiple Actions are configured; Actions may be executed in any order.

Use condition effect inputs

Some object set conditions expose effect inputs. These can be used in the Actions effect. To use condition effect inputs, the type of the Action parameter needs to align with the type of the exposed condition effect input. For example, if an effect exposes a single object of type Alert, the Action needs to take an object reference parameter of object type Alert.

In the example shown below, an object added to an object set condition exposes an effect input for an object set of type Support Ticket, because the condition uses batched execution mode. Because the selected Close Support Tickets Action expects an object set parameter of type Support Ticket, the condition effect input New Support Tickets added is a selectable option.

Action visibility settings

Not all Actions may be appropriate to use with Automate. You can disable an Action from being usable in Automate once you configure the action type in the Ontology Manager. After creating an Action type, view its details by clicking on the action type from the Action type list, then click on the Security & Submission Criteria tab in the left side panel. Then, find the Frontend consumers section and toggle off the switch that allows Automate to submit the Action.

Permissions

Actions are associated with the owner of an automation. This means that the Action will be run on behalf of the owner of the automation. That requires that the owner configuring an Action must pass the submission criteria for that Action.