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

Who can connect integrations?

Manage integrations: Developer, Account Admin, and Organisation Admin. Every standard role has Use integrations. See Roles.

What do the card actions mean?

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.

Do I connect an integration separately for each agent or app?

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.

Can I connect more than one account for the same provider?

Yes. An integration's page lists All Connections, so you can keep several accounts for the same provider. See One connection, many uses.

How do I connect an API that isn't in the catalog?

Add an API Call 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.

Can core banking integrations reach production?

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.

Credentials

Which credential models are there?

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.

Can I switch from per-user credentials back to shared?

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.

Can I read back a saved credential?

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.

Where do I see which integrations agents may use across the account?

In Control Center › Govern › Connectors, on the Integrations tab. See Connectors.

Troubleshooting

Connecting

The Connect button is disabled

A card that reads Connect via UDG or Coming Soon can't be connected yet. See What the catalog shows.

I can't manage integration connections

Hovering shows You don't have access to manage integration connections. Managing connections needs Manage integrations: Developer, Account Admin, or Organisation Admin. See Roles.

OAuth won't complete

Run the connect step again and finish the provider's consent screen. Check that your browser isn't blocking pop-ups. See Connect BYOK.

A credential link shows Link Expired

Credential links expire. Ask for a new link. See One connection, many uses.

The service I need isn't in the catalog

For a REST API without a pre-built connector, add an API Call skill to the agent.

Using a connection

The Console Operator won't use a connection

Every connection starts off for the Operator. Turn it on under Connections in the Operator's side panel. See Agents & connections.

An agent or app stopped working after a disconnect

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.

An agent can't use a connected integration

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

Related

• Integrations Hub and Connect Methods
• Connect an integration: step by step
• Apps & Services: integrations inside an agent

---

Maintained by Abhishek Paul AI-assisted, human-approved