Study guide

21.5 Integration Service Event Triggers: Connected and Disconnected

UiPath Automation Developer Professional UiPath-ADPv1

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Blueprint Map

1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan

2 Chapter 2: REFramework Architecture & State Dynamics

2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes

3 Chapter 3: REFramework Exception Handling & Recovery

3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination

4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing

4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues

5 Chapter 5: LINQ Queries & DataTable Operations

5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations

6 Chapter 6: Regex, DateTime, JSON & Invoke Activities

6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments

7 Chapter 7: Modern UI Automation & Unified Targeting

7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors

8 Chapter 8: Object Repository, Computer Vision & Remote Runtime

8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime

9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS

9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript

10 Chapter 10: Advanced Control Flow & Exception Architecture

10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures

11 Chapter 11: Orchestrator Queues & Transaction Management

11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers

12 Chapter 12: Orchestrator Tenant & Folder Entities

12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance

13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

14 Chapter 14: Monitoring, Recording & Solutions Management

14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources

15 Chapter 15: Debugging, Remote Debugging & Profiling

15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio

16 Chapter 16: RPA Testing & Test Suite

16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability

17 Chapter 17: Long-Running Workflows, Action Center & Apps

17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service

18 Chapter 18: Trigger-Based Attended Automation & Callouts

18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance

19 Chapter 19: UiPath Assistant & Robot Sessions

19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop

20 Chapter 20: Autopilot for Developers & Autopilot for Everyone

20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI

21 Chapter 21: API Automation & Integration Service

21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows

22 Chapter 22: Data Service, Context Grounding & Coded Workflows

22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services

23 Chapter 23: Integrated Scenario Practice

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

21.5 Integration Service Event Triggers: Connected and Disconnected

Key Takeaways Explain This Topic AI

An event trigger combines a connector, a connection, an event, and optional event filters.

Connectors detect events by polling, every five minutes by default, with the interval set per connection for all its triggers.

Connected triggers are created in Studio and appear as package requirements; disconnected triggers are created in Orchestrator.

Disconnected triggers pass UiPathEventConnector, UiPathEvent, UiPathEventObjectType, and UiPathEventObjectId as String arguments.

Managing event triggers needs Connections View and Resource overwrites permissions.

Last updated: September 2026

21.5 Integration Service Event Triggers: Connected and Disconnected

Core Concept: Event triggers start automations when something happens in another application, such as an email arriving in Outlook or a record being created in Salesforce. Integration Service detects these events, and Orchestrator starts the job. The exam description lists event triggers under API automation.

Anatomy of an Event Trigger

  • Part Example
  • Connector Microsoft Outlook 365
  • Connection john.smith@outlook.com
  • Trigger (event) Email received
  • Event filters Only the "Paychecks" folder of that mailbox

The available filter values depend on the selected connection.

How Events Are Detected: Polling

Connectors support events through a polling mechanism :

Integration Service queries the application's API at an interval, every five minutes by default .

The polling interval is set at the connection level, so changing it affects all triggers on that connection.

Expect a delay of up to the polling interval between the event and the job start.

In Integration Service, the only trigger setting you change is this polling interval; the triggers themselves are managed in Orchestrator.

Connected Versus Disconnected Triggers

Connected trigger Disconnected trigger

Created At design time in Studio , as the trigger activity that starts the project In Orchestrator , outside of any process

At deployment Appears as a package requirement when adding the process Attached to an existing process in Orchestrator

Event data in the workflow The full event object is available, because the workflow was designed with the trigger Only identifiers passed as arguments

Arguments for disconnected triggers

A process started by a disconnected trigger receives four String arguments:

  • Argument Contains
  • UiPathEventConnector Which connector started the automation
  • UiPathEvent The type of event
  • UiPathEventObjectType The record type involved
  • UiPathEventObjectId The unique ID of the record

Declare these as In arguments of type String. Use UiPathEventObjectId with a Get Record or HTTP activity to fetch the full record.

Permissions

Creating or editing an event trigger in Orchestrator needs:

Connections View , and assignment to the folder where the connection resides.

Resource overwrites permissions (View, Edit, Create, Delete) to use or configure a connection other than the one originally in the workflow, including per-user configurations.

Designing Triggered Processes

Filter early. Use the trigger's event filters so jobs start only for relevant events.

Keep the process idempotent. Polling and retries can mean a record is seen more than once; check whether the work was already done.

Fetch fresh data. Especially for disconnected triggers, read the record with its ID at the start of the job.

Log the event identifiers for troubleshooting.

Check the attempts history. Integration Service keeps an attempts history for each trigger, which shows whether an event was detected even when no job ran.

Event Triggers Versus Other Triggers

  • Trigger Starts a job when Latency
  • Event trigger Integration Service detects an application event Up to the polling interval
  • Queue trigger New items arrive in an Orchestrator queue Shortly after items are added
  • Time trigger A schedule is due By schedule
  • API trigger An external system calls the trigger's URL Immediate

Use an API trigger when the other system can call UiPath directly and you need an immediate start; use an event trigger when you only need to react to changes UiPath can detect through the connector.

Key Terms

Polling interval: how often Integration Service checks the application for new events; set per connection.

Event filter: conditions on the event, such as a mailbox folder or record type, that decide whether a job starts.

Package requirement: a connection or trigger a process needs, shown when the process is added in Orchestrator.

Resource overwrite: a replacement connection chosen for a process or user instead of the one used at design time.

Troubleshooting Event Triggers

The job starts minutes after the event: this is expected with polling; lower the connection's polling interval if the delay matters, remembering that it applies to every trigger on that connection.

No job started: check the trigger's attempts history , the event filters, and whether the connection is healthy or needs to be reconnected.

A disconnected trigger's process fails immediately: confirm the process declares the four UiPathEvent... arguments as String In arguments with the exact names.

Wrong mailbox or account in production: check the connection selected through Package Requirements or the resource overwrite for the process.

Worked Example: Supplier Invoices by Email

A connected trigger "Email received" on the AP team's Outlook connection, filtered to the Invoices folder and emails with attachments, starts the process.

The process saves the PDF attachments to a storage bucket and adds a queue item per invoice.

In test and production, the process uses different mailboxes; the connection is chosen per environment through Package Requirements .

The team lowers the connection's polling interval because invoices should be picked up faster, knowing this affects every trigger on that connection.