Automate security incident triage with GPT-4o-mini and Gmail notifications
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.
Nodes used (4)
- Webhook
n8n-nodes-base.webhook - OpenAI
@n8n/n8n-nodes-langchain.openAi - Gmail
n8n-nodes-base.gmail - Edit Fields (Set)
n8n-nodes-base.set
What it does
What this workflow does ----------------------- Automatically triages inbound security findings (e.g., from AWS Security Hub via EventBridge → SNS → Webhook), classifies them with an LLM, generates a 3-step remediation plan, and emails a compact incident brief. Pipeline: Webhook → CleanFinding (normalize) → Classify (LLM) → Plan (LLM) → Gmail (email). You can substitute Microsoft Teams, Slack, etc. - Normalizes the incoming finding JSON (title, description, account, resource id/type, updatedat). - Uses an LLM to assign incidenttype, severity (P0--P3), urgency, shorttitle, and why (concise rationale). - Produces a 3-step remediation plan with ownerhint and successcriteria---kept atomic and practical. - Sends a clean HTML email with all details (subject line includes short title, resource, and account). Category: Security / Cloud / Incident Management\ Time to set up: ~10--15 minutes\ Difficulty: Beginner--Intermediate\ Cost: Mostly free (n8n CE; OpenAI usage + Gmail/SMTP as used) What you'll need ---------------- - An n8n instance reachable over HTTP (for the Webhook node). - OpenAI (or compatible) credentials set in n8n. - Gmail OAuth2 credentials (or swap Gmail node for SMTP). - A source that can POST a Security-Hub-style finding to your webhook (EventBridge/SNS, a SIEM, or curl). Output (Email) - Subject: <shorttitle> - <resourceid> in <accountid> - Body: HTML summary with Type, Account, Urgency, Why, Next Actions (3 steps), Owner, Success criteria.