Automation library · Alerts and monitoring

Diagnose incident root causes and plan remediation with Claude

Started by another system calling it, and works across WhatsApp. 30 steps, 2 branches, 2 loops or waits: large, and worth reading before you trust it with anything live.

Large

30 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 2Logic 13Service 15

The steps in the order they run, from what starts it.

  1. 1Webhook - Incident TriggeredWebhookStarts it
  2. 2Manual Trigger - Test RunManual triggerStarts it
  3. 3Set - ConfigSetLogic
  4. 4HTTP Request - Fetch Application LogsHttp RequestService
  5. 5HTTP Request - Fetch Metrics SnapshotHttp RequestService
  6. 6HTTP Request - Fetch Distributed TracesHttp RequestService
  7. 7HTTP Request - Fetch Recent CommitsHttp RequestService
  8. 8HTTP Request - Fetch Recent Pull RequestsHttp RequestService
  9. 9HTTP Request - Fetch Infrastructure Change LogHttp RequestService
  10. 10HTTP Request - Fetch Recent DeploymentsHttp RequestService
  11. 11Merge - Combine All Evidence SourcesMergeLogic
  12. 12JS - Build Unified Timeline & Correlate EventsCodeLogic
  13. 13HTTP Request - Claude: Identify Probable Root CauseHttp RequestService
  14. 14JS - Parse Root Cause AnalysisCodeLogic
  15. 15HTTP Request - Claude: Rank Evidence & Build Remediation PlanHttp RequestService
  16. 16JS - Parse Remediation PlanCodeLogic
  17. 17WhatsApp - Send Root Cause ReportWhats AppService
  18. 18Wait - For Human DecisionWaitLogic
  19. 19IF - Execute Remediation PlanIfLogic
  20. 20HTTP Request - Trigger Remediation ActionHttp RequestService
  21. 21Set - Case Status DismissedSetLogic
  22. 22WhatsApp - Send Remediation StartedWhats AppService
  23. 23Wait - For Remediation Verification Grace PeriodWaitLogic
  24. 24HTTP Request - Re-Fetch Metrics SnapshotHttp RequestService
  25. 25JS - Evaluate Post-Remediation HealthCodeLogic
  26. 26IF - Incident ResolvedIfLogic
  27. 27Set - Case Status ResolvedSetLogic
  28. 28Set - Case Status EscalatedSetLogic
  29. 29WhatsApp - Send Resolution ConfirmedWhats AppService
  30. 30WhatsApp - Send Escalation (Remediation Ineffective)Whats AppService

How it's built

Starts on
Another system calling it
Steps
30, with 2 branches, 2 loops or waits
Size
Large: read it before trusting it with anything live
Connects to
WhatsApp
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own WhatsApp 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?

Take your time. At 30 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.

Before you run it

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 30 steps before you point it at anything that matters.