Connections & credentials
A connection is a saved credential — an API key, an OAuth grant, or a username/password pair — that a workflow node uses to call a third-party app on your behalf. You create one from Credentials or inline while configuring a node.
Every app that supports at least one connection type publishes its own step-by-step guide, generated directly from that app's connection definition, on its public app page.
Auth types you'll see
Apps authenticate one of three ways:
- API key — paste a key or token generated from the app's own settings.
- OAuth — sign in and approve a scope grant through the app's consent screen.
- Basic — a username/password pair (less common; used by a handful of legacy APIs).
Find an app's connection guide
Open any app under Apps — once that app supports a connection type, its page includes a "How to connect" section with field-by-field instructions and any OAuth scopes it requests. A few examples are linked below; use Explore all apps for the full directory.
Connecting via the Platform API or MCP
When an external agent calls `create_credential` (or `POST /api/v1/credentials`) for OAuth or missing secrets, the response is `{status: "credential_required", appId, connectionId, connect_url}` instead of a chat card. Open the `connect_url` while logged into the same organization, complete the credential form, then have the agent poll `list_credentials` (or `GET /api/v1/credentials?appId=…`) until the new credential appears.