Automated Wazuh rule deployment pipeline with GitHub, XML validation & Telegram alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs on Github events. Along the way it connects GitHub and Telegram.
How it runs
Trigger: On Github events.
- Valid Commit for Deployment (If): checks a condition and branches into true / false
- Extract Changed Files (Code): runs custom JavaScript code
- Download Rule (HTTP Request): calls an HTTP API
- Upload a file (SSH): uses SSH
- Rule Validation (SSH): uses SSH
- Rule Validation check (If): checks a condition and branches into true / false
- Deploying the Rules (SSH): uses SSH
- Rules deployment failed (Telegram): uses Telegram
- Restart Wazuh_manager (SSH): uses SSH
- Final Confirmation check (If): checks a condition and branches into true / false
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Github Trigger
n8n-nodes-base.githubTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - SSH
n8n-nodes-base.ssh - Telegram
n8n-nodes-base.telegram - No Operation, do nothing
n8n-nodes-base.noOp - If
n8n-nodes-base.if
From the author
🚀 Say Goodbye to Manual Rule Deployments in Wazuh! Just Commit— Let Your Pipeline Auto‑Deploy via GitHub + n8n 🎯 👨💻 Tired of This Endless Cycle? Create rule → Validate → Copy to server → Restart Wazuh → Notify team Repeat that every week — you’re…