Integrations Overview
Integrations are the connections that let CatalEx work with the services your team already uses — GitHub, Gmail, Jira, Salesforce, Notion, and many more. Once an integration is connected, your Studio agents can read from and act on it.
All integrations are connected and managed on the Tools page.
The building blocks
- An integration is a connection to an external service. It exposes a set of actions — for example, the Gmail integration includes Send Email, Create Draft, and List Labels.
- A few built-in tools are always available with no setup: Web Search and Brain (search your company and personal knowledge).
- An agent (built in Studio) decides how and when to use the tools it's been given.
An agent can use multiple tools, and a single connected integration can be used by many agents — you don't duplicate a connection per agent.
How they fit together
You
|
v
Studio agent (instructions + goals)
|
v
Tools (connected integration)
|
v
External service (e.g., Jira, GitHub, Gmail)
- You give an agent a task — in chat or on a schedule.
- The agent uses its instructions to decide what to do.
- It calls the actions of its connected tools to fetch data or take action.
- Sensitive actions pause for your approval, governed by guardrails.
Integrations vs. knowledge sources
CatalEx connects external services in two distinct ways:
- Tools (this section) let agents act — send an email, create an issue, post a message.
- Brain sources let CatalEx search your knowledge — Google Docs, Slack, and Confluence indexed for question-answering.
The same app can appear in both. See Connecting Your Data for the distinction.
Connecting integrations
See the Tools page for the full walkthrough: browsing the catalog, one-click OAuth, hosted or custom credentials, managing multiple accounts, and setting per-action guardrails. Beyond the official catalog, admins can also add custom MCP servers.
For the full list of supported services, see Official Integrations.
Who can manage integrations?
Connecting and configuring integrations requires the Admin or Owner role. Any team member can build and run agents in Studio using the tools that have been connected.