Same Slack Bot cannot run simultaneously on two workflows

Hi everyone!

I stumbled upon a weird limitation.

I have 2 separate workflows (use-cases). Each workflow has a “Get Message” trigger from Slack and they listen to 2 different Slack Channels. Obviously, I have the same webhook URL, which is configured in the " Event Subscriptions" setting in Slack.

If both workflows are active, non of them gets triggered. If only one is active, then it works fine.

Maybe I am missing something, but I don’t see a reason why would this be an issue. It’s a completely normal use-case - you have one Slack bot, who can trigger multiple workflows. Obviously I can make 1 big workflow combining everything, and have a filtering mechanism to determine which path to take, but this seems like a nonsense. Use-cases are different and it doesn’t make sense to be in one workflow.

Can anyone help with this?

Both nodes have the same settings. The only difference is the Slack channel ID.

Thanks,

Yeah I faced the same issue. For me I configured two separate apps on slack which meant two separate webhook URLs. However, when I installed the second app on my slack workspace, the first one stopped working. And when I reinstalled the first app on my workspace, the second app stopped working. Ofcourse I had two separate workflows and Slack credentials setup on n8n for both the bots.

I would like for both the apps to work simultaneously. Any help on this would be highly appreciated. Thanks!

I found out it’s a Slack limitation. So you need to use different Webhook URLs. If you copy-paste the Get Message node from one workflow to the other and just change the credentials, it will still use the same URL and this is a conflict. You should recreate the Get Message node.

I prefer this is a n8n issue, they should allow the webhook url to be reused, but it seems that listening to the whole workspace and split the flow is the only walkaround to listen multiple channels at this time.

maybe one main workflow with the webhook, then split and call the respective sub-worfklows based on the logic.

That will be a great granular networking addition to mapping URLs internally.

One Credential running concurrently in multiple active workflows based on the input.