Use this page when a connection stops working — an OAuth grant was revoked, an API key leaked or expired — or when you want to stop a workflow using it. How integrations work explains connections and how steps choose one.
Note: Reconnecting or rotating an API key creates a connection with a new ID. Steps using System (shared connection) or Current User (first connection) pick up the new connection automatically. Steps using Specific Connection (by ID), and any connection IDs you've stored on records, need the new ID.
Reconnect deletes the current connection before the new authorisation starts. If you cancel at the provider, select Connect to finish.
anythink integrations connections list --provider slack
anythink integrations disconnect <connection-id> --yes
anythink integrations oauth connect slack --name "Team workspace"
Using the anythink CLI, disconnect Slack connection <connection-id> and connect Slack again.
The assistant calls the cli tool with integrations disconnect <connection-id> --yes, then integrations oauth connect slack, which opens your browser. This needs the MCP server running locally in stdio mode.
There's no in-place key update: disconnect the old connection and connect with the new key.
Use Disconnect rather than Reconnect for Claude AI, OpenAI and Grok — Reconnect starts an OAuth flow, which API-key providers don't have.
anythink integrations disconnect <connection-id> --yes
anythink integrations connect openai --name "OpenAI"
connect prompts for the new key without echoing it.
Note: Rotate API keys in your own terminal. Through an assistant, the new key would be passed in the command and end up in your conversation.
Once the new connection works, revoke the old key in the provider's own console.
When you rotate the client secret in the provider's console, save the new one in your project. Existing connections keep working; the new secret is used the next time a token is refreshed or a connection is made.
anythink integrations oauth configure slack --client-id <CLIENT_ID> --client-secret <NEW_SECRET>Disable a connection to stop workflows using it without deleting its stored credentials:
anythink integrations disable <connection-id>
anythink integrations enable <connection-id>
Using the anythink CLI, disable integration connection <connection-id>.
The assistant calls the cli tool with integrations disable <connection-id>.
Note: The dashboard has no enable or disable control for connections. A disabled connection's card shows as not connected; don't select Configure & Connect or Connect there unless you want a second connection.
While a connection is disabled, steps that would have used it fail with "No credentials found for
On the provider's card in Settings › Integrations, select Disconnect.
anythink integrations disconnect <connection-id>
The CLI shows the connection's provider, name and scope and asks you to confirm. Add --yes to skip the prompt in scripts.
Using the anythink CLI, disconnect integration connection <connection-id>.
The assistant calls the cli tool with integrations disconnect <connection-id> --yes.
Disconnecting deletes the credentials Anythink holds. It doesn't revoke the grant at the provider — remove the app in the provider's settings too, for example in your Google Account's third-party access page or your Slack workspace's app management.
Run anythink integrations connections list. A disconnected connection is gone; a disabled one shows no in the Enabled column. Trigger a workflow that used it and check View Job History: the step fails with "No credentials found", or succeeds against the new connection.