Agent Workflows
Check connection health

Check connection health

Verify that a connected channel still has a valid token before publishing, and re-authorize it if it has expired.

User intents

"Is my YouTube channel still connected?" "Why are my posts failing — check my connection."

Required information

  • The connectionId (or none — list all connections first).

Preconditions

  • At least one connection exists for the workspace.

Tool sequence

List the channels

list_connections — review each connection's status and token validity.

Inspect a specific channel

get_connection with connectionId — confirm the token is present and not expired.

Re-authorize if needed

If the token is expired or missing, get_oauth_connect_url with the existing connectionId, hand the URL to the user, then poll check_oauth_status.

A healthy connection has a valid, non-expired token and a live platform (YouTube or Facebook). Connections for not-yet-supported platforms may list but cannot publish.

REST alternative

GET /api/v1/connections and GET /api/v1/connections/{id} — see the Connections reference.

Recovery paths

  • Token expired — re-authorize via get_oauth_connect_url with the existing connectionId, then poll check_oauth_status.
  • 404 not found — the connection was removed; re-create it via Connect a channel.
  • check_oauth_status returns expired — the re-auth ticket lapsed; request a fresh one.

Example prompt → result

"Check whether my 'Tech Reviews' channel is still connected and fix it if not."

Result: the agent reports the channel's token status and, if expired, returns a re-authorization link.

Common mistakes

  • Assuming a listed channel is publishable without checking token validity.
  • Creating a brand-new connection when the existing one just needs re-authorization.

Related docs

Connecting Channels guide · Tool reference · Connect a channel