The flow
Starts it 4Logic 6Service 6
The steps in the order they run, from what starts it.
- 1When Nivs Incident Webhook CalledWebhookStarts it
- 2If Request Includes FileIfLogic
- 3Extract Incident Data from FileExtract From FileService
- 4Merge Payload and Extracted DataMergeLogic
- 5Parse Incident Fields from FileCodeLogic
- 6Route by Incident TypeSwitchLogic
- 7Submit Initial Warning ReportNksc NivsService
- 8Submit Minor Cyber IncidentNksc NivsService
- 9Submit Major Cyber IncidentNksc NivsService
- 10Submit Near Miss IncidentNksc NivsService
- 11If Nivs Returned ErrorIfLogic
- 12Return Error ResponseRespond To WebhookStarts it
- 13If Input Came from FileIfLogic
- 14Return Json ResponseRespond To WebhookStarts it
- 15Convert Result to FileConvert To FileService
- 16Return File Download ResponseRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 16, with 4 branches
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
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.