UiPath AI Units usage

UiPath contributes Insights usage rows for AI Units consumed by tenant, folder, and project context.

Release state

This guide documents the read-only uipath connector implemented in the platform connector surface.

Required access

The names below are Venturi manifest capabilities, not UiPath OAuth scopes:

Venturi capability	Purpose
Insights.Read	Read AI Units and usage analytics.
Orchestrator.Tenant.Read	Read tenant context.
Orchestrator.Folder.Read	Read folder context.
Projects.Read	Read project context.

Do not grant robot, job, queue, or package mutation scopes.

Create a UiPath external application and select only the read resources needed for Insights and Orchestrator inventory under the target organization and tenant. UiPath owns the literal scope names shown in its external-application setup; Venturi capability names are not pasted into UiPath.

Setup

1. Create a dedicated UiPath integration identity.
2. Grant only the read-only scopes above.
3. Store the credential reference in Venturi.
4. Set VENTURI_UIPATH_LOOKBACK_DAYS if you need a poll window other than 30 days.
5. In Venturi, open Integrations and select UiPath and run Test connection.

Verification

• AI Units consumption rows appear for the expected tenants, folders, and projects.
• Usage rows keep their source as UiPath Insights.
• The connector inventory marks UiPath as read-only.

Rotation and offboarding

Rotate the integration credential through UiPath administration. Removing the connector stops new UiPath AI Units syncs.