Monitor daily traffic spikes with Databox, OpenAI and 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 22 nodes and runs on a schedule (every day at 10:00). Along the way it connects OpenAI Chat Model, Slack and MCP Client.
How it runs
Trigger: On a schedule (every day at 10: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
- sessions (MCP Client): uses MCP Client
- sessions (MCP Client): uses MCP Client
- new users (MCP Client): uses MCP Client
- new users (MCP Client): uses MCP Client
- ad costs (MCP Client): uses MCP Client
- clicks (MCP Client): uses MCP Client
- cllicks (MCP Client): uses MCP Client
…plus 9 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 (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Aggregate
n8n-nodes-base.aggregate - AI Agent
@n8n/n8n-nodes-langchain.agent - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - MCP Client
@n8n/n8n-nodes-langchain.mcpClient
From the author
Autonomous Traffic Spike Reporting: Databox, AI & Slack This workflow gives PPC agencies and performance teams a daily traffic and performance check across multiple clients using Databox data. It pulls yesterday’s and day-before-yesterday’s data for key…