Slack channel_not_found: 7 Causes We Reproduced, With Fixes

Slack returns channel_not_found when the channel you passed does not exist for the token you used. The usual causes are a mistyped or copied-wrong channel ID, a private channel the bot has not been invited to, a channel name that does not exist, and a channel ID from a different workspace. Private channels are the most common case: to a bot that is not a member, a private channel looks like it does not exist. We ran each cause on 29 September 2026 with a bot that had chat:write and chat:write.public, and recorded Slack's answer.

What each call returned

All calls were chat.postMessage with the same bot token. Every one returned HTTP 200 with "ok": false or "ok": true.

The body is the same for every channel_not_found:

{"ok": false, "error": "channel_not_found"}

Two rows are worth knowing before you debug. Every workspace has a default channel, but it is not always #general; in our test workspace it is #all-slack, so #general failed. And a DM ID only works for the people in that DM. A bot cannot post into a DM between people; pass the person's user ID instead and Slack delivers it to the app's own DM with them.

Fix: use the channel ID from channel details

Names change and can be ambiguous. IDs do not. Open the channel, click its name at the top, and the ID is at the bottom of the About tab, with a copy button:

Public channel IDs start with C. Private channels created today also start with C; the lock icon, not the ID, tells you it is private. Paste the ID into the channel field and keep the name out of your config.

Fix: invite the bot to the private channel

Type /invite @YourApp in the private channel. After we did, the same call that returned channel_not_found returned ok: true. When we removed the bot again, the error came back. Adding scopes does not help: our bot had chat:write.public and groups:history, and the private channel still did not exist for it until the invite. The invite step, with screenshots, is in Slack not_in_channel.

Fix: match the token to the workspace

A bot token belongs to one workspace install. The ID C0AQB3JTWMQ is a real channel in another workspace, and our token got channel_not_found. If your app is installed in several workspaces, store the token and the channel ID as a pair, and check auth.test: its team_id must be the workspace that owns the channel.

When the SDK says channel not found

The Python and Node SDKs raise the same error string. In Python, slack_sdk raises SlackApiError and the code is in e.response["error"]:

from slack_sdk.errors import SlackApiError
try:
    client.chat_postMessage(channel=channel_id, text="hi")
except SlackApiError as e:
    print(e.response["error"])

Run against our private channel with slack_sdk 3.44.1, it printed channel_not_found.

Other services that post to Slack, such as Zapier or CI plugins, pass the same response through. The fix is the same: use the ID, and invite their bot to private channels. For the error you get when the token lacks a permission instead, see missing_scope.

FAQ

Why does the channel exist in Slack but the API says channel_not_found? Because the token cannot see it. A private channel is invisible to a bot that is not a member, and a channel in another workspace is invisible to this workspace's token.

Does conversations.join fix channel_not_found? Not for private channels. Our bot called conversations.join on the private channel and got channel_not_found back. Only an invite from a member works.

Can I post to a channel by name? For public channels, yes: #w1-lab-public reached the channel and gave the same result as the ID. Store the ID anyway. We renamed the channel, and a post to the old name #w1-lab-public returned channel_not_found, while the ID kept working.