AI-Powered SEO Cannibalization Monitor: Databox, Google Search Console & Slack
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 AI workflow has 15 nodes and runs on a schedule (every week at 09:00). Along the way it connects OpenAI Chat Model, MCP Client and Slack.
How it runs
Trigger: On a schedule (every week at 09:00).
- Set client data (Code): runs custom JavaScript code
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- Aggregate: combines items into one
- GSC impressions (MCP Client): uses MCP Client
- GSC position (MCP Client): uses MCP Client
- SEO Keyword Cannibalization Detector (AI Agent): runs an AI agent, with model: OpenAI Chat Model
- Merge: merges the data from its input branches
- Send Cannibalization Alert (Slack): uses Slack
- Aggregate: combines items into one
- Combine data (Code): runs custom JavaScript code
…plus 2 more steps. See the full node list below.
Services it uses
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 - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Aggregate
n8n-nodes-base.aggregate - Code
n8n-nodes-base.code - MCP Client
@n8n/n8n-nodes-langchain.mcpClient - AI Agent
@n8n/n8n-nodes-langchain.agent - Slack
n8n-nodes-base.slack - Merge
n8n-nodes-base.merge
From the author
AI-Powered SEO Cannibalization Monitor: Databox, Google Search Console & Slack This workflow runs weekly and checks multiple client websites for potential SEO cannibalization issues using Google Search Console data from Databox. It pulls page-level…