UiPath Cloud Integration
Connect UiPath Automation Cloud: External Application or User Key setup, folder selection, and data sync
Connect your UiPath Automation Cloud instance to RPA Watch. Two authentication methods are supported: External Application (recommended) and User Key.
Prerequisites
- A UiPath Automation Cloud account
- Organization name and tenant name from your UiPath instance
- An External Application or User Key configured in UiPath
- Account Admin or Tenant Admin role in RPA Watch
Authentication Methods
External Application
External Applications use the OAuth 2.0 client credentials flow. This is the recommended method for production use.
1. In UiPath Automation Cloud, go to Admin → External Applications
2. Click Add Application
3. Set the application type to Confidential
4. Add the required scopes:
- OR.Folders.Read — Read folder structure
- OR.Execution.Read — Read job executions
- OR.Robots.Read — Read robot information
- OR.Jobs.Read — Read job details
- OR.Monitoring — Monitor processes
5. Note the App ID (Client ID) and App Secret (Client Secret)
Configuration in RPA Watch
1. Navigate to Account Settings from the sidebar
2. Select UiPath as your RPA tool
3. Fill in the configuration:
| Field | Description | Example |
|---|---|---|
| Base URL | UiPath Cloud URL | |
| Organization Name | Your UiPath org name | mycompany |
| Tenant Name | Your UiPath tenant | DefaultTenant |
| Client ID | App ID or Client ID | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| Client Secret | App Secret (External App only) | xxxxxxxxxxxxxxxx |
| User Key | User Key (User Key method only) | xxxxxxxxxxxxxxxx |
| Folder IDs | Optional — comma-separated folder IDs to scope sync | 12345,67890 |
4. Click Save
5. Click Test Connection to verify
> Note: Fill in either Client Secret (External App) or User Key — not both. RPA Watch detects the method automatically.
Folder Selection
UiPath organizes processes into folders (Modern Folders). By default, RPA Watch syncs data from all accessible folders.
To limit the sync to specific folders:
1. In the configuration, enter comma-separated Folder IDs
2. You can find folder IDs by clicking Fetch Folders in the account settings
If no folder IDs are specified, all folders the application has access to will be synced.
What Gets Synced
Processes (Releases)
RPA Watch syncs both Releases (classic folders) and Processes (modern folders):
- Process/release name, key, and version
- Deduplication across folders (same process in multiple folders appears once)
- Processes removed from UiPath are soft-deleted
Robots
- All robots and machines from UiPath
- Robot name, type (Attended/Unattended), machine name, and description
- Robots are tagged with rpa_tool: uipath for identification
Jobs
UiPath jobs are mapped to Jobs in RPA Watch:
| UiPath Status | RPA Watch Status |
|---|---|
| Running | Running |
| Successful | Success |
| Faulted | Failed |
| Pending | Running |
| Stopping, Terminating | Cancelled |
Each synced job includes:
- Start and end timestamps with calculated duration
- Robot name and reference
- Release/process reference (linked to process)
- Job info field mapped to result summary
Schedules
- Schedule name, cron expression, and timezone
- Active/enabled status
- Linked release reference
Token Management
RPA Watch handles OAuth tokens automatically:
- Tokens are refreshed 5 minutes before expiry
- For External Apps: uses client_credentials grant
- For User Key: uses refresh_token grant
- No manual token management required
Running and Stopping Jobs
From the RPA Watch UI, you can:
- Start a job for a specific process/release
- Stop a running job to cancel execution
Troubleshooting
| Issue | Solution |
|---|---|
| Authentication fails | Double-check your org name, tenant name, and credentials. Ensure the External App has the correct scopes. |
| No processes appear | Verify the app has access to the folders containing your processes. Try removing folder ID filters. |
| Jobs not synced | Job sync fetches the last 24 hours by default. Older jobs won't appear on first sync. |
| Duplicate processes | If the same process exists in multiple folders, it appears once (deduplicated by process key). |