Slack Error: 'messages_tab_disabled' — Cause, Fix, and Troubleshooting Guide
Fix the Slack messages_tab_disabled error: your bot can't DM a user because the app's Messages tab is turned off. Enable it in App Home settings.
- #slack
- #api
- #troubleshooting
- #errors
Stuck on this Slack error? Get the free incident triage checklist
A one-page PDF — the exact steps to isolate, fix, and verify a production error like this one. No spam, unsubscribe anytime.
Overview
messages_tab_disabled means you tried to send a direct message to a user, but your app’s Messages tab (under App Home) is turned off. With the Messages tab disabled, Slack does not allow the app to open or post to a DM with a human user.
{
"ok": false,
"error": "messages_tab_disabled"
}
It typically appears on chat.postMessage to a D… channel returned by conversations.open.
Symptoms
- Posting to public/private channels works; DMs to users fail.
conversations.openmay return a DM channel id, but the follow-upchat.postMessagefails.- The failure is per-app configuration, unaffected by scopes or the specific user.
Common Root Causes
1. The Messages tab is disabled in App Home
Under App Home → Show Tabs, the Messages Tab toggle is off. Slack blocks direct messaging entirely for the app.
2. “Allow users to send messages” unchecked
Even with the tab shown, the option to allow users/apps to message the bot may be off, which blocks the conversation.
3. App not reinstalled after enabling the tab
Toggling the setting without reinstalling can leave the running install without the capability.
How to diagnose
Open a DM and try to post:
curl -s -X POST https://slack.com/api/conversations.open \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{"users":"U0USER0001"}'
{"ok": true, "channel": {"id": "D0DM000001"}}
curl -s -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{"channel":"D0DM000001","text":"on-call ping"}'
{"ok": false, "error": "messages_tab_disabled"}
Fixes
- Enable the Messages tab: app config → App Home → turn on Messages Tab, and check Allow users to send Slash commands and messages from the messages tab.
- Reinstall the app to the workspace after changing App Home settings so the capability takes effect.
- If DMs aren’t required, post to a channel or an ephemeral message instead of a direct message.
What to watch out for
- This differs from
cannot_dm_bot(you tried to DM another bot, which is never allowed) —messages_tab_disabledis about your own app’s configuration when messaging a human. - Enabling the Messages tab also affects the App Home experience users see; coordinate with whoever owns the App Home UI.
- Some workspaces restrict App Home changes to admins; you may need an admin to flip the toggle and reinstall.
Related
- Slack Error: ‘cannot_dm_bot’
- Slack Error: ‘user_not_found’
- Slack App Home tab as an ops control panel
Fixed it? Get 500 Slack & DevOps AI prompts — free
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.
Did this fix your issue?
Get 500 Battle-Tested DevOps AI Prompts — Free
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.