The flow
Starts it 1Logic 10Service 5
The steps in the order they run, from what starts it.
- 1Webhook - Monitoring AlertWebhookStarts it
- 2Code 1 - Parse, Classify & Deduplicate AlertCodeLogic
- 3ClickUp - Create Incident TaskClick UpService
- 4Wait 1 - Debounce WindowWaitLogic
- 5API 1 - AI Root Cause Analysis (Claude)Http RequestService
- 6Code 2 - Parse RCA & Decide Remediation PathCodeLogic
- 7IF - Confidence & Risk GateIfLogic
- 8Wait 2 - Safety Override WindowWaitLogic
- 9Code 4 - Build Human Escalation ReportCodeLogic
- 10API 2 - Trigger Cursor Background AgentHttp RequestService
- 11Wait - Test & Deploy PeriodWaitLogic
- 12Wait 3 - Build, Test & Deploy Grace PeriodWaitLogic
- 13Merge - Rejoin Auto-Fix & Escalation PathsMergeLogic
- 14Code 3 - Evaluate Agent Outcome & Deployment StatusCodeLogic
- 15ClickUp - Update Incident with ResolutionClick UpService
- 16WhatsApp - Notify On-CallWhats AppService
How it's built
- Starts on
- Another system calling it
- Steps
- 16, with 1 branch, 4 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- ClickUp, WhatsApp
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own ClickUp and WhatsApp accounts. 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.
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 16 steps before you point it at anything that matters.