Monitor exposed secrets in GitHub and CI logs with WhatsApp alerts
Ready for 3.0What this workflow does
This workflow has 27 nodes and runs on a schedule (cron 0 */6 * * *) (plus 1 other trigger). Along the way it connects WhatsApp Business Cloud.
How it runs
Trigger: On a schedule (cron 0 */6 * * *) (plus 1 other trigger).
- Set - Config (Edit Fields (Set)): sets 6 fields: repoOwner, repoName, baseBranch…
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- JS - Scan Content for Secret Patterns & Compute Entropy Scores (Code): runs custom JavaScript code
- Switch: routes items into 3 branches
- Set - Cloud Verification Params (Edit Fields (Set)): sets 4 fields: verificationPass, verificationApiUrl, verificationAuthHeader…
- Set - VCS Verification Params (Edit Fields (Set)): sets 3 fields: verificationPass, verificationApiUrl, verificationAuthHeader
- Set - Payment Verification Params (Edit Fields (Set)): sets 3 fields: verificationPass, verificationApiUrl, verificationAuthHeader
- Set - Mark Unverifiable (Generic) (Edit Fields (Set)): sets 2 fields: verified, verificationNote
- HTTP Request: calls an HTTP API
…plus 15 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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - If
n8n-nodes-base.if - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - Wait
n8n-nodes-base.wait
From the author
Quick overview This workflow runs every 6 hours (or on demand) to scan GitHub commits and CI/CD logs for leaked secrets, verify suspected credentials against GitHub and Stripe when possible, score risk severity, and send WhatsApp alerts with a remediation…