Integration Service for Automation Suite User Guide

DELIVERY:

RELEASE: 2.2510

Last updated Nov 11, 2025

Triggers

Triggers provide a uniform mechanism for subscribing to events from the Connector platforms. It gives you the flexibility to automatically start automations or processes in Orchestrator.

Overview

There are two types of event triggers based on Integration Service connections:

Connected – Created with trigger activities in Studio, used inside a process.
Disconnected – Created in Orchestrator or Integration Service, used to start any automation.

Note: Triggers depend on connections. Deleting a connection also deletes all associated triggers.

Prerequisites

Before you can configure triggers, make sure the following conditions are met:

The Integration Service is enabled and provisioned for your tenant.
You have already setup an Unattended or Non-production Robot in your Orchestrator instance.
You are using modern folders (processes inside of classical folders are not visible when defining triggers).

Updating the polling interval

Connectors support events through a polling mechanism.

When you set up an event trigger on a connection, the polling interval is set by default to five minutes.

The polling interval is set at connection level. This means you can have only one polling interval per connection, even though you create several triggers per connection. Changing the polling interval affects all the associated triggers on a connection.

Polling runs on the connection at the selected interval. Once data has been retrieved, all active triggers for that connection are applied to the data set. If a poll is running when you change the interval, the service waits for the existing poll to finish, then starts another one.

To update the polling interval:

In Integration Service, go to the Connections tab.
Select a specific connection to open the connection details page.
The polling interval is displayed only for connections with added triggers.
Select the time interval to open the Update polling interval window.
You can choose one of the available options or set up a custom interval, in minutes or hours. The polling interval must be more than one minute and not longer than 24 hours or 1440 minutes.
Select Update and Check.

Viewing the trigger run history

To view the trigger run history:

In Integration Service, select the Triggers tab.
For any listed trigger, select View trigger using the More actions menu:

The Attempts' history table shows:

The event time – when the event was captured
The number of attempts
The trigger state – whether the process was successfully launched or not.

Note: The Successful state only indicates that the job was successfully launched. It does not reflect whether the job was successfully executed to the end or not. In case a job fails to start, its State will appear as Failed. Hover with the mouse cursor over the Failed state to view the error message.

To check if a job was successfully executed, select the View job logs button. This action redirects you to Orchestrator, where you can see all the necessary information on job execution.

Managing triggers

The following actions are available for triggers created in Integration Service.

Renaming a trigger

To rename a trigger, take the following steps:

Access the Triggers tab.
Hover with the mouse cursor over the name of the trigger you wish to modify. The Edit button is displayed.
Alternatively, you can select your trigger from the list to access the detailed view. The Edit button is located on the right side of your trigger name.
Select the Edit button and you can choose a new name for your trigger

Deleting a trigger

Go to the Triggers tab in the Integration Service window. Select the More Actions button corresponding to your trigger and select Delete.

Activating or deactivating a trigger

To activate or deactivate a trigger, you first have to select it to view its details. Then select the switch located in the upper-left side of the window.

Event arguments

Disconnected triggers allow you to retrieve data regarding the connector and event that triggers a process.

If you want to know the actual connector, event, record type, or record that triggered the process in your workflow, define the following input arguments of type String in your process. Integration Service populates them automatically when it starts the job:

UiPathEventConnector - Determines which connector started the automation.
UiPathEvent - Determines the type of event that occurred.
UiPathEventObjectType - Defines the specific record type resulting from the event.
UiPathEventObjectId - Provides the unique identified for the object involved in the event.

You cannot assign any value to these arguments. They are populated automatically at trigger execution time, and you are unable to view or edit them from the Arguments panel in Studio. Find out more about how Arguments work and how to manage them from the Studio documentation: Managing Arguments.

To retrieve and work with a record that has a trigger on a job run, use the UiPathEventObjectId input argument to retrieve the record from the source system.

Here is an example of how Integration Service passes the input argument values into Orchestrator logs:

Trigger-specific outputs

Connected triggers have object-specific outputs. For example, the Microsoft OneDrive & SharePoint Email Received trigger outputs an object of type Office365Message, with properties such as AttachmentsNamesList, FromAddress, InternetMessageId, SentDateTime etc. For details, refer to Microsoft OneDrive & SharePoint events.

Use the Expression Editor in Studio to view all available properties for any trigger output object.