Block 1 - Hourly Traffic Monitor1
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.3
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 p...
n8n-nodes-base.scheduletrigger, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.set, n8n-nodes-base.slack, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.aggregate, @n8n/n8n-nodes-langchain.agent
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by n8n Lab.
Original n8n.io sourceThis 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 metrics, compares changes, analyzes the results with AI, and sends both client-level and cross-client reports to Slack.
You can ask Databox Genie to provide the correct data source IDs and metric keys for each client, then format them in the same structure as the example Code node.
The workflow sends two reports:
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.
| Workflow | Monitor daily traffic spikes with Databox, OpenAI and Slack |
|---|---|
| Complexity | advanced |
| Nodes | 27 |
| Categories | Market Research, AI Summarization |
| Author | n8n Lab |
| Published | 13 May 2026 |
Use the JSON export at /data/workflows/15696/15696.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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 p...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI Summarization use case.