“The Cursor bot is not in this channel. Invite the bot to the channel to use it with automations.”
This happens on automation “Argus Automation - Layer 2 (comprehensive report to Slack #1)” targeting Slack channel ID C0BKFUAR0BD (Nubank workspace T024U97V8).
The Cursor app already appears in that channel’s Integrations/Apps in Slack. Re-inviting with /invite @Cursor and re-saving the automation does not clear the alert/error.
Related closed reports:
Steps to Reproduce
Open Cursor Automations → “Argus Automation - Layer 2 (comprehensive report to Slack #1)”
Set Slack MCP target to channel C0BKFUAR0BD
In Slack, confirm Cursor app is already in that channel (Integrations/Apps)
Run the automation
Observe Slack MCP error: bot is not in this channel
Expected Behavior
If the Cursor Slack app is already in the channel, Automations Slack MCP should read/post there without this error.
Hey there! Taking your direct question first: no, this isn’t the missing OAuth scopes issue from those two March threads. Different cause.
Your invite did go through - the Cursor app is registered in that channel on our side, so there’s no need to keep re-inviting or re-saving.
The warning is advisory rather than a hard block. If it’s stopping you at save, confirm through the warning dialog and the automation will still save and run. Membership is checked live at send time, so if the bot is in the channel the post should go through.
Why you’re seeing it: on workspaces with a very large number of channels, the membership check can time out and fall back to an incomplete channel list for up to an hour. When your channel isn’t in that list, it reports the bot as missing even though it’s there. Nothing you’ve misconfigured, and it’s an issue we’re tracking.
Could you give that a try and let me know whether the message actually posts? That tells me whether this is only a stale warning or the run itself is blocked, and the two need different fixes on our side. I’ll post here when there’s an update.
Hi Mohit, I tried once again and had no success (same issue)… Found an sdditional critical symptom that may explain it, Slack OAuth does not persist:
I complete the Slack OAuth flow for Automations / Slack MCP.
Cursor shows that OAuth succeeded / connected.
When I click “Manage” on that Slack connection, it immediately returns me to the same OAuth connect page, as if Slack was never connected.
This reproduces every time. So the UI success state is false: the Slack integration is not actually staying connected. That likely explains the Automations error “The Cursor bot is not in this channel…” even though the Cursor app appears installed in Slack channel C0BKFUAR0BD.
