Skip to main content
Connections store Vault-backed credentials MCP tools use at runtime. Manage them from Connections (/connections) in the Console. Connections are separate from workflow graphs. You wire them to MCP instances through config profiles on each instance (/mcp/instances/{instance_id}), then reference the instance in workflow mcp_call steps (instance_id + server_url after publish, or server_url only in portable exports).
This page covers shared connection flows only. Per-adapter tools and config live on each connector page.

​
Console layout

The Connections page shows:
  • Google account card (when Google connect is enabled) — OAuth once, enable per-service (Gmail, Drive, Sheets, …)
  • Connect WhatsApp — opens the WhatsApp connection modal (when enabled)
  • New custom connection — API keys, tokens, DSNs, and template-based connectors
  • A searchable list of saved connections with usage hints
Page description in the Console: “Vault-backed credentials for your workspace. Attach them from each MCP connector’s config profile.”

​
Google Workspace

Google connections use OAuth 2.0. One Google account can authorize multiple Workspace services (Gmail, Drive, Sheets, Calendar, and more).
1

Connect Google account

On Connections, use the Google account card and complete OAuth.
2

Enable services

On the connected account card, enable the services you need (for example Gmail and Sheets).
3

Wire to MCP instances

Open MCP → your instance → Instance config (/mcp/instances/{id}). Pick or create a config profile and select the Google connection in the profile’s credential wiring.
See the full Google Workspace guide.

​
WhatsApp

WhatsApp connections support embedded signup (Meta business flow) or manual credential entry for existing business accounts. On Connections, click Connect WhatsApp (when the feature is enabled for your environment). See the WhatsApp connector guide for embedded signup, tools, and templates.

​
Custom connections (API keys and DSNs)

Many connectors authenticate with API keys, personal access tokens, or connection strings.
1

Create a connection

Click New custom connection and choose a template (when listed) or enter a display name and credential fields.
2

Save credentials

Paste the API key, token, or DSN. Secrets are stored in Vault — they are not echoed back in the UI after save.
3

Wire to an MCP instance

Go to MCP → open the instance → Instance config. Activate a profile wired to this connection (or use the quick-apply connection picker on the profile panel).
4

Validate (optional)

Run MCP validation for the server at /mcp/{server_id}/validate, or validate a specific server–connection binding via the API (POST /v1/mcp/servers/{id}/connections/{connection_id}/validate).
Examples: Resend, GitHub, Shopify, Postgres DSN, Notion integration token.

​
Managing connections

ActionHow
View usageClick a connection row to open the detail sheet — see which MCP instances reference it
Update credentialsEdit the connection and save a new key or re-authorize OAuth
Rotate keysAdd the new key, update instance profiles, then revoke the old key in the external service
DeleteRemove the connection only after unwiring it from all MCP config profiles
Deleting a connection breaks MCP instances whose active profile still references it. Rewire profiles first.

​
Per-workflow connection overrides

The API supports workflow-level connection overrides (GET/PUT /v1/workflows/{id}/connection-overrides) so one graph can target sandbox vs production credentials without duplicating the workflow. The Console does not expose a dedicated overrides panel today — use the API or Platform MCP if you need per-workflow credential routing.