The flow
Starts it 2Logic 13Service 7
The steps in the order they run, from what starts it.
- 1⏱️ Trigger – Scheduled ScanSchedule triggerStarts it
- 2 ERROR – On FailureError triggerStarts it
- 3🔐 AUTH – Login to NessusHttp RequestService
- 4🛠️ UTILS – Set Grouped DataSetLogic
- 5🔐 AUTH – Set API TokenSetLogic
- 6Code1CodeLogic
- 7🌐 DISC – Initialize Network SegmentsFunctionLogic
- 8📄 EXPORT – Sheet AppendGoogle SheetsService
- 9🌐 DISC – Discover AssetsHttp RequestService
- 10🧠 AI – Process AssetsFunctionLogic
- 11🔄 UTILS – Split AssetsSplit OutLogic
- 12🧪 SCAN – Run NessusHttp RequestService
- 13🔍 SCAN – Process VulnerabilitiesFunctionLogic
- 14🤖 AI – Risk EvaluationFunctionLogic
- 15📊 AI – Triage VulnerabilitiesFunctionLogic
- 16🚦 ALERT – LEV TriggerIfLogic
- 17🛠️ UTILS – Field EditorSetLogic
- 18📧 Alert Security TeamEmail SendService
- 19📝 REPORT – Generate SummaryFunctionLogic
- 20CodeCodeLogic
- 21Send EmailEmail SendService
- 22📄 EXPORT – Save to SheetGoogle SheetsService
How it's built
- Starts on
- A clock
- Steps
- 22, with 1 branch
- Size
- Large: read it before trusting it with anything live
- Connects to
- Email, Google Sheets
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email and Google Sheets 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.