Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

SecretOps, DevSecOps Real Time Repos Secret Leak Remediation SecretOps is an n8n security automation workflow that monitors Git push events, detects high risk secrets in commits, and automatically ...

Best for

SecOps automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.switch, n8n-nodes-base.aggregate, @n8n/n8n-nodes-langchain.lmchatopenrouter, n8n-nodes-base.githubtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Taiwo Hassan.

Original n8n.io source

1.1 Workflow description

Title: Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude
Workflow name: Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude

SecretOps, DevSecOps Real-Time Repos Secret Leak Remediation

SecretOps is an n8n security automation workflow that monitors Git push events, detects high-risk secrets in commits, and automatically responds in real time.

Unlike typical scanners that only notify, SecretOps acts immediately:

Revokes leaked AWS access keys
Creates incident tickets in Jira
Alerts the security team via Slack
Uses AI as a Security Analyst to decide the correct response

This workflow demonstrates how n8n can function as a lightweight SOAR (Security Orchestration, Automation, and Response) system for DevOps teams.

🚨 The Problem

Developers sometimes commit secrets such as:

AWS access keys
Payment processor API keys (Paystack / Stripe)
Database connection URLs

These leaks can result in:

Cloud infrastructure takeover
Financial theft
Full database compromise

Most tools detect and notify. SecretOps detects and reacts.

🧠 How It Works

1) Git Push Webhook

SecretOps listens to repository push events from GitHub/GitLab.

2) Deterministic Secret Detection (Code Node)

A Code node scans changed files and extracts only high-impact secrets:

AKIA... → AWS access keys
sk_live_, pk_test_ → payment processor keys
postgres://, mongodb://, mysql://, redis:// → database URLs

3) AI Security Analyst

An AI node receives detected items and decides the correct action:

REVOKE_AWS_KEY
PAYMENT_PROCESSOR_KEY_ALERT
ROTATE_DB_PASSWORD
IGNORE_KEY

It also generates ready-to-use Jira ticket content and Slack alert messages.

4) Automated Response (Switch)

Action	Automated Response
REVOKE_AWS_KEY	Disable key in AWS IAM → Create Jira ticket → Send Slack alert
PAYMENT_PROCESSOR_KEY_ALERT	Create Jira ticket → Send Slack alert
ROTATE_DB_PASSWORD	Create Jira ticket → Send Slack alert
IGNORE_KEY	End workflow

⚡ What Makes This Unique

Immediate containment of AWS key leaks (set to Inactive automatically)
AI used for decision-making, not detection
Built-in incident workflow for developers and security teams
Minimal false positives by focusing only on real, high-risk secrets
Shows n8n as a practical DevSecOps automation tool

🧩 Requirements

GitHub or GitLab webhook
AWS credentials with IAM permissions
Jira project access
Slack webhook or bot token
n8n with AI node enabled

🛡️ Real-World Impact

SecretOps turns secret leaks from a silent vulnerability into an immediate, traceable, and automated incident response — reducing the window of exploitation from hours to seconds.

Ideal for DevOps, security teams, and engineering organizations that want proactive protection without complex security tooling.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Switch

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.4

Block 2 - Aggregate

Type / Role: n8n-nodes-base.aggregate - aggregate
Config choices: Version 1

Block 3 - OpenRouter Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 4 - Github Trigger On Push

Type / Role: n8n-nodes-base.githubTrigger - githubTrigger
Config choices: Version 1

Block 5 - Code - Extract Useful Field-1

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Fetch - Commit Changes From Github

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 7 - Code - RegEx Scanner

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - AI - Classifier

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3.1

Block 9 - Code - Formatter

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 10 - Get - UserName From AWS

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 11 - Rename

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - Revoke AccessKey On AWS

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 13 - Send a message notification-1

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 14 - Send a message notification-2

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 15 - Send a message notification-3

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 16 - Create an issue for leaked key

Type / Role: n8n-nodes-base.jira - jira
Config choices: Version 1

Block 17 - Create an issue for exposed database url

