UiPath

Set up the UiPath Orchestrator OAuth client and the Automation Hub Open API connection in ajan

Overview

ajan ships two separate UiPath integrations because they use different APIs and authentication:

A workspace admin configures an OAuth client for UiPath and an Open API token for Automation Hub. You then connect each integration independently.

Why ajan does not ship a shared UiPath OAuth client

UiPath registers external OAuth applications inside each organization (Admin → External applications → OAuth apps). A client created in one organization cannot serve every ajan customer's organization.

Because of that, ajan cannot provide a central UiPath client the way it does for Microsoft or Google. A UiPath admin in your organization must create the confidential application, then a ajan workspace admin pastes the Application ID and app secret into Bring Your Own OAuth Client.

UiPath (Orchestrator)

Connect Orchestrator so agents can run and monitor automations on behalf of each signed-in user.

Prerequisites

• A UiPath Automation Cloud organization with Orchestrator
• UiPath admin access to create an external OAuth application
• ajan workspace admin access to configure the OAuth client
• The Redirect URL and scope list from ajan's UiPath integration settings

Set up the OAuth client

Complete these steps once per ajan workspace (or once per group client if you use group-scoped clients).

Copy the Redirect URL and scopes from ajan

Go to Workspace settings → Integrations, select UiPath, then click Configure your OAuth client to use this integration.

Copy the Redirect URL. Leave Sync scopes with enabled actions on, then copy the Scopes list. Keep this dialog open or paste the values somewhere safe before you switch to UiPath.

Create a confidential OAuth app in UiPath

In UiPath Automation Cloud, open organization Admin → External applications → OAuth apps, then click Add application.

Configure the app as follows:

1. Enter an application name (for example, ajan).
2. Select Confidential application.
3. Click Add scopes, choose the Orchestrator resource, and grant the scopes from ajan under User Scope(s). Leave Application Scope(s) empty for this connection flow.
4. Paste the ajan Redirect URL into the redirect URL field.
5. Save the application.

Store the Application ID (Client ID) and the generated app secret (Client secret). UiPath shows the secret once.

For background on confidential apps and user scopes, see UiPath's OAuth apps overview.

Save the client in ajan

Back in the ajan OAuth client dialog:

1. Optionally set a Client name and choose Entire workspace or Groups.
2. Paste the UiPath Application ID into Client ID.
3. Paste the UiPath app secret into Client secret with no extra spaces or line breaks.
4. If the dialog shows OAuth connection details, you can save a UiPath Cloud URL as the default for that client, for example https://cloud.uipath.com/acme/DefaultTenant/orchestrator_/.
5. Click Save, confirm, then activate the client from the client list.

For group clients and scope sync behavior, see Bring Your Own OAuth Client and Manage Action-Level Scopes.

Connect a UiPath account

Open Integrations, select UiPath, and add a connection.

Members paste a UiPath Cloud URL that includes your organization and tenant, for example https://cloud.uipath.com/acme/DefaultTenant/orchestrator_/, unless you already set a default under OAuth connection details. You can also enter just the org name (tenant defaults to DefaultTenant) or org/tenant.

Complete the OAuth consent screen. ajan acts with that user's Orchestrator permissions.

Start using UiPath in ajan

Tag the integration with @ in any agent to list folders and processes, trigger jobs, queue work items, or inspect job history and audit logs.

Common use cases

• Run automations — Trigger Orchestrator jobs and add queue items from chat or workflows
• Discover processes — List folders and processes, including personal workspaces and Solution folders
• Troubleshoot runs — Check job status, pull job details and execution logs, and review faulted jobs
• Audit activity — Read Orchestrator audit logs for who changed jobs, queues, or other components

Troubleshooting

UiPath Automation Hub

Connect Automation Hub so agents can discover automation ideas and pipeline context. Visibility follows the Open API token user's Automation Hub roles and category access.

Prerequisites

• A UiPath Automation Cloud organization with Automation Hub enabled
• Access to Admin Console → Platform Setup → Open API to create or copy a token
• A personal or user-assigned Open API token (tenant-level tokens cannot search automations)

Setup

Copy your Automation Hub Cloud URL

Open Automation Hub in the browser and copy the URL. A typical shape is https://cloud.uipath.com/mycompany/DefaultTenant/automationhub_/.... ajan extracts the organization and tenant from this URL. You can also enter just the org name (tenant defaults to DefaultTenant) or org/tenant.

Generate a personal Open API token

In Automation Hub go to Admin Console → Platform Setup → Open API, then create or select a personal or user-assigned token. Use Copy to Clipboard next to the token so you get the combined Tenant ID/Token value.

Follow UiPath's token guide for the exact UI steps. If you set an App key when creating the token, copy that as well.

Navigate to Integrations in ajan

Go to Integrations and find UiPath Automation Hub.

Enter your credentials

Paste the UiPath Cloud URL, the Open API credential (Tenant ID/Token), and the App key if you created one. Leave App key empty otherwise.

Start using Automation Hub in ajan

Tag the integration with @ in any agent to search ideas, look up pipeline context, or browse categories and applications.

Permissions and token management

Unlike Microsoft or Google integrations, Automation Hub does not support delegated per-user OAuth. Use this section to understand what that means and how to manage tokens safely.

Understanding permission types

Automation Hub's Open API authenticates with a static token that an Automation Hub admin creates in Admin Console → Platform Setup → Open API. There is no per-user consent flow in ajan. Whoever uses the connected token sees what that Automation Hub user can already see in the UI.

Recommended setup

Create separate connections for regular catalog access and for privileged CoE work. Do not reuse a high-privilege CoE token as the default connection for everyone.

flowchart LR
  subgraph AH["Automation Hub"]
    RU["Dedicated regular user<br/>limited roles + categories"]
    COE["CoE / privileged user<br/>broader AH rights"]
  end
  subgraph LD["ajan"]
    C1["Catalog connection"]
    C2["CoE connection"]
    A1["Shared or agent-fixed<br/>for regular users"]
    A2["CoE-only agents<br/>or workflows"]
  end
  RU -->|personal / user-assigned token| C1 --> A1
  COE -->|separate token| C2 --> A2

Regular-user catalog connection

1. Create an Automation Hub user whose roles and category access match what regular ajan users should be allowed to see.
2. Grant only the permissions needed for search and basic idea detail. Skip CBA, collaborator, and detailed assessment permissions unless they are deliberately in scope.
3. Generate a personal or user-assigned Open API token for that user (not a tenant-level token).
4. Connect it in ajan, then either:
   • Share the connection with the people or groups who should use the catalog (Sharing Non-OAuth Connections Directly), or
   • Preselect it on an agent as a fixed connection (Using shared connections in agent actions).

Either option keeps visibility bounded to the dedicated user's Automation Hub rights. That is the strongest limited-view pattern the API allows.

CoE connection

Separately, the Center of Excellence (or another privileged team) can create their own Open API token for a user with broader Automation Hub permissions. Keep that connection on CoE-only agents or workflows.

What a limited token can see

What each action can return

Polling triggers (New automation idea, Updated automation idea) inherit the same visibility: they only see ideas the token user can already access.

For a regular-user catalog connection, enable the catalog actions you need and leave privileged options off unless required: Get cost-benefit analysis, Include collaborators, and Include advanced assessment.

Common use cases

• Idea discovery — Search automation ideas by text, phase, status, category, or application
• Pipeline context — Look up an idea's current phase and status, plus categories and apps it touches
• Taxonomy browsing — List categories and applications to understand how ideas are organized
• Change signals — Trigger workflows when ideas are created or updated within the token user's visibility

Troubleshooting