Integration disconnected
A connected app, channel, or MCP server stops working: messages do not arrive, a tool call returns an authentication error, or the connection shows as disconnected.
Likely causes
- The third-party authorization expired or was revoked (token timed out, password changed, app uninstalled on the provider side).
- The integration’s credentials or scopes changed and no longer cover what the agent needs.
- A channel (Slack, WhatsApp, Telegram, email) lost its link, so inbound messages never reach the agent.
- An MCP server is unreachable or its endpoint moved.
Step-by-step fix
- Find the affected connection
Open Settings → Connected apps and locate the integration. A disconnected or errored connection is flagged here.
- Reconnect or re-authorize
Reconnect the integration to refresh its authorization. Many providers expire tokens periodically, so a reconnect resolves most failures. Confirm the granted scopes still cover the tools your agent calls. See Managing connections.
- Check the channel link
If the problem is an inbound channel rather than a tool, verify the channel is still published and linked on the agent. Review the relevant channel setup and re-link if needed.
- Verify MCP servers
For an MCP server, confirm the server URL is reachable and any required key is still valid, then reconnect.
- Test end to end
Trigger one action that uses the integration (send a test message, run a tool) and confirm it now succeeds.
Where to look
- Connected apps — /settings/connected-apps for connection status.
- Manage connections — /integrations/manage-connections to reconnect or re-authorize.
- Task and workflow history — a disconnected integration usually appears as a failed tool call in the run record.