- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read Only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
Event triggers represent the starting point of an automation, based on the occurrence of an external event, such as a new email arriving in your Outlook inbox. The events, filters, and connections available for trigger configuration are displayed in Integration Service.
Event triggers can be created either in Integration Service, or at design-time in Studio.
Learn more about Triggers in Integration Service.
An event trigger consists of:
a connector - the external application integrated in UiPath system (for example, Microsoft Outlook 365).
the connection - the authenticated user instance of the connector (for example, John.Smith@outlook.com).
the trigger activity - the activity that starts the automation (for example, When a New Email Arrives).
activity filters - filters used to add specificity for the trigger execution (for example, the "Paychecks" inbox folder of John Smith).
Note: The available filter values depend on the selected connection.
Roles and permissions for event triggers
To create or edit an event trigger, you need the following permissions:
|View||Connections||Allows you to see the list of available connections you can configure for your event trigger.
You also need to be assigned to the folder the connection resides in.
|View||Resource overwrites||Allows you to use the connection you want instead of the connection used originally in the workflow.
As a user, you can see what the admin configured for you.
|Edit||Resource overwrites||Allows you to edit the connection configuration for a specific user.
As an admin, you can set a specific connection for a specific user.
|Create||Resource overwrites||Allows you to configure the connection for a specific user.
For example, when you want to create custom user configurations for a process, or manage user event triggers.
|Delete||Resource overwrites||Allows you to delete a user-specific event trigger configuration.|
Event triggers created using UiPath Activities
Event triggers can also be created by RPA developers at design-time in Studio, using Integration Services trigger activities, such as the When New Email Arrives activity of the UiPath.MicrosoftOffice365.Activities.
Orchestrator identifies these types of triggers as package requirements, and the only way to add them in Orchestrator is from the Package Requirements page.
Any configuration set at design-time is reflected in Orchestrator and cannot be modified.
For example: Say you have an automation that automatically uploads attachments received in your "Paychecks" Outlook folder to your Google Drive "2023" folder. In this case:
the Microsoft Outlook 365 connection is your Outlook account and the recipient of the emails.
the event trigger activity is the mail arriving in your inbox.
the filter applied to the event trigger is folder "Paychecks" in your inbox.
the activity that downloads all new attachments in folder "Paychecks" operates for the same Microsoft Outlook 365 connection used to receive the emails. Orchestrator does not display this activity (Download Email Attachments), as it does not have any filters that can be overwritten. For it, the filters set by the RPA developer are final.
the Google Drive connection is your Google account and the recipient of the attachment uploads.
the filter applied to the uploading activity is the "2023" folder in Google Drive.