From cbfb1ba039682075307313203ef9277059bf9267 Mon Sep 17 00:00:00 2001 From: chemavx Date: Thu, 9 Jul 2026 20:54:21 +0000 Subject: [PATCH] feat(n8n): inyectar TELEGRAM_BOT_TOKEN/CHAT_ID desde telegram-notify-infisical MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Para que el workflow 'Health Check General' lea el token del bot de notificaciones via process.env en vez de hardcodearlo (rotación 2026-07-09). Co-Authored-By: Claude Fable 5 --- n8n/deployment-n8n.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/n8n/deployment-n8n.yaml b/n8n/deployment-n8n.yaml index 8033d5f..a6e516b 100644 --- a/n8n/deployment-n8n.yaml +++ b/n8n/deployment-n8n.yaml @@ -45,6 +45,19 @@ spec: secretKeyRef: name: n8n-secret-infisical key: GETXAPI_TOKEN + # Token del bot @chemavx_bot (notificaciones) — rotado 2026-07-09. + # Lo consume el workflow "Health Check General" vía process.env, + # ya no hardcodeado. Fuente: Infisical homelab/prod/telegram. + - name: TELEGRAM_BOT_TOKEN + valueFrom: + secretKeyRef: + name: telegram-notify-infisical + key: TELEGRAM_BOT_TOKEN + - name: TELEGRAM_CHAT_ID + valueFrom: + secretKeyRef: + name: telegram-notify-infisical + key: TELEGRAM_CHAT_ID # n8n ≥1.x bloquea $env en expresiones por defecto; sin esto el nodo # HTTP del autopost no puede leer GETXAPI_TOKEN. Instancia single-user. - name: N8N_BLOCK_ENV_ACCESS_IN_NODE