Audit workflows for hardcoded secrets with GitHub and Telegram
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 12 nodes and runs on a schedule (every day at 03:00). Along the way it connects GitHub and Telegram.
How it runs
Trigger: On a schedule (every day at 03:00).
- Configuration (Edit Fields (Set)): sets 6 fields: repoOwner, repoName, repoPath…
- Get All Workflows (n8n): uses n8n
- Scan and Redact (Code): runs custom JavaScript code
- Loop Over Workflows (Loop Over Items (Split in Batches)): loops over the items in batches
- Build Audit Report (Code): runs custom JavaScript code
- Check Snapshot Exists (GitHub): get (file)
- Only If Something Found (Filter): keeps only the items that match a condition
- Snapshot Exists? (If): checks a condition and branches into true / false
- Send Audit Report (Telegram): uses Telegram
- Update Redacted Snapshot (GitHub): edit (file)
…plus 1 more step. 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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - n8n
n8n-nodes-base.n8n - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - GitHub
n8n-nodes-base.github - If
n8n-nodes-base.if - Filter
n8n-nodes-base.filter - Telegram
n8n-nodes-base.telegram
From the author
Quick overview Scans every workflow on your n8n instance for credentials, tokens, and personal data pasted straight into node parameters. Findings are reported to Telegram by severity, and the snapshot committed to GitHub has those values masked. How it works…