Integrations Hub
Connect third-party services once, and use them from agents, apps, and the Console Operator.
The Integrations Hub is where you connect third-party services — banking, CRM, productivity, compliance, analytics, and more. It is one catalog to discover integrations, configure their credentials, and manage their connections.
Open Integrations in the Console sidebar.
How the Integrations Hub works
Discover — Browse a catalog of 228 integrations, organized by category. Each card shows what the integration does and whether you can connect it.
Configure — Connect an integration and choose how its credentials are held: shared, per user, or managed by the platform. Credentials are encrypted at rest and masked on read.
Use — Once connected, an integration is available to agents and apps, in the builders it supports. Agents call its methods as tools during conversations, and the Console Operator can use connections you turn on for it.
What the catalog shows
Each card shows the integration's logo, name, and description, and one action:
Connect
Available to connect. Opens the connect form.
Connected
Already connected.
Connect via UDG
A UDG integration. The button is disabled; it can't be connected yet. See Connect Methods.
Coming Soon
Listed, but not yet available for any builder.
Filter the catalog by status: All, Available, Connected, or Coming Soon. UDG integrations are counted under Available.
Can be connected
126
Listed through UDG, not yet connectable
82
Coming Soon
20
Total in the catalog
228
How integrations connect
Each integration uses one of three connect methods. See Connect Methods for the details.
Connect BYOK
106
You supply credentials for your own account with the provider, or use Platform Managed Keys where offered.
Sandbox account (through Kinective)
20
Core banking systems. Agent Builder only, sandbox only, Platform Managed Keys.
Connect via UDG
82
Brokered through the UDG partner network. Not yet available to connect.
Choose how credentials are held
The connect form can offer up to three credential models:
Shared credentials — the default. One set of credentials, used for every run.
Use per-user credentials (ONE-WAY) — each user provides their own credentials at runtime, in their own vault. Once saved, the integration can't go back to shared credentials.
Use Platform Managed Keys (RECOMMENDED) — the platform handles credentials and security, so you connect without any setup.
Of the integrations you can connect, 76 offer per-user credentials and 36 offer Platform Managed Keys. See Choose a credential model.
Some integrations connect to a sandbox for testing, with production access on request. See Sandbox and production.
One connection, many uses
Connect once. Agents and apps that use an integration reuse its connection, without connecting again.
Agents and apps share it. There is no separate agent-side setup. An agent calls a connected integration's methods the same way it calls any other tool.
More than one connection. An integration's page lists All Connections, so you can keep several accounts for the same provider.
The Operator needs it turned on. The Console Operator can use a connection only after you turn it on for the Operator; every connection starts off. See Agents & connections.
Credentials by link. A credential link opens an Enter Credentials form for the integration. Links expire; an expired one shows Link Expired.
Disconnect a connection
Disconnecting a connection permanently revokes its stored credentials and cannot be undone. Before you confirm, the dialog checks where the connection is used and lists any Connected apps and Connected agents, so you can see what will stop working. To use the integration again, connect it again.
Using integrations with agents, skills, and apps
Agents can call integration methods during conversations. For example, an agent can look up a contact in Salesforce, create a Jira ticket, or send a Slack message, all as part of a conversation.
Flows can include integration calls as steps.
Apps built in App Builder can use integrations for authentication (Google OAuth, Microsoft OAuth), payments (Stripe), messaging (Twilio), and data access.
Each category page lists, for every integration, the builders it's available in and how it connects, and the use cases documented for it.
Security and credentials
Encryption at rest — credential fields are encrypted before storage and never stored in plaintext.
Masked display — when credentials are read back through the UI or API, sensitive values show as
******. They are decrypted only when the integration runs.Per-user isolation — with per-user credentials, no user's session can read or use another user's credential.
OAuth lifecycle — for OAuth integrations, the platform manages the authorization flow, token refresh, and state validation.
Browse integrations by category
Core banking, digital banking and lending, financial data, payments, credit bureaus, accountancy
45
29
13
CRM, marketing and outreach, advertising and social media, commerce, customer support
36
24
5
Workplace tools, storage, email, messaging, meetings, project management, source control
30
8
2
An integration can appear on more than one page.
To see which integrations the account has made available to agents, use Connectors in Control Center.
Connecting to APIs not in the catalog
To connect to a REST API that isn't in the catalog — an internal service, a proprietary endpoint, or a third-party API without a pre-built connector — add an API Call skill to the agent. It defines a custom API request the agent can call, without a catalog entry.
For common questions and fixes, see Integrations Hub: FAQs & Troubleshooting.
Maintained by Abhishek Paul
AI-assisted, human-approved
Last updated
Was this helpful?