The flow
Starts it 1Logic 12Service 5
The steps in the order they run, from what starts it.
- 1OpenObserve Alert TriggerOpen Observe triggerStarts it
- 2Set Incident Enrichment FieldsSetLogic
- 3Normalize Alert DataCodeLogic
- 4Prepare Log Search QueryCodeLogic
- 5Execute Alert Window QueryOpen ObserveService
- 6Find Closest Log AnchorCodeLogic
- 7Check for Log AnchorIfLogic
- 8Search Logs Near AnchorOpen ObserveService
- 9Compile Incident BriefCodeLogic
- 10Retrieve Notification CooldownData TableService
- 11Assess Notification NeedsCodeLogic
- 12Determine if Notification NeededIfLogic
- 13Check If Preview OnlyIfLogic
- 14Log Suppressed NotificationCodeLogic
- 15Log Notification PreviewCodeLogic
- 16Deliver Incident via NovuNovuService
- 17Store Notification CooldownData TableService
- 18Log Novu ResponseCodeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- 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 an event in a connected app.
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.