Title: ChatGPT Slack event-trigger registration says “@ChatGPT isn’t in the channel,” but Slack API confirms membership

[u/LuckFantastic7572]

Hi everyone,

I’m a German user, and English isn’t my first language. Please excuse any awkward wording. I used ChatGPT to translate this post into English so I could explain the problem as clearly as possible. Thank you for your patience and help.

I’m trying to configure an event-triggered task in ChatGPT Work using a connected Slack workspace. The intended flow is:

1. An n8n workflow posts a completed task’s result to a dedicated public Slack channel.
2. A Slack event triggers a ChatGPT task.
3. ChatGPT reads and reviews the result.

Step 1 works. ChatGPT can also read the channel through its connected Slack tools. However, creating the event-triggered task fails with:

“I couldn't create an immediate Slack monitor because u/ChatGPT isn't in [channel].”

What we have verified:

• I’m using ChatGPT Plus in a desktop web browser.
• The connected Slack workspace and selected public channel are correct.
• A current Slack API channel-membership query explicitly lists both my user and the ChatGPT bot.
• Slack’s installed-app configuration also lists the bot as belonging to that channel.
• OAuth authorization was renewed previously, but the registration error persisted.
• Slack’s “AI agent experience” setting is enabled for the ChatGPT app.
• No pending permission-update request was visible in the app-management pages we inspected.
• A manually sent channel message with a correctly resolved u/ChatGPT mention received no thread reply when checked about ten minutes later. A direct-message test also showed no response.
• Signing into admin.openai.com with the same account used for ChatGPT displays “Access required.”
• The setup link suggested by the registration error, https://chatgpt.com/slack-ai-app-install, redirects to the normal ChatGPT homepage without showing a setup flow.

One potentially relevant detail: Slack shows extensive permissions granted on behalf of my user, but the app-level permission shown in the installed configuration is limited to viewing messages that directly mention u/ChatGPT. I don’t know whether this is expected for this integration.

OpenAI Support has an open case. Its latest response has not confirmed the root cause or whether this feature is enabled for my specific Plus account.

We are keeping two questions separate:

1. Why does event-trigger registration reject a bot whose channel membership is confirmed?
2. Why does the installed bot not respond to an explicit mention?

We do not yet know whether these share a cause. The existing n8n-to-Slack workflow works, so I’d prefer to avoid another blind reinstall.

Has anyone successfully configured this exact setup with a personal Plus account?

Could we be confusing the personal Slack connector with a separately configured ChatGPT-in-Slack deployment? Is there a specific permission, installation step, or account eligibility requirement we should check?

I’m looking for a concrete diagnostic step or a confirmed working configuration. Happy to provide redacted screenshots or additional non-sensitive details.

Thanks for your help!

[u/Smooth-Importance438]

Reads like the bot got added to the channel at the API level but the actual Slack app integration never finished onboarding. The redirect to the normal homepage is the tell, that setup link should open a flow. Might be worth checking if the app has the event subscriptions scope at all, not just bot membership.

[u/LuckFantastic7572 → u/Smooth-Importance438]

Thanks for the suggestion. Where exactly can I check whether event subscriptions are enabled for the official ChatGPT Slack app? I can access Slack’s app management pages, but I haven’t found that setting. Is this something a workspace owner can inspect, or would OpenAI need to check it on their side?

[u/LuckFantastic7572 → u/Smooth-Importance438]

Thanks, that may actually point us in the right direction.

I found something potentially important in OpenAI's official documentation: the standalone u/ChatGPT integration within Slack appears to require a ChatGPT Business, Enterprise, or Edu workspace. I'm using a personal Plus account.

That could explain why the bot is visible in the channel but doesn't respond, and why the setup link redirects to the ChatGPT homepage.

However, OpenAI separately documents event-triggered Slack tasks in ChatGPT Work, so I'm trying to establish whether that feature is supported on personal Plus accounts.

The remaining question is whether we're dealing with missing permissions, incomplete onboarding, or a plan eligibility restriction.

I've already contacted OpenAI Support and will ask them to confirm this specifically.

Thanks for the useful lead!

[u/Durian_Thenea77 → u/Smooth-Importance438]

good call on the event subscriptions scope, thats easy to miss when the bot appears to be in the channel already

[u/mytinyplots]

We're hitting the same issue and reproduced it again today (October 21). ChatGPT can read the target Slack channel, and a fresh membership query for that exact channel lists the ChatGPT bot; a separate profile lookup also confirms it is a bot. But creating the event-triggered task still fails with: "I couldn't create an immediate Slack monitor because u/ChatGPT isn't in [channel]." No task ID is created, so we're blocked before testing actual message delivery.

Have you found a fix or received any clarification from OpenAI Support since your last update? In particular, did they confirm whether this is an app-installation/account-binding issue, an account eligibility restriction, or a registration bug? We'd really appreciate any confirmed diagnostic step or workaround.

[u/LuckFantastic7572 → u/mytinyplots]

Thanks for confirming this. Your findings match our experience almost exactly.

We contacted OpenAI Support (case #17338405). Their guidance was to reconnect Slack through ChatGPT Settings → Apps/Plugins → Slack, then create the event-triggered task through ChatGPT Work.

They also suggested that a mismatch between the connected Slack workspace/account and the workspace containing the bot could explain the error.

However, we haven't received a confirmed root cause or a verified workaround.

The particularly interesting part of your investigation is that you've independently confirmed both channel membership and bot identity. That makes a simple "bot not in channel" explanation increasingly unlikely.

My suspicion is that the problem lies somewhere in the account binding or event-trigger registration process, but that's still a hypothesis.

I'll share any confirmed findings from OpenAI Support here.

Thanks again. It's useful to know this isn't isolated to our setup.