Two Slack Apps Both Active in Same Channel . I Can't Remove One, Both Bots Responding

Questions
1

Hey everyone, need help untangling a Slack + n8n mess.
What happened:
I created two separate Slack apps, intending each for a different channel
Somehow both apps ended up integrated into the same channel
Now both bots respond when only one should
I can’t figure out how to remove one of the apps from that channel
My setup:
Two Slack apps, two OAuth credentials, two callback URLs
Two separate n8n workflows
Both apps currently active in the same channel
My questions:
How do I remove one Slack app from a specific channel without uninstalling it from the whole workspace?
Is there a way to restrict a Slack app to only one channel during setup?
Could the issue be that both apps are subscribed to the same workspace-level events instead of channel-specific ones?
Thanks in advance :folded_hands:

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:
3

Hey thanks benjamin sold advices, I was also wondering do I need to create 2 apps for different type of workflows?

I have disable one of the workflows for now but thinking like just one app is enough for multiple workflows

4

hi @Asim_Arman
Slack apps are installed at the workspace level, not per channel, so I usually keep a single Slack app for multiple workflows and add filtering in n8n (channel ID, event type, user, bot ID, etc.) so only the intended workflow responds in each channel.

5

Thank you so much. I think I am going to go with this in the future, I have currently deacitvied the other flow, but will proceed with this, as I willbe working with multiple work flow in the future