Type / Role: n8n-nodes-base.jira - jira
Config choices: Version 1

Block 18 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Code - Hash Leaked Value

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 23 - If row does not exist

Type / Role: n8n-nodes-base.dataTable - dataTable
Config choices: Version 1.1

Block 24 - Save To DataTable-1

Type / Role: n8n-nodes-base.dataTable - dataTable
Config choices: Version 1.1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude
Complexity	advanced
Nodes	26
Categories	SecOps, AI Summarization
Author	Taiwo Hassan
Published	26 Apr 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15314/15314.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source SecOps workflows AI Summarization workflows

Frequently asked questions

What does Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps, AI Summarization use case.

Taiwo Hassan

4 workflows

Nodes

n8n-nodes-base.switch n8n-nodes-base.aggregate @n8n/n8n-nodes-langchain.lmchatopenrouter n8n-nodes-base.githubtrigger n8n-nodes-base.code n8n-nodes-base.httprequest @n8n/n8n-nodes-langchain.agent n8n-nodes-base.set

Complexity

advanced

Published 26 Apr 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15314/15314.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Generate incident response reports with Supabase, Gemini and Claude

## Quick Overview This workflow ingests incident and playbook content from GitHub into Supabase (including pgvector embeddings with Google Gemini) and, on a webhook trigger, enriches a test incident with historical matches, a routed response playbook, and live web threat intel (via Tavily + OpenRouter) to generate a validated incident response report. ## How it works 1. Receives a POST webhook containing the incident payload (including an encrypted OpenRouter API key) and decrypts the key for downstream LLM calls. 2. Creates a tracking row in a Supabase table and loads configuration values used by the retrieval and report-generation steps. 3. Retrieves similar resolved incidents from a Supabase pgvector store using Google Gemini embeddings and returns structured historical patterns. 4. Retrieves the best-matching reference playbook from a Supabase pgvector store and fetches the full playbook text from Supabase, falling back to a built-in generic playbook when no match is found. 5. Uses Tavily Search plus an OpenRouter-backed agent to gather external threat intelligence, IOCs, and phased mitigation guidance when the incident is classified as security-relevant. 6. Merges the three intelligence branches and uses an OpenRouter LLM to synthesize a structured JSON output and an 11-section Markdown incident response report. 7. Validates that required report fields exist and, if valid, writes the structured output and Markdown report back to the Supabase test incident record; otherwise it skips the write. ## Setup 1. Create Supabase tables for test incidents and vector stores (for resolved incidents and reference playbooks) and configure the matching SQL functions used for retrieval (for example, `match_resolved_incidents_v1` and `match_reference_playbooks_v1`). 2. Add Supabase credentials in n8n and set the correct table names and query function names in the workflow’s configuration nodes. 3. Add Google Gemini (PaLM) API credentials and ensure the embedding model name used in the config (for example, `models/gemini-embedding-001`) is available to your account. 4. Add an OpenRouter API credential for the chat models used by the agents and synthesizer, and ensure your webhook caller sends an `encrypted_openrouter_key` value that matches the workflow’s decryption format. 5. Add a Tavily API credential for web search, then copy the webhook URL and configure your incident source to POST the incident JSON to it.

View

Check JWT security of API endpoints with HTTP requests and Google Sheets

