Skip to main content

​
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.
Authentication: API Key (personal or user-assigned Open API token)
Category: Knowledge Base
Availability: All workspace plans
Supported deployment: UiPath Automation Cloud only

​
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

1

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.
Only UiPath Automation Cloud URLs are accepted. Automation Suite and other self-hosted hosts are rejected.
2

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 for the exact UI steps. If you set an App Key when creating the token, copy that as well.
3

Navigate to Integrations in Langdock

Go to Integrations and find UiPath Automation Hub.
4

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

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.

​
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

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

​
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:
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

​
What each action can return

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

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