From 3796bd738ab5ef20da360faedefa6d95fc855f91 Mon Sep 17 00:00:00 2001 From: Gustavo Date: Mon, 24 Aug 2026 21:15:04 -0300 Subject: [PATCH] fix(v2): confirmed real Slack channel slug (chamados-suporte) Two more real test-send attempts (both with the user's standing authorization), each confirming a bit more of the pipeline and each correctly caught/recorded/surfaced by the failure branch -- no message ever actually reached Slack, exactly as the guard is designed to behave on failure: 1. channel "CHAMADOS SUPORTE" (as literally given) -> channel_not_found (Slack channel identifiers are always lowercase-hyphenated). 2. channel "chamados-suporte" -> not_in_channel: the channel resolved correctly this time, but the Bot Coordenador app is not yet a member of that channel (chat.postMessage requires channel membership without the chat:write.public scope). This is a Slack-side action for the user (invite the bot to the channel), not fixable from n8n config. Updated the channel value to the confirmed-correct slug. Reverted SEND_ENABLED to false, workflow deactivated, temp webhook removed. 158/158 tests passing. Co-Authored-By: Claude Sonnet 5 --- n8n/deployed/coordenador-glpi-v2.n8n.json | 2 +- n8n/workflow.template.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/n8n/deployed/coordenador-glpi-v2.n8n.json b/n8n/deployed/coordenador-glpi-v2.n8n.json index 98306b2..7afb81f 100644 --- a/n8n/deployed/coordenador-glpi-v2.n8n.json +++ b/n8n/deployed/coordenador-glpi-v2.n8n.json @@ -785,7 +785,7 @@ "channelId": { "__rl": true, "mode": "name", - "value": "CHAMADOS SUPORTE" + "value": "chamados-suporte" }, "text": "={{ $json.mensagem }}", "otherOptions": {} diff --git a/n8n/workflow.template.json b/n8n/workflow.template.json index 2e2f681..408796e 100644 --- a/n8n/workflow.template.json +++ b/n8n/workflow.template.json @@ -785,7 +785,7 @@ "channelId": { "__rl": true, "mode": "name", - "value": "CHAMADOS SUPORTE" + "value": "chamados-suporte" }, "text": "={{ $json.mensagem }}", "otherOptions": {}