The flow
Starts it 1Logic 5Service 10
The steps in the order they run, from what starts it.
- 1Schedule Trigger - Every 15 MinutesSchedule triggerStarts it
- 2Fetch Network LogsHttp RequestService
- 3Fetch Vulnerability Scan ResultsHttp RequestService
- 4Fetch Threat Intelligence FeedHttp RequestService
- 5Merge All Threat DataMergeLogic
- 6Analyze & Detect ThreatsCodeLogic
- 7Check Threat SeverityIfLogic
- 8Send Slack Alert - CriticalSlackService
- 9Send Email Alert - DetailedEmail SendService
- 10Log Medium/Low ThreatsHttp RequestService
- 11Create PagerDuty IncidentHttp RequestService
- 12Create Security TicketHttp RequestService
- 13Store in DatabasePostgresService
- 14Merge All PathsMergeLogic
- 15Generate Summary ReportCodeLogic
- 16Send Summary to Monitoring ChannelSlackService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Email, Postgres, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email, Postgres and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.