Slack error restricted_action_read_only_channel: Cannot post into a read-only channel
Last verified against Slack API reference - chat.postMessage errors
Cannot post any message into a read-only channel.What error restricted_action_read_only_channel means
The channel you targeted is read-only for your app, and Slack will not accept any message there. The documented text is "Cannot post any message into a read-only channel." It sits in a family of channel-posture errors on chat.postMessage, alongside restricted_action_thread_only_channel ("Cannot post top-level messages into a thread-only channel"), restricted_action_non_threadable_channel and restricted_action_thread_locked.
The channel exists and your app may be a member, so channel_not_found and not_in_channel do not apply. The restriction is a property of the channel, usually set by workspace admins for announcement-style channels where only certain people may post. The more general restricted_action covers workspace-wide posting preferences.
The response will not change on retry. Either the channel's posting permissions change, or your app posts somewhere else. Check whether the destination was picked by a user during setup, since that is where the fix belongs.
What it looks like
POST /api/chat.postMessage
{"channel": "C0ANNOUNCE1", "text": "Deploy finished"}
{"ok": false, "error": "restricted_action_read_only_channel"}Why it happens
- The target is an announcement or read-only channel where only selected members may post.
- An admin changed the channel's posting permissions after the app was configured.
- A notification destination was set to a company-wide announcements channel by mistake.
How to fix Slack error restricted_action_read_only_channel
- 1Check with a workspace admin how the channel's posting permissions are set.
- 2Ask an admin to allow the app to post there, if that fits the channel's purpose.
- 3Otherwise, point the integration at a channel where apps may post.
- 4Surface this error to whoever configured the destination instead of retrying.
How to stop it recurring
When users pick a destination channel, send a test message right away and show any restricted_action_* error in the setup UI. Recheck destinations when posting starts to fail, because admins can change channel posting rules at any time. Store the last error per destination so the setup screen can explain why a channel stopped working.
Official reference: Slack API reference - chat.postMessage errors. See all Slack error codes or the Slack limits and quotas.
Related codes
- restricted_action: A workspace preference blocks this postingA workspace preference prevents the authenticated user from posting.
- not_in_channel: Bot is not a member of the channelCannot post user messages to a channel they are not in.
- is_archived: Channel has been archivedChannel has been archived.
- channel_not_found: Value passed for channel was invalidValue passed for channel was invalid.
Error restricted_action_read_only_channel - quick answers
What does Slack error restricted_action_read_only_channel mean?
The channel you targeted is read-only for your app, and Slack will not accept any message there.
How do I fix Slack error restricted_action_read_only_channel?
1. Check with a workspace admin how the channel's posting permissions are set. 2. Ask an admin to allow the app to post there, if that fits the channel's purpose. 3. Otherwise, point the integration at a channel where apps may post. 4. Surface this error to whoever configured the destination instead of retrying.
Stop debugging Slack by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.