Block 1 - Detect GA4 Anomalies
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Who’s it for Teams that monitor traffic, signups, or conversions in Google Analytics 4 and want automatic Slack/email alerts when a channel suddenly spikes or drops. What it does This n8n template ...
n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.slack, n8n-nodes-base.gmail, n8n-nodes-base.scheduletrigger, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Artur.
Original n8n.io sourceTeams that monitor traffic, signups, or conversions in Google Analytics 4 and want automatic Slack/email alerts when a channel suddenly spikes or drops.
This n8n template pulls daily GA4 metrics, detects outliers with a rolling mean and z-score, and sends alerts with a sparkline chart. It supports per-channel analysis (e.g., sessionDefaultChannelGroup) and consolidates multiple anomalies into a single email while posting each one to Slack.
sessions, newUsers, conversions, bounceRate by date + channel.alert === true and optional ALERT_ME toggle.In the GA UI:
481356553).From the URL (quick way):
When you’re inside the GA4 property, the URL looks like:
…/analytics/web/#/p123456789/… → the digits after p are your Property ID (123456789 in this example).
What not to use:
G-XXXXXXX) — that’s the data stream ID, not the property ID.UA-XXXXX-Y) — those are legacy and won’t work with GA4 Data API.In this template:
Put that numeric ID into the Set → PROPERTY_ID field. The HTTP node path properties/{{ $json.PROPERTY_ID }}:runReport expects only the number, no prefixes.
PROPERTY_ID, LOOKBACK_DAYS, ALERT_PCT, Z_THRESHOLD, CHANNEL_DIM, ALERT_ME.Subject → {{$json.emailSubject}} and HTML body → {{$json.emailHtml}}. Keep Execute once enabled.WINDOW/MA_WINDOW) and chart range (LAST_N_DAYS_CHART).CHANNEL_DIM (e.g., source/medium) to analyze different dimensions.Z_THRESHOLD or ALERT_PCT.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.
| Workflow | Ga4 anomaly detection with automated Slack & email alerts |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | Market Research, Multimodal AI |
| Author | Artur |
| Published | 26 Aug 2025 |
Use the JSON export at /data/workflows/7912/7912.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.
Who’s it for Teams that monitor traffic, signups, or conversions in Google Analytics 4 and want automatic Slack/email alerts when a channel suddenly spikes or drops. What it does This n8n template ...
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, Multimodal AI use case.