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

> Connect UiPath Automation Hub to Langdock, understand Open API permissions, and set up least-privilege catalog and CoE connections

## Overview

UiPath Automation Hub is where your organization collects and manages automation ideas through the pipeline. Once connected, you can use Langdock to search ideas, browse categories and applications, review pipeline phase and status, and retrieve cost-benefit or collaborator details when you need them, directly from your conversations.

<Info>
  **Authentication:** API Key (personal or user-assigned Open API token)<br />
  **Category:** Knowledge Base<br />
  **Availability:** All workspace plans<br />
  **Supported deployment:** UiPath Automation Cloud only
</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 your browser and copy the URL. A typical URL looks like `https://cloud.uipath.com/mycompany/DefaultTenant/automationhub_/...`. Langdock extracts the organization and tenant from this URL. You can also enter just the organization name (the tenant then 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** and 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 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 & Token Management

Unlike Microsoft or Google integrations, Automation Hub does not support delegated per-user OAuth. This section explains 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 permissions.** Every request runs as the user assigned to the Open API token, with that user's category access and role permissions. Langdock does not add its own privacy layer and does not filter out 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, the corresponding Langdock actions can return that data once they are enabled.
</Warning>

### Recommended setup

Create **separate connections** for regular catalog access and for privileged Center of Excellence (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 permissions"]
  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 details. Skip cost-benefit analysis, 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](/en/using-langdock/integrations/connections#sharing-non-oauth-connections-directly)), or
   * **Preselect it on an agent** as a fixed connection ([Sharing connections via agents](/en/using-langdock/integrations/connections#sharing-connections-via-agents)).

Both options limit visibility to what the dedicated user can see in Automation Hub. That is the strictest visibility control the API allows.

### CoE connection

The CoE 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 token without CoE permissions 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**              | Users without CoE permissions usually do not get the full All / Review / Decision / Implementation / Live views |
| **Privileged fields**            | Cost-benefit analysis, collaborators, and detailed assessment stay gated by Automation Hub permissions          |

### What each action can return

| Action                                      | Typical data                                                                                        | Permission note                                                                                                 |
| ------------------------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Search automations**                      | Name, description, phase/status, categories, apps, scores, estimated benefit hours, submitter/owner | Optional **Include advanced assessment** returns detailed assessment Q\&A when Automation Hub allows it         |
| **Get automation**                          | Same core fields for one idea                                                                       | Optional documents, components, and collaborators; collaborators need View Idea Collaborators in Automation Hub |
| **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**               | Cost-benefit summary for one idea                                                                   | Requires View Cost Benefit Analysis in Automation Hub                                                           |

Polling triggers (**New automation**, **Updated automation**) 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                                                          |