Managing Connections

Inspect saved app connections, reconnect expired accounts, and review dependent automations from the Connections page.

At a glanceVerified in app · Oct 30, 2026

Use it to: Inspect connection health, reconnect expired accounts, and manage external MCP agent tools
Find it: Left sidebar → Connections (Connections and Agent tools tabs)
Limits: Members can disconnect their own connections · Admins can disconnect any workspace connection

Viewing All Connections

Open Connections from the left sidebar (/app/[team]/workflows/connections). Below the Connect the apps your automations use hero and search bar, the page has two tabs:

Connections: Shows your workspace’s saved connections under Your connections (with a health summary such as 5 connected · all healthy or 1 needs attention), followed by Browse apps with category filters and the Connect an app button.
Agent tools: Register and review external Model Context Protocol (MCP) tool servers so builders can attach their tools to an AI Agent under Tools → MCP tools.

Use the top search bar to filter Your connections (by app, connection name, or account identity) and Browse apps at the same time. Scroll sideways through the tiles; hover over or focus a tile to check its account, owner, and status. When two workspace members share the same display name, Glow includes their email address (Name ([email protected])) to distinguish the owner. Click a tile to open the connection’s details.

To configure a workspace-owned OAuth registration, open Use your own app during the app’s sign-in setup. See Credentials & Authentication.

Connection Status

Status	Indicator	Meaning and next step
Connected	Standard tile	The connection is saved and not marked as expired. Verify actual resource access with a read-only automation run.
Needs reconnecting	Red indicator	Authorization needs attention. Click the tile to check Owner, then follow Reconnecting.
Disconnected	Hidden from normal list	Disconnected and unavailable for new Step selections.

Click a saved connection’s tile to check Connected as, Owner, Added, Last used, Scopes, and Automations using it (which lists shared workspace automations and excludes other members’ Private automations).

Connection Ownership & Lifecycle

Action	Connection Owner	Workspace Admin	Other Members (Admin, Manager, Member)
Select in a Step	Yes	Yes	Yes (Viewers cannot)
Rename or Reconnect	Yes	Own connections only (except OpenRouter)	No
Disconnect	Yes	Any workspace connection	No

If an owner leaves the workspace or loses content access, their connection cannot be used for new Step bindings, and reinviting them does not restore it. Workspace OpenRouter connections have separate Admin controls for reconnection, key rotation, and removal. Connection changes are blocked during MSP impersonation sessions.

Disconnecting a Connection

Check dependents before disconnecting. Removal can break Steps in every automation that uses the connection, including work already in progress. Another saved account for the same app does not automatically replace it.

Open the connection’s details

As the connection owner or a workspace Admin, open Connections and click the saved connection’s tile under Your connections. Check the intended account and coordinate any replacement with your team.

Choose what to disconnect

Click Disconnect in that connection’s details. This affects the selected connection, not every account saved for the app. The confirmation applies even when other connections remain.

Review and confirm

Review the dependent automations in the confirmation dialog. When it shows active automations, acknowledge the warning before clicking Disconnect.

The notification offers Undo while removal is pending. Use it immediately if you made a mistake. Closing or reloading the browser page ends that opportunity. Check the connection list after removal. If removal fails, the connection returns to the list and the error notification offers Retry. Address the error before trying again.

For a compromised credential, revoke or rotate it at the provider promptly. Disconnecting in Glow does not undo requests already sent or replace provider-side revocation.

Reconnecting

Use this sequence when an ordinary app connection shows Needs reconnecting, or after a password change, revoked provider grant, or API key rotation. You do not need to disconnect first: reconnecting updates the saved connection in place so dependent Steps keep their reference.

Open the affected Step

Check the account named in the App drawer’s warning. Ask the person who created that connection to complete reconnection. If that person is unavailable, coordinate a replacement account with your team and select it in the affected Steps instead.

Reconnect with the intended account

Click Reconnect {App} below the connection warning in the App drawer, or click the saved connection’s tile under Your connections and choose Reconnect. Complete the service’s sign-in or credential prompts using the same provider account as before. Glow rejects a mismatched account when it can detect one, but not every app supplies identity details. To switch identities deliberately, add another connection instead.

Verify the selected account and access

Confirm that Connection shows the intended account and the warning has cleared. Recheck the Step’s target resource and run a read-only access check before resuming normal runs.

Check other dependent Steps

Reconnecting keeps the saved connection reference, whereas choosing a replacement connection requires updating each affected Step. Verify dependent Steps and their destinations before returning them to service.

Before retrying an automation that writes data or sends messages, check what already happened in the connected service. Reconnecting does not undo earlier work, and repeating a run can repeat its effects. Real runs, including runs in Draft, use credits and may incur provider charges.

Multi-Account Support

Glow allows you to connect multiple accounts for the same app, such as separate Google Workspace accounts for operations and marketing or separate Slack workspaces. Keep different clients in separate Glow workspaces; see Client Onboarding.

Adding a Second Account

From a Step, open the Connection dropdown in the App drawer and choose Connect a new connection…. If a connection dialog offers saved workspace connections, choose Connect another, then Continue. Check the service’s sign-in screen carefully so you do not authorize the first account again.

Selecting Between Accounts in an Automation

Open the Connection dropdown to choose the account for each Step, then recheck the Step’s resource fields. For example, one Google Sheets Step can read from [email protected] while another writes to [email protected] in the same automation.

Where Connections Appear in the App drawer

In the App drawer, the Connection dropdown selects which saved workspace account the Step uses, or starts Connect a new connection…. The connection options menu (⋯) offers Select connection, Open Connections, and Remove from this step (which clears only that Step’s selection without disconnecting the workspace account). To rename a connection you own, click its tile on the Connections page and choose Rename.

Post-Reconnection Checks

These checks are for your review only. They are not saved, and Glow does not verify or change your automation.

0 of 4 checked

Review dependent Steps and accounts
Check Automations using it in the connection details and confirm with teammates whether any private automations also use the account.
Run a read-only access test first
Verify the account can read the target resource using Testing a Connection before testing any write against a safe destination.
Inspect downstream field mappings
Confirm the Step output and check the fields used downstream.
Verify trigger readiness before returning to Live
For automatic triggers, follow the activation checks and inspect the external service before repeating any uncertain write.

Verify it works

Run: Open Connections in the sidebar and check the summary bar
You should see: All active accounts show a healthy status, and clicking Reconnect refreshes credentials without breaking existing Steps.

What’s Next?

Connecting an App walks through account selection and a read-only access check.
Testing & Debugging helps you inspect results before retrying an automation.
Permissions and Access explains workspace roles and automation visibility.