# Predict and prevent service failures with Claude and ClickUp: n8n workflow > Started by a clock, and works across WhatsApp. 30 steps, 3 branches, 1 loop or waits: large, and worth reading before you trust it with anything live. Source: https://millionrounds.com/workflow/predict-and-prevent-service-failures-with-claude-and-clickup (Millionrounds; every figure on the page links to its filing or article) [Automation library](https://millionrounds.com/workflows) · [Alerts and monitoring](https://millionrounds.com/workflows?category=Alerts+and+monitoring#library) # Predict and prevent service failures with Claude and ClickUp Started by a clock, and works across WhatsApp. 30 steps, 3 branches, 1 loop or waits: large, and worth reading before you trust it with anything live. Large [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fpredict-and-prevent-service-failures-with-claude-and-clickup) **30 steps** Large: read it before trusting it with anything live **3** Branches: places the flow splits **1** Loop or waits **1** Service it connects to ## The flow Starts it 2 Logic 15 Service 13 The steps in the order they run, from what starts it. - 1 **Schedule Trigger - Daily** Schedule trigger *Starts it* - 2 **Manual Trigger - Test Run** Manual trigger *Starts it* - 3 **Set - Config** Set *Logic* - 4 **HTTP Request - Fetch Historical Incident Log** Http Request *Service* - 5 **HTTP Request - Fetch Deployment History** Http Request *Service* - 6 **HTTP Request - Fetch Metrics Trend Data** Http Request *Service* - 7 **HTTP Request - Fetch Error Log Volume Trend** Http Request *Service* - 8 **HTTP Request - Fetch Code Change Activity** Http Request *Service* - 9 **Merge - Combine All Historical Sources** Merge *Logic* - 10 **JS - Build Per-Service Risk Profiles & Detect Recurring Patterns** Code *Logic* - 11 **HTTP Request - Claude: Predict Services Likely to Fail** Http Request *Service* - 12 **JS - Parse Failure Predictions** Code *Logic* - 13 **Switch - Route By Risk Level** Switch *Logic* - 14 **WhatsApp - Send Urgent Risk Alert** Whats App *Service* - 15 **HTTP Request - Create Standard Preventive Task** Http Request *Service* - 16 **Set - Logged Only (No Action)** Set *Logic* - 17 **HTTP Request - Create Urgent Preventive Task** Http Request *Service* - 18 **JS - Attach Task Id to Prediction Record** Code *Logic* - 19 **Wait - For Prediction Verification Window** Wait *Logic* - 20 **HTTP Request - Re-Fetch Incident Log For Service** Http Request *Service* - 21 **HTTP Request - Fetch Preventive Task Status** Http Request *Service* - 22 **Merge - Combine Incident Check & Task Status** Merge *Logic* - 23 **JS - Build Prediction Outcome Record** Code *Logic* - 24 **IF - Incident Occurred During Window** If *Logic* - 25 **WhatsApp - Alert Prediction Confirmed (Incident Occurred)** Whats App *Service* - 26 **IF - Preventive Task Completed** If *Logic* - 27 **Set - Case Status Prediction Confirmed** Set *Logic* - 28 **WhatsApp - Send Prevention Success Summary** Whats App *Service* - 29 **Set - Case Status No Incident Task Pending** Set *Logic* - 30 **Set - Case Status Prevented Successfully** Set *Logic* ## How it's built - **Starts on:** A clock - **Steps:** 30, with 3 branches, 1 loop 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 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 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. ## Run it in n8n - **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n) - **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fpredict-and-prevent-service-failures-with-claude-and-clickup) - **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts. Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind. ## Connects to Each opens the other workflows that use it. [WhatsApp](https://millionrounds.com/workflows?service=WhatsApp#library) ## Workflows like it Also alerts and monitoring, with the same services where possible, closest in size first. - [**Diagnose incident root causes and plan remediation with Claude** 30 steps · WhatsApp](https://millionrounds.com/workflow/diagnose-incident-root-causes-and-plan-remediation-with-clau) - [**Email cleaner with Gmail and WhatsApp** 28 steps · Gmail, WhatsApp](https://millionrounds.com/workflow/email-cleaner-with-gmail-and-whatsapp) - [**Triage AWS security posture changes with Claude and Slack** 28 steps · calls a model · Email, Slack](https://millionrounds.com/workflow/triage-aws-security-posture-changes-with-claude-and-slack) - [**Monitor exposed secrets in GitHub and CI logs with WhatsApp** 27 steps · WhatsApp](https://millionrounds.com/workflow/monitor-exposed-secrets-in-github-and-ci-logs-with-whatsapp) - [**Monitor engineering health across ClickUp, GitHub and APM** 25 steps · WhatsApp](https://millionrounds.com/workflow/monitor-engineering-health-across-clickup-github-and-apm) - [**Monitor engineering health with ClickUp and GitHub** 25 steps · WhatsApp](https://millionrounds.com/workflow/monitor-engineering-health-with-clickup-and-github)