Detect search intent drift in Google SERPs with Claude and WhatsApp alerts
Ready for 3.0What this workflow does
This workflow has 28 nodes and runs on a schedule (every 24 hours) (plus 2 other triggers). Along the way it connects WhatsApp Business Cloud. It also calls api.anthropic.com over HTTP.
How it runs
Trigger: On a schedule (every 24 hours) (plus 2 other triggers).
- Normalize Trigger Input Data (Code): runs custom JavaScript code
- Set Configuration Parameters (Edit Fields (Set)): sets 11 fields: historicalWindowSize, minPeriodsForDrift, driftConfidenceThreshold…
- Determine Trigger Mode (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Build Queue from Ad Hoc Keyword (Code): runs custom JavaScript code
- Fetch Tracked Keywords (HTTP Request): calls an HTTP API
- Retrieve Next Keyword from Queue (Code): runs custom JavaScript code
- Build Queue from Tracked Keywords (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Build Final Drift Digest (Code): runs custom JavaScript code
…plus 15 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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Webhook
n8n-nodes-base.webhook - Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Quick overview This workflow monitors Google SERP changes for tracked keywords by storing daily SERP snapshots, classifying dominant intent over time with Anthropic Claude, detecting meaningful intent drift, and sending WhatsApp alerts and a run digest. How…