Skip to main content

​
Why connection management matters

Connections are not a one-time setup task. Over time, accounts change, permissions get updated, tokens expire, and workflows start depending on the same app access in multiple places. Good connection management helps you avoid unexpected workflow failures later.

​
Reuse before you duplicate

In most cases, you should reuse an existing connection instead of creating a new one. That makes it easier to:
  • keep app access consistent
  • reduce clutter in the Connections list
  • update fewer records when credentials change
Create a separate connection only when there is a clear reason, such as using a different account, a different environment, or a different ownership boundary.

​
Keep names clear

As your workspace grows, names matter more. Use connection names that make it obvious:
  • which app the connection belongs to
  • which account it uses
  • whether it is intended for production, testing, or a specific workflow group
Clear naming reduces mistakes when selecting connections inside workflow steps.

​
Understand default connections

Default connections can speed up setup, but they also affect how quickly someone can attach the wrong account to a workflow. Review default connections carefully when:
  • the same app is used by multiple teams
  • you have both personal and shared accounts
  • you maintain separate test and live environments
Defaults are convenient, but they work best when the ownership model is already clear.

​
When to update a connection

You may need to update or replace a connection when:
  • the connected account changes
  • permissions need to be expanded
  • access tokens become invalid
  • the workflow should now use a different app account
When this happens, avoid changing several workflows first. Update the connection situation first, then retest the affected workflows.

​
Rotation and replacement

Sometimes app credentials or tokens need to be refreshed or replaced. A safe pattern is:
  1. identify which workflows use the connection
  2. update or recreate the connection as needed
  3. run targeted tests on the affected workflows
  4. verify a real run after the change
This reduces the risk of silently breaking workflows that were previously stable.

​
Periodic cleanup

It helps to review connections from time to time and ask:
  • is this still in use
  • is this the right default
  • is this clearly named
  • is this account still the one we want workflows to use
Small cleanup habits keep the workspace manageable as automation usage grows.

​
What good connection management looks like

A healthy setup usually has:
  • a small number of well-named reusable connections
  • clear separation between test and production accounts when needed
  • deliberate use of defaults
  • regular retesting after credential changes
That kind of setup makes workflows easier to trust because the integration layer underneath them is more stable.