ExamFinch.com My Study

Study guide

21.1 Integration Service: Connectors, Connections & Connector Activities

Practice this exam

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.1 Integration Service: Connectors, Connections & Connector Activities

Key Takeaways Explain This Topic AI

A connector packages an application API as activities and triggers; a connection is an authenticated, folder-scoped link to one account.

Since March 2026 connections can be created in the Orchestrator folder Connections tab, which requires Connections - Create; the Integration Service tab is scheduled for migration around July 2026.

Keep personal-account connections in Personal Workspaces and service-account connections in shared folders.

Per-environment connections are selected for a process on Orchestrator's Package Requirements tab.

A connector's HTTP Request activity calls endpoints without a dedicated activity using the connection's authentication; Private (Relay) connections reach private HTTP-based systems.

Last updated: September 2026

21.1 Integration Service: Connectors, Connections & Connector Activities

Core Concept: Integration Service lets automations work with other applications through their APIs. A connector packages an application's API (for example Salesforce, Microsoft 365, or ServiceNow) as activities and triggers. A connection is an authenticated link to one account of that application. The exam's API automation topics build on these two ideas.

Connectors, Connections, Activities, and Triggers

  • Building block What it is
  • Connector A prebuilt integration for one application, with its authentication options, activities, and events

Connection An authenticated link created when a user signs in to the application's API; it stores the tokens so workflows don't

Connector activities Studio and Studio Web activities that use a connection, such as sending an email or creating a record

Triggers Events from the application, such as a new record, that start automations (covered in the event triggers section)

Creating Connections

Where: In Orchestrator , open a folder and select the Connections tab, then Add connection , pick the connector, choose the authentication type, and select Connect . You can also create connections directly from Studio, Studio Web, or Assistant.

Change in 2026: Starting March 2026, new connections can be created in Orchestrator. Existing connections stay visible on Integration Service's Connections tab until July 2026 (subject to extension), when they are migrated to Orchestrator and that tab is removed.

Permission: creating a connection requires Connections - Create in the target folder.

Firewall: an IP allow list for Integration Service must be configured.

Authentication types

Some connectors support several; the options can include OAuth 2.0 Authorization code , OAuth 2.0 Password , Bring your own OAuth 2.0 app (your organization's own OAuth app instead of UiPath's public app), and Personal Access Token . Options vary by connector.

Shared connections and personal workspaces

A connection in a shared folder can be used, and edited, by everyone with access to that folder.

UiPath recommends creating connections authenticated with personal accounts in Personal Workspaces , and using shared folders only for connections authenticated with service accounts .

Administrators can prevent regular users from creating shared connections in team folders.

Private systems: Relay

For systems in a private network, a connection can use Private (Relay) instead of Standard , routing traffic through your own infrastructure without a VPN or inbound firewall changes. An administrator must configure Relay first, and you provide the Base URL . Only HTTP-based connectors support it; Snowflake and Database Hub (JDBC), SAP BAPI (SAP Java Connector), and Oracle NetSuite (SOAP) do not.

Managing connections

The Connections tab shows each connection's health and lets you reconnect , manage triggers, edit the name and polling interval , and delete connections.

One Workflow, Several Environments

All connectors support choosing the connection at run time:

Create a named connection per environment with the same connector, for example Salesforce Dev , Salesforce Test , and Salesforce Production .

Place each one in the Orchestrator folder of its environment.

In Orchestrator, use the process's Package Requirements tab to choose which connection the process uses.

The published automation then uses the connection assigned for that folder, with no workflow change.

Using Connectors in Automations

Connector activities: add an activity such as a Microsoft 365 or Salesforce activity, select the connection , and fill in the fields the connector exposes. The connector handles authentication and token refresh.

HTTP Request inside a connector: connectors also offer an HTTP Request activity for API endpoints that have no dedicated activity. It calls the vendor's API with the connection's authentication , so you only supply the method, path, and body.

Coded automations: services that use connections, such as Gmail, Google Sheets, Excel, OneDrive, and Office 365 mail, reach them through the connections object, for example connections.Gmail.My_Workspace_john_doe_gmail_com . The connection can be overridden in Orchestrator after publishing.

Orchestrator connector: the UiPath Orchestrator connector offers activities such as Get Asset, Get Credential, Get Queue Items, Run Job, and a UiPath Orchestrator HTTP Request activity.

Choosing an API Approach

  • Need Best tool
  • The application has a connector and the operation has an activity Connector activity

The application has a connector but not this operation The connector's HTTP Request activity, reusing its connection

The application has no connector, but a REST API Connector Builder to build one, or a plain HTTP Request activity with your own authentication

  • A fast, headless sequence of API calls An API workflow in Studio Web
  • React to events in the application Integration Service triggers
  • Common Traps

A connection belongs to a folder ; it is not global to the tenant.

Do not put personal-account connections in shared folders.

Environment differences belong in connections chosen through Package Requirements , not in duplicated workflows.

Private (Relay) works only for HTTP-based connectors.