Integrations
Connect the services and data your AI can act on — built-in integrations, or any API via an OpenAPI spec.
An integration connection links Compass to an external service or data source. Where a provider is what your AI thinks with, an integration is what it acts on — querying a database, reading files from a bucket, calling your own API. Integrations show up in your work as Integration nodes and as tools you give an agent.
Available integrations
Each integration has its own page covering what it does, how to connect it, and the actions it offers.
Postgres
Query and modify a PostgreSQL database.
S3
Read and write files in AWS S3 or any S3-compatible store — and sync them into datasets.
Qdrant
Your own Qdrant vector store, for vector pipelines you build on the canvas.
Custom (OpenAPI)
Any HTTP API, described by an OpenAPI spec — each operation becomes an action.
Connecting an integration
Start a new connection
Under Studio → Connections, click the integration's card, then New connection, and give it a Connection name.
(Optional) Route through a gateway
Choose a gateway under Gateway if this service's traffic should pass through one. Gateways apply to HTTP APIs — custom OpenAPI integrations.
Authenticate
Pick the Auth type if the integration offers more than one, and enter the credentials. Credentials are encrypted and never shown again; see Config and credentials.
Configure
Fill in the integration's settings — a host and database, a bucket, a URL.
Create
Click Create connection.
Actions
Each integration offers a set of actions — the specific operations it can perform, each with a typed input and output. Open an integration's card and choose the Tools tab to see them all. When you use an integration:
- In a workflow, an Integration node runs one action with inputs you bind.
- As an agent tool, you choose which actions the agent may call, and it decides when to call them. The same goes for Compass Chat's Tools menu.
Read and write actions
Every action is marked as either a read or a write. When you attach an
integration as a tool — to an agent, on the canvas, or in chat — only its read
actions start switched on. Write actions (inserting rows, uploading files,
calling a POST endpoint) are one tick away, so giving an agent the power to
change things is always a deliberate choice. You can also require
human approval for any action.