How to disconnect and reconnect your chat platform
Disconnecting and reconnecting refreshes OAuth tokens, re-registers slash commands, and fixes many “bot stopped responding” issues. It is the right first step after workspace migrations, admin consent changes, or mystery auth errors. This article explains when to do it, what changes per platform, and what data typically survives the cycle.
Quick check
- You are an org admin — Only admins (or the person who installed the integration) can disconnect and reconnect.
- Announce a short window — Users may see brief duplicate welcome messages or need to re-authorize DMs.
- Use Dailybot’s official connect flow — Always start from Dailybot Integrations, not from unofficial OAuth links.
- Have platform admin access ready — Slack, Google Workspace, or Teams may prompt an approving admin.
- Note custom bot tokens — If you use advanced custom app setups, document current IDs before changing anything.
Common causes and fixes
When to use this
Reach for disconnect and reconnect when login loops appear, slash commands vanish, channel lists are stale, or Dailybot shows “disconnected” while the bot still looks online in chat. It also helps after renaming a Slack workspace, moving Discord servers, or switching which Teams tenant is canonical for your org. It is not a substitute for fixing channel permissions; invite the bot to private channels after reconnect as needed.
Steps for Slack
In Dailybot, open Integrations > Slack, choose Disconnect, confirm, then Connect Slack and approve the requested scopes in the OAuth screen. Return to Dailybot and verify the workspace name matches production. Re-invite @Dailybot to private channels and re-pin any workflow posts. Slack may take a few minutes to refresh slash commands across clients.
Steps for Discord
Disconnect from Dailybot’s Discord integration page, then reconnect using the install URL Dailybot provides so command registration stays in sync. Confirm you select the intended server. Restore channel mappings for check-ins and kudos. Review role hierarchy if interactions failed before the reconnect.
Steps for Google Chat
Disconnect and run the Chat install flow again. A Workspace admin may need to approve the Chat app if policies tightened. Re-add the bot to spaces that lost membership during the disconnect window.
Steps for Microsoft Teams
Disconnect in Dailybot, then reconnect with an account that can consent to the Teams app. IT may need to allow the app tenant-wide. Add Dailybot back to teams and channels where it was removed automatically.
What gets preserved vs what does not
Org membership, billing, and most web-app configuration usually remain. Platform-specific mappings (default channels, per-channel listeners) may reset or need validation. Historical messages in chat stay in Slack or Discord; Dailybot does not delete them. Active OAuth sessions for users might require signing in again if your IdP enforces re-auth on scope changes.
If none of this worked
Before contacting support, gather:
- Platform and workspace, server, or tenant identifier (non-secret)
- Approximate time of disconnect and reconnect
- Any OAuth error text shown during reconnect
- Whether the bot can post plain messages after reconnect
- Whether issues affect all users or only some
- Steps you already tried from this article
Then contact Dailybot support from the Help or Contact options in the product or on the website.