> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/integrations-hub/integrations-hub-faqs-and-troubleshooting.md).

# Integrations Hub: FAQs & Troubleshooting

Answers to common Integrations Hub questions, and fixes for disabled Connect buttons, credentials, and connections agents can't use.

This page answers common questions about connecting integrations, credential models, and connections. Use the troubleshooting entries when you can't connect an integration, or an agent, app, or the Console Operator can't use one.

## FAQs

### Connecting

<details>

<summary>Who can connect integrations?</summary>

**Manage integrations**: Developer, Account Admin, and Organisation Admin. Every standard role has **Use integrations**. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>What do the card actions mean?</summary>

**Connect** opens the connect form. **Connected** means it's already connected. **Connect via UDG** is disabled: UDG integrations can't be connected yet. **Coming Soon** means the integration is listed but not yet available for any builder. See [What the catalog shows](/ai-workbench-qore/console/integrations-hub.md#what-the-catalog-shows).

</details>

<details>

<summary>Do I connect an integration separately for each agent or app?</summary>

No. Connect it once, and agents and apps that use it reuse the connection, in the builders the integration supports. There's no separate agent-side setup. See [One connection, many uses](/ai-workbench-qore/console/integrations-hub.md#one-connection-many-uses).

</details>

<details>

<summary>Can I connect more than one account for the same provider?</summary>

Yes. An integration's page lists **All Connections**, so you can keep several accounts for the same provider. See [One connection, many uses](/ai-workbench-qore/console/integrations-hub.md#one-connection-many-uses).

</details>

<details>

<summary>How do I connect an API that isn't in the catalog?</summary>

Add an [API Call](/ai-workbench-qore/platform-resources/skill-library/api-call.md) skill to the agent. It defines a custom API request the agent can call, without a catalog entry. See [Connecting to APIs not in the catalog](/ai-workbench-qore/console/integrations-hub.md#connecting-to-apis-not-in-the-catalog).

</details>

<details>

<summary>Can core banking integrations reach production?</summary>

The 20 core banking integrations reached through Kinective connect with a sandbox account only, use Platform Managed Keys, and are available in Agent Builder only. Some other integrations offer **Production access**, marked **Contact sales**. See [Sandbox and production](/ai-workbench-qore/console/integrations-hub/connect-methods.md#sandbox-and-production).

</details>

### Credentials

<details>

<summary>Which credential models are there?</summary>

**Shared credentials**, the default, use one set for every run. **Use per-user credentials** has each user provide their own at runtime, in their own vault. **Use Platform Managed Keys** lets the platform handle credentials, so there's no setup. Each integration offers only the models it supports. See [Choose a credential model](/ai-workbench-qore/console/integrations-hub/connect-methods.md#choose-a-credential-model).

</details>

<details>

<summary>Can I switch from per-user credentials back to shared?</summary>

No. **Use per-user credentials** is one-way: once saved, the connection can't go back to shared credentials. The form asks you to confirm before saving. See [Per-user credentials can't be undone](/ai-workbench-qore/console/integrations-hub/connect-methods.md#per-user-credentials-cant-be-undone).

</details>

<details>

<summary>Can I read back a saved credential?</summary>

No. Credential fields are encrypted at rest and show as `******` when read through the UI or API. They're decrypted only when the integration runs. See [Security and credentials](/ai-workbench-qore/console/integrations-hub.md#security-and-credentials).

</details>

<details>

<summary>Where do I see which integrations agents may use across the account?</summary>

In **Control Center** › **Govern** › **Connectors**, on the **Integrations** tab. See [Connectors](/ai-workbench-qore/control-center/govern/connectors.md).

</details>

## Troubleshooting

### Connecting

<details>

<summary>The Connect button is disabled</summary>

A card that reads **Connect via UDG** or **Coming Soon** can't be connected yet. See [What the catalog shows](/ai-workbench-qore/console/integrations-hub.md#what-the-catalog-shows).

</details>

<details>

<summary>I can't manage integration connections</summary>

Hovering shows *You don't have access to manage integration connections*. Managing connections needs **Manage integrations**: Developer, Account Admin, or Organisation Admin. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>OAuth won't complete</summary>

Run the connect step again and finish the provider's consent screen. Check that your browser isn't blocking pop-ups. See [Connect BYOK](/ai-workbench-qore/console/integrations-hub/connect-methods.md#connect-byok-bring-your-own-key).

</details>

<details>

<summary>A credential link shows Link Expired</summary>

Credential links expire. Ask for a new link. See [One connection, many uses](/ai-workbench-qore/console/integrations-hub.md#one-connection-many-uses).

</details>

<details>

<summary>The service I need isn't in the catalog</summary>

For a REST API without a pre-built connector, add an [API Call](/ai-workbench-qore/platform-resources/skill-library/api-call.md) skill to the agent.

</details>

### Using a connection

<details>

<summary>The Console Operator won't use a connection</summary>

Every connection starts off for the Operator. Turn it on under **Connections** in the Operator's side panel. See [Agents & connections](/ai-workbench-qore/console/console-operator/agents-and-connections.md#connections).

</details>

<details>

<summary>An agent or app stopped working after a disconnect</summary>

Disconnecting permanently revokes the connection's stored credentials and can't be undone. Connect the integration again. Before you disconnect, the dialog lists the **Connected apps** and **Connected agents** that use it. See [Disconnect a connection](/ai-workbench-qore/console/integrations-hub.md#disconnect-a-connection).

</details>

<details>

<summary>An agent can't use a connected integration</summary>

An integration is available only in the builders it supports, and the account's Connectors set the outer limit for every agent. Check the integration's builders on its category page, and its **Standing** in Connectors. See [Browse integrations by category](/ai-workbench-qore/console/integrations-hub.md#browse-integrations-by-category) and [Connectors](/ai-workbench-qore/control-center/govern/connectors.md).

</details>

### Related

* [Integrations Hub](/ai-workbench-qore/console/integrations-hub.md) and [Connect Methods](/ai-workbench-qore/console/integrations-hub/connect-methods.md)
* [Connect an integration](/ai-workbench-qore/task-guides/how-to-connect-an-integration.md): step by step
* [Apps & Services](/ai-workbench-qore/console/agent-builder/build/apps-and-services.md): integrations inside an agent

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/console/integrations-hub/integrations-hub-faqs-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.