Automated GA4 analytics data backfill to BigQuery with Telegram alerts

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow automates the daily backfill of Google Analytics 4 (GA4) data into BigQuery. It fetches 13 essential pre processed reports (including User Acquisition, Traffic, and E commerce) and up...

Best for

Market Research automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.googleanalytics, n8n-nodes-base.googlebigquery, n8n-nodes-base.set, n8n-nodes-base.scheduletrigger, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.telegram, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Aliz.

Original n8n.io source

1.1 Workflow description

Title: Automated GA4 analytics data backfill to BigQuery with Telegram alerts
Workflow name: Automated GA4 analytics data backfill to BigQuery with Telegram alerts

This workflow automates the daily backfill of Google Analytics 4 (GA4) data into BigQuery. It fetches 13 essential pre-processed reports (including User Acquisition, Traffic, and E-commerce) and uploads them to automatically created tables in BigQuery, and then send an alert in telegram.

How it works

Configuration: You define your Project ID, Dataset, and Date Range in a central "Config" node.
Parallel Fetching: The workflow runs 13 parallel API calls to GA4 to retrieve key reports (e.g., ga4_traffic_sources, ga4_ecommerce_items).
Dynamic Tables: It automatically checks if the target BigQuery table exists and creates it with the correct schema if it's missing.
Telegram Alerts: After execution, it sends a summary message to Telegram indicating success or failure for the day's run.

Set up steps

Google Credentials (OAuth): This workflow uses n8n's built-in "Google OAuth2 API" credential. You do not need a Service Account key. Connect your Google account and ensure you grant scopes for Google Analytics API and BigQuery API.
Config Node: Open the "Backfill Config" node and fill in:
- GA4 Property ID
- Google Cloud Project ID
- BigQuery Dataset ID
Telegram Setup (Optional): If you want alerts, configure the Telegram node with your Bot Token and Chat ID. If not, you can disable/remove this node.
Schedule: By default, this is set to run daily. It is recommended to use a date expression (e.g., Today - 2 Days) to allow GA4 time to process data fully before fetching.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - GA4 - Session Channel Group

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 2 - BQ - ga4_data_session_channel_group

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 3 - GA4 - Session Source/Campaign/Medium

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 4 - BQ - ga4_data_session_source_campaign_medium

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 5 - GA4 - Country/Language/City

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 6 - BQ - ga4_data_country_language_city

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 7 - GA4 - Item Name

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 8 - BQ - ga4_data_item_name

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 9 - GA4 - Browser/OS/Device

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 10 - BQ - ga4_data_browser_os_device

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 11 - GA4 - First User Source/Medium

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 12 - BQ - ga4_data_first_user_source_medium

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 13 - GA4 - First User Channel Group

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 14 - BQ - ga4_data_first_user_channel_group

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 15 - GA4 - Ads Data

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 16 - BQ - ga4_ads_data

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 17 - GA4 - All Metrics

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 18 - BQ - ga4_all_metrics_data

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 19 - GA4 - Event Metrics

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 20 - BQ - ga4_event_metrics_data

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 21 - GA4 - Page Location

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 22 - BQ - ga4_page_location_data

Type / Role: n8n-nodes-base.googleBigQuery - googleBigQuery
Config choices: Version 2.1

Block 23 - GA4 - Landing Page

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Block 24 - GA4 - Transaction Items

Type / Role: n8n-nodes-base.googleAnalytics - googleAnalytics
Config choices: Version 2

Showing the first 24 of 34 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Automated GA4 analytics data backfill to BigQuery with Telegram alerts
Complexity	advanced
Nodes	34
Categories	Market Research
Author	Aliz
Published	19 Nov 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/11010/11010.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Download workflow JSON Original n8n.io source Market Research workflows

Frequently asked questions

What does Automated GA4 analytics data backfill to BigQuery with Telegram alerts do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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 use case.

Aliz

1 workflow

Nodes

n8n-nodes-base.googleanalytics n8n-nodes-base.googlebigquery n8n-nodes-base.set n8n-nodes-base.scheduletrigger n8n-nodes-base.merge n8n-nodes-base.code n8n-nodes-base.telegram n8n-nodes-base.stickynote

Complexity

advanced

Published 19 Nov 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/11010/11010.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Automated GA4 analytics data backfill to BigQuery with Telegram alerts

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

How it works

Set up steps

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - GA4 - Session Channel Group

Block 2 - BQ - ga4_data_session_channel_group

Block 3 - GA4 - Session Source/Campaign/Medium

Block 4 - BQ - ga4_data_session_source_campaign_medium

Block 5 - GA4 - Country/Language/City

Block 6 - BQ - ga4_data_country_language_city

Block 7 - GA4 - Item Name

Block 8 - BQ - ga4_data_item_name

Block 9 - GA4 - Browser/OS/Device

Block 10 - BQ - ga4_data_browser_os_device

Block 11 - GA4 - First User Source/Medium

Block 12 - BQ - ga4_data_first_user_source_medium

Block 13 - GA4 - First User Channel Group

Block 14 - BQ - ga4_data_first_user_channel_group

Block 15 - GA4 - Ads Data

Block 16 - BQ - ga4_ads_data

Block 17 - GA4 - All Metrics

Block 18 - BQ - ga4_all_metrics_data

Block 19 - GA4 - Event Metrics

Block 20 - BQ - ga4_event_metrics_data

Block 21 - GA4 - Page Location

Block 22 - BQ - ga4_page_location_data

Block 23 - GA4 - Landing Page

Block 24 - GA4 - Transaction Items

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions