Slack Node Not Triggering Push Notifications (Despite Correct @Mention)

Hi n8n Community,
I’m hoping an expert can help me debug a very strange issue I’m having with the Slack node. I’ve built a workflow that successfully posts a message to a channel, but it is failing to generate a push notification on mobile or desktop.
My Goal:
My [AI] Zero Inbox Manager] workflow is designed to send an alert to my #sales-leads channel when a new prospect emails me.
What’s Working:
The n8n workflow runs successfully.
The Slack - Post Message node executes without errors.
The message does appear correctly in the #sales-leads channel.
The message text includes a direct, correctly formatted @mention to my username.
The Problem:
No push notification is received on my Mac desktop app or my phone for the messages sent by my n8n bot.
The Strange Part (What I’ve Tested):
I have confirmed that push notifications from Slack are working on both my devices. If I use Slack’s native /remind command, the notification from Slackbot comes through perfectly.
The issue seems to be exclusively with messages sent from the n8n bot via the API.
I have already invited the n8n bot into the private #sales-leads channel.
I have triple-checked all of my global and channel-specific notification settings in Slack to “All new messages.”
I have an open ticket with Slack support, and they have confirmed from their logs that they “detect the message” being posted, but “no notification gets generated.”
My Question for the Experts:
Has anyone else encountered an issue like this? Is there a specific scope, permission, or a subtle setting in the Slack App configuration that I might be missing that would cause only bot messages with mentions to be delivered silently?
I feel like I’m missing one final piece of the puzzle. Any advice would be hugely appreciated!
Thank you!

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

This usually happens because messages posted via bots are treated differently by Slack’s notification system. Even if the message includes an @mention, push notifications won’t trigger unless the bot has proper chat:write and users:read scopes and the mention is formatted using the user ID (e.g. <@U12345>), not just the username.

Also check these common causes:

  • :white_check_mark: Make sure the bot is a member of the channel (you already did).

  • :white_check_mark: Confirm the message is sent as the bot user, not a webhook or app-level token.

  • :white_check_mark: Try sending the mention dynamically via user ID to ensure Slack recognizes it as a real mention.

  • :white_check_mark: If the app uses a bot token, enable “Always notify for mentions from bots” in your notification preferences (under Notifications > Mentions).

If all of the above are correct and it’s still silent, it’s often on Slack’s side, they sometimes suppress notifications from automated messages unless explicitly configured to treat them as user mentions.

Slack doc : https://docs.slack.dev/

Could you please walk me through this step?

  • :white_check_mark: If the app uses a bot token, enable “Always notify for mentions from bots” in your notification preferences (under Notifications > Mentions).

When I go to my Notifications on the desktop app, I do not see the Mentions section where I can “Always notify for mentions from bots”

That option isn’t available for every workspace. Some Slack orgs don’t expose “Always notify for mentions from bots” in the desktop app. In that case, the only reliable fix is to make sure your bot formats mentions with the user ID (<@U12345>) and has the right scopes (chat:write, users:read). If the setting isn’t visible, it usually means Slack is handling bot notifications at the workspace level, and only Slack support can enable/change that behavior.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.