# Slack Trigger Node stopped working between two different channels **URL:** \ **Category:** Questions\ **Tags:** node, slack\ **Created:** [August 20, 2025, 3:26am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101 "2025-08-20T03:26:38Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Ageng\_Putra](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ageng_putra/32/111658_2.png) [@Ageng\_Putra](https://community.n8n.io/u/Ageng_Putra)\ **Post date:** [August 20, 2025, 3:26am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/1 "2025-08-20T03:26:38Z")
## 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: **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? ---
**Author:** ![khmuhtadin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/khmuhtadin/32/111661_2.png) [@khmuhtadin](https://community.n8n.io/u/khmuhtadin)\ **Post date:** [August 20, 2025, 3:40am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/2 "2025-08-20T03:40:57Z")
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. ---
**Author:** ![Ageng\_Putra](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ageng_putra/32/111658_2.png) [@Ageng\_Putra](https://community.n8n.io/u/Ageng_Putra)\ **Post date:** [August 20, 2025, 3:48am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/3 "2025-08-20T03:48:25Z")
Hi, appreciate your reply — thank you! 🙏 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. ---
**Author:** ![khmuhtadin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/khmuhtadin/32/111661_2.png) [@khmuhtadin](https://community.n8n.io/u/khmuhtadin)\ **Post date:** [August 20, 2025, 4:06am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/4 "2025-08-20T04:06:50Z")
yes, the second options also a good fix ---
**Author:** ![Ageng\_Putra](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ageng_putra/32/111658_2.png) [@Ageng\_Putra](https://community.n8n.io/u/Ageng_Putra)\ **Post date:** [August 20, 2025, 4:06am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/5 "2025-08-20T04:06:59Z")
> [@khmuhtadin](#): > > 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 update it worked normally after upgrading n8n version, thank you ---
**Author:** ![khmuhtadin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/khmuhtadin/32/111661_2.png) [@khmuhtadin](https://community.n8n.io/u/khmuhtadin)\ **Post date:** [August 20, 2025, 4:08am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/6 "2025-08-20T04:08:40Z")
if you find this helpfull please marked as solved thanks ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [August 27, 2025, 4:09am UTC](https://community.n8n.io/t/slack-trigger-node-stopped-working-between-two-different-channels/172101/7 "2025-08-27T04:09:12Z")
Closed on August 27, 2025, 4:09am UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.