Slack - send message as bot

Questions
21

Any update to this old topic? I’m trying to us the Slack node to send as bot using OAuth2.

22

Hey @Felix_is_stuck,

For a bot the bot api token would be the way to handle it at the moment, I am not sure what happened with the PR maybe @RicardoE105 will know.

23

Hi Guys any update on this?

24

Hey @pb84,

You can already post as a bot by using the Access Token option and inputting a bot token, This is currently not an option when using OAuth. Do you need the OAuth option to also support this?

1 Like
25

Trying to conclude everything as long I have passed the whole process of finding the issue:

  1. Sending messages to Channels is only available using Slack Node connection using “Access Token”
  2. Access Token is Slack environment for the bot is not actually called simply as “Access Token”, but “OAuth Token”, so you need to go to API.SLACK.COM and choose “OAuth and Permissions” on the left menu.
  3. Copy “OAuth Token” in the section of “Bot Tokens” and use it to authorise your connection in n8n

image
image1440×1584 269 KB

  1. Don’t forget to add your BOT in the channel if the channel is PRIVATE.

image
image1570×862 104 KB

All that solved my problem! Hope you are as well

1 Like
26

Only today I I realised I use BOT TOKEN which has an expiration time. Tried to find a way to solve that, and seems that might be a common issue by using Slack and n8n or I might be wrong.

Raised a separate topic:

27

I’m having the exact same issue…
If I use just the “slack oath2 api” credential, the only choice I have is a client id and client secret with a callback url. It will not let you use the bot user oath token beginning in xoxb. When I try to send a message, it sends as myself. If I use “slack api” credential then I have the option of just using the bot user oath token which starts with xodb and it works fine. From my understanding, slack api is going to be deprecated in 2025 so its not a long term solution.

I’m using the self hosted community version 1.71.3