Skip to content

Integrations

This page complements Integrations in XTM One.

That guide explains when integrations matter. This page gives you a quick tour of the integration screens.

The list page

In the left navigation, this area is Integrations. The list page answers one practical question fast: which external connections are usable right now.

Each card is status-heavy by design, so the list already works as a health dashboard. The status badge is the signal to read first — it distinguishes a connection that is ready, one that is configured but not yet authorized, and one that needs re-authorization because permissions changed. You can search by name or provider and filter by visibility, tags, or category to narrow a long list.

If you have permission, New Integration starts a new connection. Credentials are always encrypted in the database.

The detail page

Opening an integration shows a header with the connection status and the actions that make sense for it — a setup guide for provider prerequisites, Test Connection to validate the live connection, Authorize or Re-authorize to resolve OAuth state, and delete. The detail page itself is organized into Overview, Configuration, and Activity tabs.

Overview

Overview tells you not only whether the integration works, but why it does or does not. It combines usage figures, the connection state (authentication method, credential readiness, authorized and missing scopes), and cards showing which agents — and, for sync sources, which knowledge bases — depend on it.

Configuration

Configuration is a richer screen than most other resources because it mixes three concerns: the integration's identity, its authentication and provider setup, and its visibility and reuse in the workspace. The description field matters more than it looks — the UI passes it to agents as tool context.

This tab is also where you see what the integration actually does:

  • The available tools are split into read tools (retrieve or inspect information) and write tools (change something in the connected system). That split helps you judge risk. When the integration is connected, you can test a tool with real credentials before binding it to an agent.
  • If the provider supports events, an event triggers card explains, in business language, which external changes an agent can react to and how they are delivered (webhook, polling, or hybrid).
  • A webhooks card shows how external events enter XTM One. Depending on the provider it can display a URL to copy or, for GitHub, let you create and remove repository webhooks directly from the UI.

Activity

Activity is the change history — when the integration was edited, whether it was tested recently, and whether an issue started after a configuration change.

Read-only and managed nuances

Integrations can have more nuanced edit behavior than other resources. Company-managed integrations are read-only for non-admins, and some suite-level registrations behave like centrally managed records rather than personal connections. Status, tools, and related usage stay visible even when editing is restricted.

Good habits

  • Read the status badge before editing anything.
  • Use Test Connection before assuming the agent is broken.
  • Use the available tools card to understand what the integration really provides.
  • Check scopes and re-authorization warnings when OAuth behavior changes.
  • Look at Agents Using before editing a shared integration.