Manage mobile canary rollouts with Anthropic Claude 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 22 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects WhatsApp Business Cloud. It also calls api.anthropic.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Code: runs custom JavaScript code
- Set - Config (Edit Fields (Set)): sets 11 fields: rolloutStages, observationWindowMinutes, crashRateDeltaThreshold…
- Wait: waits 60 minutes
- HTTP Request: calls an HTTP API
- HTTP Request: calls an HTTP API
- Merge: merges the data from its input branches
- Code: runs custom JavaScript code
- Code: runs custom JavaScript code
- API 1 - AI Rollout Recommendation (Claude) (HTTP Request): calls api.anthropic.com (POST)
- Code: runs custom JavaScript code
…plus 10 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)
- Webhook
n8n-nodes-base.webhook - Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Wait
n8n-nodes-base.wait - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Switch
n8n-nodes-base.switch - If
n8n-nodes-base.if - WhatsApp Business Cloud
n8n-nodes-base.whatsApp
From the author
Quick overview This workflow monitors a mobile app canary rollout by fetching crash/ANR and API error/latency metrics, comparing them to the previous release baseline, asking Anthropic Claude for a proceed/pause/rollback recommendation, and then updating…