UiPath

UiPath is a robotic process automation tool for large-scale end-to-end automation. It monitors user activity to automate repetitive front and back office tasks, including those performed using other business software such as customer relationship management (CRM) or enterprise resource planning (ERP) software.

In order to integrate UiPath with Relyance AI you will need an App ID, App Secret, Organization Name, and Tenant Name.

In UiPath:

1. Login to your UiPath account.
2. Click on the Admin menu found in the top left-corner Bento menu.
3. Select External Applications from the page selections.
4. Click the Add Application button.
5. Create an application with the following settings: Application Name: Provide a meaningful name Application Type: Confidential application Scopes: Platform Management PM.Group.Read PM.User.Read PM.Group.Write* PM.User.Write* (* For DSR-enabled integrations.) Orchestrator OR.Folders.Read OR.Queues.Read OR.Tasks.Read OR.Users.Read Redirect URL: https://root.relyance.ai/api/oauth2
6. Click Add.
7. Once you add this application, you'll get a dialog box with your App ID and App Secret. Copy these down to be used in Relyance.
8. You should now see your newly created Application in the UI.
9. On the application has been added, go to the top right-hand corner profile dropdown and select Preferences.
10. On the General page, you'll find your Organization Name.
11. On the Privacy & Security page, you'll find your Tenant Name.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the UiPath integration card and click it to open its connections.
6. Under Authentication Method, choose Oauth2 / App Token.
7. Paste the App ID, App Secret, Organization Name, Tenant Name into their respective fields.
8. If this integration is to process data subject requests, ensure the Process DSARs checkbox is selected.
9. Click Authenticate.
10. At this point, you should see the following result on the Vendor Integrations page:
11. Congratulations, you are now connected to UiPath.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs PM.Group.Read, PM.User.Read, PM.User.Write. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. A credential rotated at the vendor is not picked up here. App Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example uipathinc/<connection_id>) or reading it with the relyance_integration_connection data source.