Detect and route cybersecurity threats with SIEM, Slack, email and PagerDuty
Ready for 3.0What this workflow does
This workflow has 16 nodes and runs on a schedule (every 15 minutes). Along the way it connects Slack and Postgres. It also calls api.threatintel.com and api.pagerduty.com over HTTP.
How it runs
Trigger: On a schedule (every 15 minutes).
- Fetch Network Logs (HTTP Request): calls an HTTP API (POST)
- Fetch Vulnerability Scan Results (HTTP Request): calls an HTTP API (POST)
- Fetch Threat Intelligence Feed (HTTP Request): calls api.threatintel.com
- Merge: merges the data from its input branches
- Analyze & Detect Threats (Code): runs custom JavaScript code
- Check Threat Severity (If): checks a condition and branches into true / false
- Send Slack Alert - Critical (Slack): uses Slack
- Send Email: sends an email over SMTP
- Log Medium/Low Threats (HTTP Request): calls an HTTP API (POST)
- Create PagerDuty Incident (HTTP Request): calls api.pagerduty.com (POST)
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: api.threatintel.com, api.pagerduty.com
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 (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Send Email
n8n-nodes-base.emailSend - Postgres
n8n-nodes-base.postgres
From the author
This n8n workflow proactively scans and aggregates threat intelligence, network logs, and vulnerability data every 15 minutes to detect emerging risks across the infrastructure. It analyzes anomalies, correlates indicators, assigns severity, triggers critical…