## Quick Overview This workflow reads API endpoints and JWTs from Google Sheets, tests each endpoint with multiple token scenarios using HTTP requests, and writes a risk-scored security summary back to Google Sheets. ## How it works 1. Triggers manually (or on an optional daily schedule). 2. Loads the target Google Sheets document ID and the endpoint/results tab names. 3. Reads endpoint definitions from Google Sheets and keeps only rows marked as active. 4. For each endpoint, decodes the provided JWT and generates test variants (no auth, tampered payload, and alg:none). 5. Sends HTTP requests to the endpoint using the valid token and, if that succeeds, repeats the request with each test token variant and captures the response status codes. 6. Evaluates the status codes and token metadata to flag issues (for example, unauthenticated access, tampered token acceptance, alg:none acceptance, or missing exp) and assigns a risk level. 7. Appends the timestamped results and summary to the results tab in Google Sheets. ## Setup 1. Create a Google Sheet with an endpoints tab containing columns like `label`, `endpoint_url`, `method`, `token`, and `active`, and a results tab with columns like `timestamp`, `label`, `risk_level`, `t1_valid`, `t2_no_auth`, `t3_tampered`, `t4_alg_none`, and `summary`. 2. Add a Google Sheets Service Account credential in n8n and share the spreadsheet with the service account email. 3. Update the Sheet ID and tab names in the workflow’s variables (Sheet ID, endpoints sheet name, and results sheet name). 4. Ensure each endpoint row includes a valid JWT in the `token` column and set `active` to TRUE for endpoints you want to test. 5. If you want it to run automatically, enable the schedule trigger and adjust the cron expression as needed.

View

Monitor SSL certificate expiry with Google Sheets, Slack, Gmail and Jira

## Quick Overview This workflow runs daily to check SSL certificate expiry for domains listed in Google Sheets, using ssl-checker.io to fetch certificate details, then creating Jira issues and sending Slack and Gmail alerts for risky certificates while logging results and posting a daily Slack digest. ## How it works 1. Runs every day at 08:00 on a schedule trigger. 2. Reads the domain list from a Google Sheets “Domains” sheet and filters out blank rows or domains marked as disabled. 3. Processes domains one by one, calling the ssl-checker.io API to retrieve each site’s live SSL certificate details. 4. Calculates days remaining until expiry, assigns a status (Expired, Critical, Warning, Healthy, or Unknown), and flags items that require attention. 5. For certificates that need attention, creates a Jira task and sends an alert to Slack and an email via Gmail with the certificate details. 6. For healthy certificates, writes the latest check results to a Google Sheets “Log” sheet. 7. Aggregates all results from the run into a single summary message and posts the daily digest to Slack. ## Setup 1. Create a Google Sheet with a “Domains” sheet containing at least a `domain` column (and optionally an `enabled` column) and a “Log” sheet to store results, then add your Google Sheets credentials and set the spreadsheet ID. 2. Add an API key for ssl-checker.io (or a compatible SSL lookup endpoint) and place it in the HTTP Authorization header. 3. Add your Jira credentials and set the target project key for ticket creation. 4. Add your Slack credentials and set the channel ID used for alerts and the daily digest. 5. Add your Gmail credentials and set the recipient address for email alerts. 6. (Optional) Adjust the warning and critical thresholds (30 and 7 days) in the expiry calculation code if your policy differs.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Detect and remediate leaked secret on repo with GitHub, AWS, Jira, Slack, Claude

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

SecretOps, DevSecOps Real-Time Repos Secret Leak Remediation

🚨 The Problem

🧠 How It Works

1) Git Push Webhook

2) Deterministic Secret Detection (Code Node)

3) AI Security Analyst

4) Automated Response (Switch)

⚡ What Makes This Unique

🧩 Requirements

🛡️ Real-World Impact

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Switch

Block 2 - Aggregate

Block 3 - OpenRouter Chat Model

Block 4 - Github Trigger On Push

Block 5 - Code - Extract Useful Field-1

Block 6 - Fetch - Commit Changes From Github

Block 7 - Code - RegEx Scanner

Block 8 - AI - Classifier

Block 9 - Code - Formatter

Block 10 - Get - UserName From AWS

Block 11 - Rename

Block 12 - Revoke AccessKey On AWS

Block 13 - Send a message notification-1

Block 14 - Send a message notification-2

Block 15 - Send a message notification-3

Block 16 - Create an issue for leaked key

Block 17 - Create an issue for exposed database url

Block 18 - Sticky Note

Block 19 - Sticky Note1

Block 20 - Sticky Note2

Block 21 - Sticky Note3

Block 22 - Code - Hash Leaked Value

Block 23 - If row does not exist

Block 24 - Save To DataTable-1

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions