Managing connections

What the Connections page is for

A connection stores the credentials a workflow needs to talk to another service: an API key, OAuth tokens, AWS keys, a bearer token, a username and password, or a database address. You create it once, and every step that needs that service reuses it. See Connections for how steps refer to connections through variables.

Connections belong to the selected store. Choose a store in the header first.

The list

Connections lists your connections with a count.

• Search connections… filters by name, and the provider dropdown (All providers and then each provider) filters by type.
• Switch between list and grid. The list shows Name, Type, Status and Updated. The grid shows a card with a masked summary of the credentials (for example the start of a client ID), the last updated date and the connection's ID, which you can copy.
• Status is Active or Inactive. An inactive connection can be turned back on with Activate; for OAuth connections that opens the authorization window again.
• Select a row or Edit to change a connection. Delete removes it after you confirm.

Creating a connection

1. Select Create connection.
2. Choose the service or auth method. Use Search providers… or the category pills: Generic, Commerce, Payments & Tax, AI, Messaging, Marketing & CRM, Shipping, Data & Search, Identity & Cloud, Fraud, ERP & Finance and File Transfer.
3. Enter a Connection name. It starts as the provider's name, so change it to say which account it is, for example "Stripe production".
4. Fill in the fields for that provider.
5. Select Create connection.

If there is no provider for your service, the Generic ones cover most APIs:

Generic type	Use it for
API Key	A key sent in a header (choose the header name and format) or a query parameter
Bearer Token	A static token sent in a header, normally Authorization: Bearer …
Basic Auth	A username and password
OAuth Client Credentials	Server-to-server OAuth: client ID and secret, token URL and optional scopes
OAuth 2.0	Authorization-code OAuth with any provider: client ID and secret, and the provider's URLs. Copy the shown Callback URL into the provider's app settings as the redirect URI.

Provider-specific types ask only for what that service needs.

Secrets

Secret fields such as keys, tokens and passwords are encrypted when you save and can't be viewed again. When you edit a connection they appear locked. Select Override to type a new value, or Cancel and keep existing value to leave it. That is also how you rotate a key: edit the connection, override the secret and save. Anything you don't touch is kept.

OAuth connections

For OAuth-style connections (including OAuth, Slack, Google, Xero, Zoho CRM, QuickBooks Online, Sage Intacct, Royal Mail and FedEx) the button reads Save & connect. Saving opens a sign-in window with the provider. If you close it or authorization fails, the connection isn't created.

To re-authorize later, edit the connection and select Reconnect. If that fails, your existing connection is left unchanged and still active.

Using a connection in a workflow

Steps don't point at a connection directly. In the workflow, add a variable of type Connection and pick the connection as its default, choosing which connection types it allows. New connection in that form creates one without leaving the page. A step then picks that variable under Connection Variable. Choosing None means the step supplies its own authentication in its header fields.

Because steps use the variable, you can point it at a different connection, such as a staging account, without editing the steps. When you launch a workflow, you choose the connection for each environment.

Deleting a connection

Deleting is permanent. The dialog warns that workflow steps using the connection will fail until they are reconfigured. The page doesn't show which workflows use a connection, so check your connection variables first.