Integrations overview

Connect an agent to your external systems — the primary way to grant capabilities.

Integrations overview

An Integration connects an agent to an external system — your service desk, HRIS, identity provider, file store, or collaboration tool — and turns that system’s capabilities into tools the agent can use. Integrations are the primary way an agent gets the ability to find information and take action. Reach for one before authoring a Skillset.

Each integration is built and maintained by Cobalt, with guardrails and audit logging built in.

Two kinds of capability

Integrations provide two kinds of tools, and they’re authorized differently:

• Reads (on behalf of the user). Search and lookup tools that run as the asking user. Each end user authorizes once, and the agent only ever sees what that user can already see. No administrator credential is required beyond enabling the integration.

• Privileged actions (granted by an administrator). Tools that act for the organization — reset a password, add a user to a group, change a record. These require an administrator to grant access once, run under policy, and write an audit entry on every call. Until they’re authorized, these tools wait in an “awaiting authorization” state while the read tools work normally.

Adding an integration

1. Browse the catalog

   From an agent, open Integrations and choose a system from the catalog.

2. Select modules

   Pick which parts of the system to enable (for example, mail and calendar but not files). Each module maps to a set of tools.

3. Authorize

   Review the access requested and authorize. Reads use per-user authorization; privileged actions use one of the administrator methods below.

4. Index content (optional)

   For systems that hold documents — a knowledge base, a file store, a wiki — choose which spaces, sites, or folders to index so the agent can search and cite them.

5. Test

   Run the built-in connection test to confirm the integration is working before you rely on it.

Administrator authorization methods

Privileged actions use whichever method a given system supports. All credentials are encrypted at rest and never shown back in the console.

Method	How it works	Typical systems
Admin authorization	One-click grant — you’re sent to the vendor to approve, and Cobalt stores the resulting token.	Slack, Okta, Zendesk, ServiceNow, Atlassian
Service-account key	Upload a service-account key file and name the account to act as.	Google Workspace
Credential form	Enter the vendor’s connection fields (for example a directory ID, client ID, and secret).	Microsoft 365, Workday
Manager pool	No credentials — the action is allowed only when the asking user is the target’s manager.	Workforce-management and HR approvals

What’s available

Cobalt includes integrations across the systems an IT or HR agent typically needs, including:

• Productivity & collaboration — Google Workspace, Microsoft 365, Outlook, SharePoint / OneDrive, Slack, Microsoft Teams, Notion, Box, Dropbox.
• IT service management — ServiceNow, Zendesk, Freshservice, Atlassian (Jira, Confluence, Jira Service Management).
• Identity & security — Okta, Microsoft Entra, SailPoint.
• HR, HRIS & payroll — Workday, UKG, Gusto, Rippling, Freshservice.
• CRM — Salesforce, Freshworks.

The catalog in your console is the source of truth for what’s available and which capabilities each integration supports.

A flagship example

See Google Workspace for an end-to-end setup — read access in about a minute, plus the steps to enable privileged admin actions.