Databases
Query and write relational or document databases.
PostgreSQLMySQLMongoDB
Integrations
Connect the apps you already use
Plug in models, APIs, and SaaS tools without writing connector code.
One connection, three different uses
- 01
Add the connection on the organization. Authentication payloads for credentials are encrypted. Do not put a reusable secret in a named HTTP tool's static headers. That headersJson field is not encrypted.
- 02
On a flow, use a catalog node such as Slack with that connection. A named connection is the credential the node resolves on the server.
- 03
On an agent, select MCP tools or a named HTTP tool. A database grant is separate and covers one table, view, or collection.
Integration catalog
One catalog for every connection
One organization catalog holds connections. AI Vendors stores provider credentials. Models are what a node or agent runs. A connection is not the same action on every surface.
Integrations
SaaS apps and everyday tools your team already uses.
SlackNotionGitHub
AI Vendors
Provider credentials live under AI Vendors. You bring the key for that provider.
OpenAIAnthropicGemini
Models
Models are the models a flow node or an agent runs. They are not the same list as provider credentials.
ChatEmbeddingsImages
MCP Servers
Attach catalog servers or your own MCP endpoints as tools.
HostedCustom URLTool scopes
FTP
Move files to and from the servers your flows depend on.
HostPortCredentials
SMTP
Send transactional email from your own mail infrastructure.
HostPortTLS
S3
Read and write objects in your own storage buckets.
BucketRegionAccess key
Organization-scoped credentialsSame catalog for flows and agents
Catalog is not one action
A connection lives on the organization. What you can do with it depends on the surface.
| Surface | You can | Do not assume |
|---|---|---|
| Flow node | Place a catalog node that exists for that app and point it at an organization connection. | A catalog connection is not always a node. Figma can be connected while no Figma node is available on the graph. |
| Agent tool | Enable MCP tools, add a named HTTP tool, turn on httpRequest, attach Knowledge, or grant one database table, view, or collection. | Catalog app nodes are not automatically agent tools. There is no built-in web search. |
| Channel trigger | Slack, Discord, Microsoft Teams, email, and a schedule can start a new agent session when the agent is active. | Those bindings are not flow nodes, and a matching event does not continue the previous session. |
What each connection is for
Connect without writing code
Pick an integration from the catalog and add it to your organization. There is no connector code to write or maintain.
Apps as flow nodes
Apps that have a flow node appear on the graph. A catalog connection without a node, such as Figma today, cannot be placed on the graph.
Database grants, not every app
Grant create, read, update, or delete on one PostgreSQL or MySQL table or view, or one MongoDB collection. Other apps use MCP or a named HTTP tool.
Bring your own MCP servers
Attach MCP servers to your organization. Their tools show up for your agents, alongside the tools from catalog servers.
AI vendors and models
Store the provider key under AI Vendors. Pick the model under Models for a flow node or an agent.
Files, email, and storage
Use FTP, SMTP, and S3 connections from flows with credentials stored at the organization level.
Integrations questions, answered
API keys and OAuth are the two main options. Add the credential for your organization, and the platform stores it encrypted before any flow or agent uses it.
Credentials belong to the organization. Authentication payloads are encrypted and resolved on the server. Static headers on a named HTTP tool are stored in headersJson and are not encrypted. Do not put a reusable secret there.
Remove the integration or connection from your organization's integrations settings. Connected flows and agents stop using it once the credential is removed.
Integrations, Databases, AI Vendors, Models, MCP Servers, FTP, SMTP, and S3 are all managed from the same catalog. Each connection has its own page and organization-level credentials.
Provider credentials are under AI Vendors. The model you run is under Models. Connecting a provider does not make every catalog app an agent tool.
A run spends organization credits. Log storage and other limits follow your plan. See pricing
Connect it once on the organization
Connect a provider or an app once on the organization. Then choose a flow node, an agent tool, or a channel trigger. See the table above for which surface applies.