- About this guide
- Getting started
- Installing
- Upgrading
- Connecting and licensing
- Configuring
- Running workloads
- RPA processes and tests
- Agents, functions, and API workflows
- Limits
- Securing and governing
- Monitoring
- Troubleshooting
- Reference
Connecting the Robot to Orchestrator
Connect UiPath Robot 2026.10 to Orchestrator with the connection methods that apply to attended and unattended robots.
A robot runs jobs only after it connects to Orchestrator. How it connects depends on who runs the automations: a person signs in, or the machine authenticates with client credentials from its machine object.
| Connection method | Attended robots | Unattended robots |
|---|---|---|
| Interactive sign-in, with the Service URL in Assistant | Recommended | For troubleshooting only, from a user session on the machine |
| Client credentials in Assistant | Supported | Supported |
| Client credentials in the command line | Supported | Supported. Recommended for scripted setups. |
Client credentials are the recommended way to connect a robot. Machine key connections are deprecated. Robots connected with a machine key still run RPA processes and test cases, but by default they don't run agents, functions, or API workflows.
Client credentials, a client ID and a client secret, come from the machine object or machine template in Orchestrator. For how to create one, refer to Managing machines.
When the robot connects, it takes the runtimes and slots of its machine object, and reports which workloads it can run.
Client credentials and machine keys
A machine key connection uses a token that never expires. Wherever the key is copied, it keeps granting access to Orchestrator for as long as the key is valid. Client credentials use the OAuth 2.0 framework instead: the robot exchanges its client ID and client secret for an access token that expires, and authenticates as itself, not as a user.
| Property | Client credentials | Machine key |
|---|---|---|
| Token | An access token that expires, issued by Identity Server | A token that never expires |
| Agents, functions, and API workflows | Supported | Not supported |
| Status | Recommended | Deprecated. When the robot connects, the Robot log and Assistant show a deprecation message that asks you to reconnect with client credentials. |
With client credentials:
- The robot authenticates with its own identity, and Orchestrator checks that the robot itself is authorized for each action.
- To revoke a machine's access, delete the client secret it uses. Machines that use another secret of the same client ID keep their access.
- To rotate a secret, add a new secret to the machine object, deploy it to the machines, then delete the old one.
A client secret is shown only once, when Orchestrator creates it. Store it in a secure location, such as a secrets vault, and record its Secret ID, which is how you find the secret later to delete it. For details, refer to Robot authentication with client credentials.
Moving from a machine key to client credentials
Moving a robot from a machine key to client credentials is a change you make on each machine. Orchestrator doesn't switch connected robots for you.
- In Orchestrator, open the robot's machine object or machine template, and copy its client ID.
- Add a client secret, and copy it.
- On the machine, disconnect the robot from Orchestrator. To connect with different credentials or to a different Orchestrator, disconnect first.
- Connect it again with the client ID and the client secret, in Assistant or with the command line.
The robot connects with an expiring token, and can now run agents, functions, and API workflows. Because the client credentials belong to the same machine object as the machine key, the machine keeps its runtimes, folder assignments, and job history.
To move many machines, run the two commands on each machine from your deployment tool:
UiRobot.exe disconnect --wait
UiRobot.exe connect --url https://cloud.uipath.com/<Organization_Name>/<Tenant_Name>/orchestrator_ --clientId <Client_ID> --clientSecret <your-client-secret>
UiRobot.exe disconnect --wait
UiRobot.exe connect --url https://cloud.uipath.com/<Organization_Name>/<Tenant_Name>/orchestrator_ --clientId <Client_ID> --clientSecret <your-client-secret>
The --wait option lets running jobs finish before the robot disconnects.
After every unattended robot in the tenant uses client credentials, you can set robot authentication in Orchestrator to Client Credentials, which accepts only tokens that expire. For the options, refer to Robot authentication.
Connect at install time
The UiPath Platform Installer can connect an unattended robot while it installs it. Enter the Service URL, Client Id, and Client Secret in the Robot settings, or set SERVICE_URL, ORCHESTRATOR_CLIENT_ID, and ORCHESTRATOR_CLIENT_SECRET in a silent installation. Connecting at install time with a client ID and secret works only for a per-machine installation with the Unattended robot type (REGISTER_ROBOT_SERVICE=true). The Service URL, the client ID, and the client secret are all required. The connection is best effort: after installing, check that the robot is connected in Assistant or on the Orchestrator Machines page. For details, refer to Silent installation.
For Entra ID accounts with multifactor authentication on unattended robots, refer to Using EntraID users with multifactor authentication.