Documentation
Get Started

Connections & Credentials

Add, manage, and reuse app credentials from Settings → Connections.

Settings → Connections is where you manage every app connection for your organization — OAuth accounts and API key / token credentials.

Credentials are stored once per organization and reused across Action nodes, Start (app) triggers, and End nodes. You do not paste secrets into every node.

Open Connections

  1. Open Settings.
  2. Go to Credentials → Connections (or the Connections tab).
  3. Make sure the correct organization is selected — connections are scoped to the org.

Add an API credential

Use this for apps that authenticate with an API key, bearer token, basic auth, or custom fields (for example Finnhub, Telegram, Stripe, SendGrid).

  1. Click Add credential.
  2. Search for the app and select it.
  3. Enter the required fields (API key, token, etc.).
  4. Optionally set a display name for the connection.
  5. Save.

The connection appears in the list and is ready for any workflow in that organization.

Connect from a workflow

You can also add credentials while building a workflow:

  1. Add an Action, Start (App), or End node and select the app.
  2. Click Connect [App] in the configuration panel.
  3. Enter your key or token in the modal and save.

That connection is the same one shown under Settings → Connections. Later nodes for the same app reuse it automatically — no need to re-enter secrets.

OAuth apps (Google, Zoho, Lark, …)

OAuth apps appear in Connections after you authorize them:

  1. From a node, click Connect, or manage them from Settings → Connections.
  2. Complete the provider login / consent flow.
  3. Tokens are stored securely and refresh automatically when supported.

See OAuth Authentication and Connecting Apps.

Manage existing connections

On each connection you can typically:

ActionWhat it does
VerifyCheck that the credential still works
Update / ReconnectReplace an API key or re-run OAuth
DisconnectRemove the credential from the organization

After disconnecting, workflows that use that app will prompt you to connect again before they can run successfully.

Organization scope

  • Credentials belong to the selected organization, not a single workflow.
  • Switching organizations shows that org’s connections only.
  • Workflow exports never include secrets.

Tips

  • Prefer Add credential or node Connect over putting keys in workflow variables when a dedicated integration exists.
  • Use workflow variables or the HTTP Request node for one-off APIs that are not in the app catalog.
  • Organization API keys under Settings → API Keys (wk_...) are for calling into TogoFlow (webhooks, MCP) — not for third-party app auth. See API Keys.

Next steps