Skip to main content

Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets

Workflow preview

Workflow preview
100%
Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets preview
Open on n8n.io

1. Workflow Overview

Automates the full vulnerability lifecycle — from scheduled scanning and data aggregation to intelligent prioritization, ticket creation, real time alerting, weekly reporting, and centralized track...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.webhook, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.httprequest, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title
Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets
Workflow name
Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets

Automates the full vulnerability lifecycle — from scheduled scanning and data aggregation to intelligent prioritization, ticket creation, real-time alerting, weekly reporting, and centralized tracking. Ensures critical vulnerabilities are patched quickly while maintaining audit-ready logs and executive visibility.

How it works

  1. Dual Trigger - Scheduled daily scans at 6 AM + on-demand webhook for emergency scans
  2. Multi-Scanner Aggregation - Pulls findings from Nessus, Qualys, and custom scanner APIs in parallel
  3. Normalize & Deduplicate - Unifies scan results into a standard CVE schema, removes duplicates
  4. GPT-4 Risk Prioritization - AI enriches each vuln with exploitability context, business impact, and remediation urgency
  5. Severity Gate - Routes Critical/High vulns to expedited track; Medium/Low to standard queue
  6. Jira Ticket Creation - Auto-creates structured remediation tickets with SLA-based due dates
  7. Real-Time Alerting - Sends Slack alerts for Critical vulns and email digests for High findings
  8. Patch Verification - Checks remediation status against scanner re-scan results
  9. Weekly Executive Report - Generates CISO-ready KPI summary and sends to leadership
  10. Audit Log - Writes immutable compliance log to Google Sheets for SOC2/ISO 27001

Setup Steps

  1. Import workflow into n8n
  2. Configure credentials:
  • OpenAI API — GPT-4o for risk prioritization
  • Jira API — Ticket creation and tracking
  • Slack — Critical vulnerability alerts
  • Google Sheets — Vulnerability registry and audit log
  • SMTP / Gmail — Executive and team email reports
  1. Set your scanner API endpoints and tokens in aggregation nodes
  2. Configure Jira project key and SLA thresholds
  3. Set Slack channel IDs for security team alerts
  4. Schedule weekly report trigger to your preferred day/time
  5. Activate both the scheduled and webhook triggers

CVE Severity SLA Targets

  • 🔴 CRITICAL (CVSS 9.0–10.0) — Patch within 24 hours
  • 🟠 HIGH (CVSS 7.0–8.9) — Patch within 7 days
  • 🟡 MEDIUM (CVSS 4.0–6.9) — Patch within 30 days
  • 🟢 LOW (CVSS 0.1–3.9) — Patch within 90 days

Sample Scanner Payload (Nessus)

{
 "scanId": "SCAN-2025-0042",
 "scanner": "nessus",
 "targetHost": "192.168.1.105",
 "hostName": "prod-db-01",
 "cveId": "CVE-2024-21413",
 "cvssScore": 9.8,
 "pluginId": "212105",
 "description": "Microsoft Outlook RCE vulnerability"
}

Features

  • Multi-scanner normalization — Nessus, Qualys, and custom scanners unified
  • AI-powered exploit context — GPT-4 adds CISA KEV status, weaponization likelihood
  • SLA-driven Jira tickets — auto-assigns, sets due dates, links CVE details
  • Executive KPI dashboard — weekly metrics: MTTD, MTTR, patch compliance rate
  • Audit-ready log — every vuln tracked from detection to closure

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 - Sticky Note

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

Block 2 - Sticky Note1

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

Block 3 - Sticky Note2

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

Block 4 - Sticky Note3

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

Block 5 - Sticky Note4

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

Block 6 - Daily Scan Schedule — 6 AM

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 7 - On-Demand Emergency Scan Webhook

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

Block 8 - Merge Scan Triggers

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 9 - Build Scan Context

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

Block 10 - Fetch Nessus Scan Results

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

Block 11 - Fetch Qualys Scan Results

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

Block 12 - Fetch Custom Scanner Results

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

Block 13 - Normalize and Deduplicate Findings

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

Block 14 - GPT-4 AI Risk Prioritization

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

Block 15 - GPT-4o Model

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

Block 16 - Parse GPT-4 Risk Assessment

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

Block 17 - Severity Gate — Critical/High vs Medium/Low

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

Block 18 - Create Jira Ticket — Critical/High

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

Block 19 - Create Jira Ticket — Medium/Low

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

Block 20 - Slack Alert — Critical Vulnerabilities

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

Block 21 - Merge Post-Routing Paths

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 22 - Store to Vulnerability Registry

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.5

Block 23 - Check Patch Status in Registry

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.5

Block 24 - Email High Severity Digest

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

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

3. Summary Table

Workflow Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets
Complexity advanced
Nodes 31
Categories SecOps, AI Summarization
Author Oneclick AI Squad
Published 07 Nov 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/10594/10594.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

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

  4. 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. 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.

Frequently asked questions

What does Manage vulnerabilities end-to-end with GPT-4, Jira, Slack and Google Sheets do?

Automates the full vulnerability lifecycle — from scheduled scanning and data aggregation to intelligent prioritization, ticket creation, real time alerting, weekly reporting, and centralized track...

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.