Issue with Multiple Slack Triggers in Separate Workflows

[_https_hjm79.top]

Description:
I am encountering an issue with using multiple Slack Triggers across different workflows in n8n. Even though each workflow uses a separate Slack App and a distinct webhook URL, enabling the Slack Trigger in one workflow causes the Slack Trigger in the other workflow to stop functioning.

Setup Details:

1. I created two workflows:

• Workflow A: Configured with Slack App A and its webhook URL.
• Workflow B: Configured with Slack App B and a different webhook URL.

2. Both workflows are designed to trigger on messages from specific Slack channels:

• Workflow A listens to Channel A.
• Workflow B listens to Channel B.

3. The Slack Triggers are connected to their respective Slack Apps, and each has unique webhook URLs.

Issue:

• When I activate the Slack Trigger in Workflow A, it works as expected, but the Slack Trigger in Workflow B stops functioning.
• Conversely, if I reactivate the Slack Trigger in Workflow B, Workflow A’s trigger stops working.

Troubleshooting Steps Taken:

1. Verified that both Slack Apps are properly configured with different webhook URLs.
2. Confirmed that no other workflows or Slack Apps are using the same webhook URL.
3. Tested both workflows individually, and they function correctly when only one trigger is active.
4. Tried using separate n8n instances for each workflow, and this seems to resolve the issue, but it is not an ideal solution due to added complexity.

Expected Behavior:

Each Slack Trigger should operate independently, even if they are configured in separate workflows with different Slack Apps and webhook URLs.

Request:

• Is this a known limitation or a bug in n8n’s Slack Trigger implementation?
• Are there any recommended solutions to allow multiple Slack Triggers to function simultaneously within the same n8n instance?

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[Jon]

Hey @_https_hjm79.top

Which version of n8n are you using? I know Slack has a limitation with the trigger URLs but I didn’t think our node did as I don’t remember adding anything to block more than one being used.