Integrations
Connect the services and data your AI can act on — Postgres, 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, calling an API, sending a message. Integrations show up in your work as Integration nodes and as tools you give an agent.
Built-in integrations
Postgres
Connect a PostgreSQL database to read and work with its data.
Bring your own with OpenAPI
Beyond the built-ins, you can connect any HTTP API by uploading its OpenAPI specification. Compass reads the spec and turns each operation into a typed action your agents and workflows can call — no custom code required.
Add a custom integration
Under Forge → Connections, click Custom Integration.
Upload the spec
Drop in or paste the API's OpenAPI document (JSON). Optionally set a base URL if it isn't in the spec.
Review
Compass fills in the name and description from the spec and lists the actions it found. This creates a new integration type in your project.
Add a connection
Create a connection for the new integration, supplying its authentication and any configuration — just like a built-in.
Actions
Each integration exposes a set of actions — the specific operations it can perform (for Postgres, querying tables; for an API, each of its endpoints). When you use the integration:
- In a workflow, an Integration node runs one action with inputs you wire in.
- As an agent tool, you choose which actions the agent is allowed to call, and it decides when to call them.
See Node types and Giving agents tools for how actions appear in each place.
Authentication
Integrations authenticate using whichever method the service requires — an API Key, Username & Password, HTTP Basic, or None. You choose this when creating the connection. Credentials are encrypted and never shown again; see Config and credentials.