Slack Trigger Node stopped working between two different channels

Questions
,
1

Describe the problem/error/question

I have two separate workflows, each using a different Slack app integration:

  • Staging channel → uses trigger-app 1

  • Production channel → uses trigger-app 2

The issue:
The Slack Trigger node stops working when both workflows are active. After some testing, I found that n8n does not respond to the second trigger if one has already responded.

For example:

  • If I trigger in the staging channel, it works fine.

  • But when I later try to trigger in the production channel, it does not work at all — despite having:

    • Different workflows

    • Different Slack apps/webhooks

    • Both workflows in active state

Temporary workaround:
I need to re-activate the workflow every time I switch channels. For example, if I trigger staging first and then want to trigger production, I have to re-activate the production workflow. Otherwise, there’s no response at all.

What is the error message (if any)?

No error message — just no response from the production workflow.

Please share your workflow

I can’t share the full workflow because it contains company credentials. But I can confirm that:

  • Both workflows are valid

  • Both are in an active state

  • Each has its own production webhook registered for its Slack app

Information on your n8n setup

  • n8n version: 1.102.3
  • Database: default (not using external DB)
  • EXECUTIONS_PROCESS setting: default
  • Running via: Docker
  • Operating system: Ubuntu 24.04 (x86_64)

Question:

  • Is this the expected behavior when running multiple Slack Trigger nodes on different workflows/channels? Or is this a bug in the current version of n8n?

  • If it’s a bug, is there a more robust workaround than manually re-activating workflows each time, until a fix is released?

2

In release 1.102.x, there was an additional bug: n8n registered the listener only for the first trigger, so other workflows would never receive the webhook unless re-activated. This issue was reported on the forum and GitHub, and has been patched since version 1.105.2 (and all newer releases).

Recommended solutions:

• Upgrade n8n
The latest version resolves the “second trigger ignored” bug. After upgrading, workflows using different Slack apps will work independently.

• Use a single Slack Trigger with internal routing
If both workflows handle the same type of event, it’s more reliable to use one Slack Trigger and then:
a. Add a Switch node to differentiate event.channel (staging vs production).
b. In each branch, use Call Workflow to delegate the specific logic.
This way, deduplication happens only once, but you still get two separate executions (main + sub-workflow) and don’t need to manually re-activate workflows.

1 Like
3

Hi, appreciate your reply — thank you! :folded_hands:
I’ll try upgrading my n8n to the suggested version.
I tried checking the release notes for version 1.105.2 and newer, but I couldn’t find any mention that this issue was patched. Could you please share the specific release note or link to the patch? I’d really appreciate it.

For the second option, I separated the workflows so it’s easier to record and maintain for each environment.

4

yes, the second options also a good fix

5

update
it worked normally after upgrading n8n version, thank you

6

if you find this helpfull please marked as solved

thanks

1 Like