- 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
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Connections
- About Connections
- Managing Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Starting with March 12, 2026, and as announced in the Release Notes, Integration Service connections must be created in Orchestrator.
The creation process remains identical when initiated directly from Integration Service, ensuring a consistent experience for all users.
This move brings several key advantages:
-
Less context-switching
You can now create assets, queues, triggers, and connections all in one place, without navigating to another left-hand menu. Fewer clicks, fewer page loads, and lower cognitive load lead to a smoother workflow.
-
Easier troubleshooting
When runs fail, you are already in Orchestrator reviewing jobs, queues, or logs. You can now view and manage the related connection in the same interface, reducing time to resolution.
-
A consistent mental model
Orchestrator already centralizes your resources. Managing connections alongside assets and triggers ensures a more intuitive and cohesive experience.
A connection is a reusable, governed authorization to an external application, created through a specific Connector.
It securely stores the required identity or credentials, such as OAuth tokens or API keys, and manages their lifecycle.
Connections are used across the UiPath platform, including in workflows, triggers, activities, and agents, to call that application’s APIs.
The following table describes the fields available on the Connections tab:
| Field | Description |
|---|---|
| Connection name | The name of the connection. The default name is the connection account. This field is editable by the user. |
| Connector | The name of the connector used to create the connection. |
| Connection account | The identifier used for creating the connection. Typically, this is the account or username. This field is read-only. |
| Authentication type | The authentication type used to create the connection. The
possible options are:
Note:
Available options may vary depending on the connector. This field cannot be changed once the connection is created. |
| Status | The status of the connection. The possible options are:
|
| Polling frequency | How often the system checks an external application for updates or new events. |