The flow
Starts it 1Model 1Logic 10Service 6
The steps in the order they run, from what starts it.
- 1Run Every HourSchedule triggerStarts it
- 2ConfigurationSetLogic
- 3Fetch GitHub AdvisoriesHttp RequestService
- 4Fetch NVD CVEsHttp RequestService
- 5Fetch n8n ReleasesHttp RequestService
- 6Fetch JPCERT RSSHttp RequestService
- 7Fetch JVN RSSHttp RequestService
- 8Wait for All SourcesMergeLogic
- 9Parse Releases XMLXmlLogic
- 10Parse JPCERT XMLXmlLogic
- 11Parse JVN XMLXmlLogic
- 12Filter New AdvisoriesCodeLogic
- 13Any New Items?IfLogic
- 14Summarize with ClaudeAnthropicModel
- 15No New ItemsNo OpLogic
- 16Format Slack MessageCodeLogic
- 17Send Slack AlertSlackService
- 18Save Notified IDsCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 18, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. 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. 18 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 18 steps before you point it at anything that matters.