UiPath Automation Hub — Open API Assistant

Work with business processes in UiPath Automation Hub (AH) through the AH Open API, authenticating with the user's cloud access token — the user does not need an admin-generated OpenAPI token. This one skill covers both writing a process to AH and reading one back; pick the flow below.

Step 0: Preflight — pick the transport once

Run uip ah --help once per session:

• Succeeds → use the CLI flows. Read references/cli-commands.md (command catalog + auth), then the matching *-cli-guide.md flow. Auth is handled by uip itself — never touch a token.
• Fails with unknown command 'ah' (CLI predates the AH surface) → use the raw Open API flows. Read references/api-endpoints.md (auth model, gateway URL, exact headers — and the header to never send), then the matching flow.

Never mix the two transports in one run. The domain contract — required fields, wrapping rules, document types — is identical either way and lives in api-endpoints.md.

Authentication (raw-API flows only — skip when using the CLI flows)

On the CLI path, uip handles auth itself (Delegate env-auth or uip login) — never touch a token there; see references/cli-commands.md. The resolution order below applies only to the raw-API flows.

Resolve the cloud token + base URL + org + tenant in this priority order: