Every connection you set up powers other parts of your workspace — automations, apps, and ontology or catalog sources that read data through it. Before you change a connection's credentials or delete it, you need to know what's actually relying on it. The Dependencies and Activity tabs on a connection give you two complementary views: what depends on it today, and how it has changed over time.
Overview
Open any connection and switch between its Dependencies and Activity tabs. Dependencies shows the impact of a change before you make it — a map of every automation, app, or data source that would break if the connection stopped working. Activity shows the history behind the connection's current state — who created, edited, re-authenticated, shared, or disabled it, and when.
What the Dependencies tab shows
The Dependencies tab displays a visual graph with the connection in the middle and a Used by branch listing everything that relies on it to reach the underlying app — automations, apps, and other dependent assets. It's a map of impact: check it whenever you're about to make a disruptive change, so you don't unknowingly break something that depends on the connection. You can open any dependent asset directly from the graph to review or update it.
Deciding whether it's safe to delete a connection
Open the Dependencies tab before you delete a connection. If automations or apps still use it, deleting it will break them. The safe sequence is:
Open the connection's Dependencies tab and review what's listed under Used by.
Move those automations or apps to another connection, or retire them.
Only then delete the connection.
The delete confirmation also warns you how many assets will stop working, as a final check. If you're not ready to commit, disconnecting the connection instead of deleting it is a gentler option while you confirm nothing still relies on it.
Finding which automation uses a connection
Start from the connection rather than searching automations one by one. Its Dependencies tab lists every automation and other asset that references it, and you can click through to each one. This is the fastest way to answer "what will break if I touch this connection?" — and it's equally useful for tracing a failing automation back to a connection that recently changed.
What the Activity tab shows
The Activity tab is the connection's change history — who did what to it and when, including creation, edits, re-authentication, sharing, and disabling. It's the audit trail for the connection: useful for understanding how it got to its current state, who has been maintaining it, and whether a specific change — like a re-authentication or a settings update — lines up with when a problem started. Anyone with access to view the connection can read its activity.
Notes
Check the Dependencies tab before every disruptive change to a connection, not just before deleting it — re-authenticating or editing credentials can affect the same dependent assets.
The Used by graph reflects assets that reference the connection directly; always confirm nothing is missing before you proceed with a change.
The Activity tab is read-only history — it doesn't let you undo a change, only see what happened.