orchestrator
latest
false
- Getting started
- Best practices
- Tenant
- 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
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Automation Suite Robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Last updated Apr 16, 2026
Event triggers
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.
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, [email protected]).
- the trigger - the activity that starts the automation (for example, Email received).
- event 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.
There are two types of event triggers:
- Connected triggers: You create this type of trigger at project design time, in Studio. When you deploy a process in Orchestrator, any connected trigger associated with the underlying project appears as a package requirement during the Add Process workflow. For information on configuring a connected trigger, refer to Configuring connected event triggers.
- Disconnected triggers: You create this type of trigger in Orchestrator, outside of a process. For further information on disconnected triggers, refer to Creating a disconnected event trigger.
Roles and permissions for event triggers
To create or edit an event trigger, you need the following permissions:
| Permission | Permission Set | Description |
|---|---|---|
| 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. |