About this block

Connection Health Panel is the integration status surface for a workspace of automations. Each row names a connected app, Slack, Gmail, Postgres, Stripe, and Salesforce, with the account it authenticates as, a status badge, and a count of how many automations depend on it. Healthy rows offer a Manage button; broken ones swap it for a filled action.

Two rows are unhealthy, and each carries an inline explanation directly under it: an expired Gmail token that has paused seven automations, and a Salesforce connection that hit its daily API quota. A footer note states that connections use the narrowest OAuth scopes each automation needs, and that revoking access in the source app pauses the automations that depend on it.

When to use

Reach for this block on an integrations settings page or in an automation health dashboard, wired to your connection registry. It is where an admin looks when automations silently stop: the status badges and the dependent counts turn a vague outage into a specific connection to reconnect. Wire Reconnect to your OAuth flow and Manage to the connection detail.

A natural flow around it on an Application Pro page:

Before

• Integrations
• Settings pages

After

• Automation usage stats
• Status and health

What you can display

One strong use is the connected apps health list. Other connection panel shapes:

• All healthy. Every row connected, notes hidden, a compact read-only inventory of integrations.
• Grouped by scope. Rows clustered by the data each connection can read or write, for an audit view.
• Add connection empty state. The list replaced by a prompt to authorize the first app.

Tip: show the dependent automation count on every row; a broken connection means little until you can see that seven live automations are waiting on it.