Predict and prevent service failures with Claude, ClickUp, and WhatsApp alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 30 nodes and runs on a schedule (cron 0 6 * * *) (plus 1 other trigger). Along the way it connects WhatsApp Business Cloud. It also calls api.anthropic.com over HTTP.
How it runs
Trigger: On a schedule (cron 0 6 * * *) (plus 1 other trigger).
- Set - Config (Edit Fields (Set)): sets 15 fields: servicesList, clickupListId, repoOwner…
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- Merge: merges the data from its input branches
- JS - Build Per-Service Risk Profiles & Detect Recurring Patterns (Code): runs custom JavaScript code
- HTTP Request: calls api.anthropic.com (POST)
- JS - Parse Failure Predictions (Code): runs custom JavaScript code
…plus 18 more steps. See the full node list below.
Services it uses
HTTP calls to: api.anthropic.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if
From the author
Quick overview This workflow runs daily to collect incident, deployment, metrics, log-volume, and GitHub code-churn history, builds per-service risk profiles, asks Anthropic Claude to predict which services are most likely to fail next, and creates preventive…