> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# UiPath

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

## Overview

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

| Integration               | Product surface | Authentication                                       | What you can do                                                                                 |
| ------------------------- | --------------- | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **UiPath**                | Orchestrator    | OAuth (confidential app in your UiPath organization) | Trigger jobs, queue work items, list folders and processes, inspect jobs and audit logs         |
| **UiPath Automation Hub** | Automation Hub  | API key (personal or user-assigned Open API token)   | Search ideas, browse categories and applications, review pipeline context and optional CBA data |

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

<Info>
  **Supported deployment:** UiPath Automation Cloud only. Automation Suite and other self-hosted hosts are not supported.
</Info>

### Why Langdock 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 Langdock customer's organization.

Because of that, Langdock 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 Langdock workspace admin pastes the Application ID and app secret into [Bring Your Own OAuth Client](/en/admin/manage-integrations/bring-your-own-oauth).

***

## UiPath (Orchestrator)

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

<Info>
  **Authentication:** OAuth (your organization's confidential application)<br />
  **Availability:** All workspace plans
</Info>

### Prerequisites

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

### Set up the OAuth client

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

<Steps>
  <Step title="Copy the Redirect URL and scopes from Langdock">
    Go to [**Workspace settings → Integrations**](https://app.langdock.com/settings/workspace/products/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.

    <Warning>
      Copy the Redirect URL from Langdock exactly. A trailing slash, wrong host, or typo causes `redirect_uri_mismatch` during connect.
    </Warning>
  </Step>

  <Step title="Create a confidential OAuth app in UiPath">
    In UiPath Automation Cloud, open organization **Admin → External applications → OAuth apps**, then click **Add application**.

    <Note>
      Open this from organization **Admin → External applications → OAuth apps**. Some UiPath pages also describe an Orchestrator **Manage Access** route, which may not appear in every tenant.
    </Note>

    Configure the app as follows:

    1. Enter an application name (for example, `Langdock`).
    2. Select **Confidential application**.
    3. Click **Add scopes**, choose the **Orchestrator** resource, and grant the scopes from Langdock under **User Scope(s)**. Leave **Application Scope(s)** empty for this connection flow.
    4. Paste the Langdock **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](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/authorizing-external-applications).

    <Warning>
      Put Orchestrator scopes under **User Scope(s)** only. Application scopes are for app-only access and do not match Langdock's user-delegated OAuth flow.
    </Warning>
  </Step>

  <Step title="Save the client in Langdock">
    Back in the Langdock 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. Click **Save**, confirm, then activate the client from the client list.

    For group clients and scope sync behavior, see [Bring Your Own OAuth Client](/en/admin/manage-integrations/bring-your-own-oauth) and [Manage Action-Level Scopes](/en/admin/manage-integrations/manage-action-level-scopes).
  </Step>

  <Step title="Connect a UiPath account">
    Open [Integrations](https://app.langdock.com/integrations), select **UiPath**, and add a connection.

    Paste a **UiPath Cloud URL** that includes your organization and tenant, for example `https://cloud.uipath.com/mycompany/DefaultTenant/orchestrator_/...`. You can also enter just the org name (tenant defaults to `DefaultTenant`) or `org/tenant`.

    Complete the OAuth consent screen. Langdock acts with that user's Orchestrator permissions.
  </Step>

  <Step title="Start using UiPath in Langdock">
    Tag the integration with `@` in any agent to list folders and processes, trigger jobs, queue work items, or inspect job history and audit logs.
  </Step>
</Steps>

### Common use cases

<CardGroup cols={2}>
  <Card title="Run automations" icon="play">
    Trigger Orchestrator jobs and add queue items from chat or workflows
  </Card>

  <Card title="Discover processes" icon="folder-tree">
    List folders and processes, including personal workspaces and Solution folders
  </Card>

  <Card title="Troubleshoot runs" icon="magnifying-glass">
    Check job status, pull job details and execution logs, and review faulted jobs
  </Card>

  <Card title="Audit activity" icon="clipboard-list">
    Read Orchestrator audit logs for who changed jobs, queues, or other components
  </Card>
</CardGroup>

### Troubleshooting

| Issue                                   | Solution                                                                                                                                             |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **`invalid_client` or secret errors**   | Re-copy the app secret from UiPath. If you regenerated the secret, update **Client secret** in Langdock. Avoid trailing spaces when pasting          |
| **`redirect_uri_mismatch`**             | Paste the Redirect URL from the Langdock dialog into the UiPath app with no changes                                                                  |
| **Authorization or scope errors**       | Confirm every scope shown in Langdock is granted under **User Scope(s)** for Orchestrator, not Application Scope(s). Reconnect after changing scopes |
| **Cloud URL / org tenant errors**       | Use a full Automation Cloud URL with organization and tenant, or `org/tenant`. Product path segments such as `orchestrator_` are not tenants         |
| **Folders or processes missing**        | The signed-in user needs Orchestrator access to those folders. Use **Get folders** to discover folder IDs, including personal workspaces             |
| **Audit or execution logs unavailable** | Enable the matching actions so Langdock requests `OR.Audit.Read` or `OR.Monitoring.Read`, then reconnect                                             |

***

## 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.

<Info>
  **Authentication:** API Key (personal or user-assigned Open API token)<br />
  **Category:** Knowledge Base<br />
  **Availability:** All workspace plans
</Info>

### 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

<Steps>
  <Step title="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_/...`. Langdock extracts the organization and tenant from this URL. You can also enter just the org name (tenant defaults to `DefaultTenant`) or `org/tenant`.

    <Note>
      Only UiPath Automation Cloud URLs are accepted. Automation Suite and other self-hosted hosts are rejected.
    </Note>
  </Step>

  <Step title="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](https://docs.uipath.com/automation-hub/automation-cloud/latest/api-guide/generate-your-token-from-automation-hub) for the exact UI steps. If you set an App key when creating the token, copy that as well.
  </Step>

  <Step title="Navigate to Integrations in Langdock">
    Go to [Integrations](https://app.langdock.com/integrations) and find **UiPath Automation Hub**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Start using Automation Hub in Langdock">
    Tag the integration with `@` in any agent to search ideas, look up pipeline context, or browse categories and applications.
  </Step>
</Steps>

### 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

| Model                 | Who acts                                   | Typical Langdock integrations  | Automation Hub |
| --------------------- | ------------------------------------------ | ------------------------------ | -------------- |
| **Delegated (OAuth)** | Signed-in end user                         | Microsoft, Google, and similar | Not available  |
| **Open API token**    | The Automation Hub user bound to the token | (this integration)             | Required       |

<Info>
  **Langdock uses the token user's Automation Hub rights.** Every request runs as the user assigned to the Open API token (category access plus role permissions). Langdock does not add its own privacy layer, and it does not strip privileged fields.
</Info>

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 Langdock. Whoever uses the connected token sees what that Automation Hub user can already see in the UI.

<Warning>
  If the token user can view cost-benefit analysis, collaborators, or detailed assessment data in Automation Hub, those Langdock actions can return it whenever they are enabled.
</Warning>

#### 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.

```mermaid theme={null}
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["Langdock"]
    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 Langdock 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 Langdock, then either:
   * **Share the connection** with the people or groups who should use the catalog ([Sharing Non-OAuth Connections Directly](/en/using-langdock/integrations/connections#sharing-non-oauth-connections-directly)), or
   * **Preselect it on an agent** as a fixed connection ([Using shared connections in agent actions](/en/using-langdock/integrations/connections#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

| Expectation                      | What happens                                                                                       |
| -------------------------------- | -------------------------------------------------------------------------------------------------- |
| **Category-scoped ideas**        | A typical Standard User (non-CoE) token only returns ideas in categories that user can view        |
| **Full Live / deployed catalog** | Usually incomplete unless Explore or category visibility already surfaces those ideas to that user |
| **Pipeline tables**              | Non-CoE users usually do not get the full All / Review / Decision / Implementation / Live views    |
| **Privileged fields**            | CBA, collaborators, and detailed assessment stay gated by Automation Hub permissions               |

#### What each action can return

| Action                                      | Typical data                                                                                        | Privilege note                                                                                      |
| ------------------------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Search automation ideas**                 | Name, description, phase/status, categories, apps, scores, estimated benefit hours, submitter/owner | Optional **Include advanced assessment** returns detailed assessment Q\&A when AH allows it         |
| **Get automation idea**                     | Same core fields for one idea                                                                       | Optional documents, components, and collaborators; collaborators need View Idea Collaborators in AH |
| **List categories** / **List applications** | Taxonomy for filters and discovery                                                                  | Follows what the token user can access                                                              |
| **List idea flows**                         | Tenant phases and statuses (names/keys)                                                             | Use with Search results for numeric phase/status IDs                                                |
| **Get cost-benefit analysis**               | CBA summary for an idea                                                                             | Requires View Cost Benefit Analysis in AH                                                           |

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

<CardGroup cols={2}>
  <Card title="Idea discovery" icon="magnifying-glass">
    Search automation ideas by text, phase, status, category, or application
  </Card>

  <Card title="Pipeline context" icon="diagram-project">
    Look up an idea's current phase and status, plus categories and apps it touches
  </Card>

  <Card title="Taxonomy browsing" icon="folder-tree">
    List categories and applications to understand how ideas are organized
  </Card>

  <Card title="Change signals" icon="bell">
    Trigger workflows when ideas are created or updated within the token user's visibility
  </Card>
</CardGroup>

### Troubleshooting

| Issue                                        | Solution                                                                                                                                       |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authentication failed**                    | Confirm the Open API credential is the full `Tenant ID/Token` value from Copy to Clipboard, and that the token is still active and not expired |
| **Search returns fewer ideas than expected** | The token user may lack category or Explore/pipeline visibility for those ideas. Check what that user sees in the Automation Hub UI            |
| **Tenant-level token errors on search**      | Use a personal or user-assigned token instead. Tenant-level tokens cannot search automations                                                   |
| **Cost-benefit or collaborators fail**       | Grant the matching Automation Hub permission to the token user, or leave those actions disabled for a least-privilege catalog                  |
| **Cloud URL rejected**                       | Use an Automation Cloud URL (`cloud.uipath.com/...`). Automation Suite and other hosts are not supported                                       |
| **App key required**                         | If the token was created with an App key, paste it into the **App key** field in Langdock                                                      |