The flow
Starts it 1Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Fetch Technology Watchlist CSVHttp RequestService
- 3Read Watchlist CSVExtract From FileService
- 4Fetch Recent CVEs from NVDHttp RequestService
- 5Match CVEs to WatchlistCodeLogic
- 6Deduplicate AlertsCodeLogic
- 7Prepare EPSS LookupCodeLogic
- 8Fetch EPSSHttp RequestService
- 9Attach EPSS ScoreCodeLogic
- 10Fetch KEV from GitHub MirrorHttp RequestService
- 11Attach KEVCodeLogic
- 12Prioritize & Build DigestCodeLogic
- 13Send Email DigestGmailService
- 14Send Slack DigestSlackService
How it's built
- Starts on
- A clock
- Steps
- 14
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail 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. 14 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.
Nothing 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 14 steps before you point it at anything that matters.