Back to Catalog

Automate google analytics reporting

Alex KimAlex Kim
17329 views
2/3/2026
Official Page

Automate Google Analytics Reporting with n8n

This n8n workflow collects, processes, and formats Google Analytics data into a comprehensive HTML report. The report is segmented into three primary categories: Engagement Stats, Search Results, and Country Views. The formatted report can be emailed or saved as a document, and the workflow includes error handling and logging for better debugging.

Overview

Purpose

To automate the extraction, processing, and presentation of Google Analytics data in a visually appealing and structured format for easier insights and decision-making.

Features

  • Data Parsing: Individual parsers process raw Google Analytics data for different time periods and categories.
  • Data Aggregation: Combines parsed data into a single structured JSON object.
  • HTML Report Generation: Formats the aggregated data into an HTML table with color-coded segments for better readability.
  • Email or Document Output: The formatted report can be emailed or saved as a Google Doc (will need additional setup).
  • Error Handling: Includes checks for missing data and detailed error messages for debugging.

Workflow Steps

  1. Data Fetching:

    • Six separate Google Analytics data pulls:
      • Page Engagement Stats (This Week and Prior Week)
      • Google Search Results (This Week and Prior Week)
      • Country Views (This Week and Prior Week)
  2. Data Parsing:

    • Each data pull is processed using a dedicated parser node to generate a URL-safe string.
    • Example nodes:
      • Parse - Get Page Engagement This Week
      • Parse - Country Views Prior Week
  3. Data Aggregation:

    • Aggregates parsed data into a structured JSON object using the Aggregate Data node.
    • Ensures consistency and handles missing or malformed data.
  4. HTML Report Generation:

    • Creates a formatted HTML report with color-coded tables for each segment:
      • Engagement Stats: Green
      • Search Results: Blue
      • Country Views: Orange
    • Includes headers and neatly formatted tables for each data set.
  5. Output:

    • The report can be sent via email using the Gmail API or saved to Google Docs.
    • Example nodes:
      • Gmail node for email delivery.
      • Google Docs node for saving the report as a document.

Requirements

Prerequisites

  • Google Cloud Setup:
    • Enable Google Analytics API.
    • Enable Gmail API (if using email output).
    • Generate OAuth credentials for API access.
  • n8n Installation:

Environment Variables

  • Ensure API credentials and tokens are set up in the n8n environment.
  • Update the respective nodes with client ID, client secret, and access tokens.

Configuration

Google Analytics

  • Configure the Get Report nodes with the appropriate property ID and metrics.
  • Ensure correct date ranges are selected for each node.

Formatting Node

  • The Format Data node processes aggregated data and generates the HTML content.
  • Customize the HTML styling and segment colors as needed.

Email Node

  • Configure the Gmail node with OAuth credentials.
  • Set the recipient email address and subject line dynamically.

Error Handling

Common Issues

  1. Authentication Errors:

    • Ensure OAuth credentials are correct.
    • Verify that the APIs are enabled in the Google Cloud Console.
  2. Empty Data:

    • Check the raw data from Google Analytics.
    • Validate the property ID and query parameters in the Get Report nodes.
  3. Parsing Errors:

    • Ensure the parser nodes are correctly configured and match the expected input format.

Debugging

  • Use debug logs in each node to identify data flow issues.
  • Add error-handling nodes to capture and log issues during execution.

Example Usage

  1. Run the Workflow
    • Trigger the workflow to fetch, process, and format Google Analytics data.
  2. Verify Output
    • Check the formatted HTML output in the debug logs.
    • Ensure the email or Google Doc contains the correctly formatted report.

Future Enhancements

  • Add support for additional metrics or dimensions.
  • Integrate with Slack for notifications.
  • Enable scheduling for automated reports.
  • Add a visual dashboard for real-time analytics.

Automate Google Analytics Reporting

This n8n workflow simplifies and automates the process of extracting data from Google Analytics and sending reports via email. It's designed to help you regularly monitor your website's performance without manual intervention.

What it does

  1. Triggers on a schedule: The workflow can be set to run automatically at predefined intervals (e.g., daily, weekly, monthly) using the "Schedule Trigger" node. It can also be triggered manually for ad-hoc reports.
  2. Fetches Google Analytics Data: It connects to your Google Analytics account to retrieve specified analytics data.
  3. Processes Data: A "Code" node is included, suggesting that the workflow can perform custom data manipulation or formatting on the fetched analytics data.
  4. Prepares Email Content: The "Edit Fields (Set)" node is used to define or modify data, likely structuring the analytics information into a format suitable for email.
  5. Sends Email Report: Finally, the workflow uses the "Gmail" node to send an email containing the processed Google Analytics report to a designated recipient.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Analytics Account: Access to a Google Analytics account with the necessary permissions to retrieve data.
  • Google Account (for Gmail): A Google account connected to Gmail for sending emails.
  • n8n Credentials:
    • Google OAuth2 credentials configured in n8n for both Google Analytics and Gmail.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Locate the "Google Analytics" node and configure your Google OAuth2 credentials.
    • Locate the "Gmail" node and configure your Google OAuth2 credentials.
  3. Customize Google Analytics Query:
    • Open the "Google Analytics" node.
    • Specify the View ID, date range, metrics, and dimensions you wish to retrieve.
  4. Customize Data Processing (Optional):
    • If needed, modify the "Code" node to perform custom transformations on your analytics data.
  5. Configure Email Content:
    • Adjust the "Edit Fields (Set)" node to structure the data for your email report.
    • Open the "Gmail" node.
    • Set the recipient email address, subject, and body of the email. You can use expressions to dynamically include data from previous nodes in the email body.
  6. Set Schedule (Optional):
    • If you want the workflow to run automatically, configure the "Schedule Trigger" node with your desired interval (e.g., daily, weekly, monthly).
  7. Activate the Workflow: Once configured, activate the workflow to enable scheduled runs or execute it manually using the "When clicking โ€˜Execute workflowโ€™" trigger.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch ๐Ÿ”— LinkedIn โ€“ Wessel Bulte

Wessel BulteBy Wessel Bulte
247

๐ŸŽ“ How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From โ€“ senderโ€™s email address To โ€“ recipientโ€™s email address Subject โ€“ email subject line Summary โ€“ short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits โœ… Full Automation: Eliminates manual reading and data entry from incoming emails. โœ… Multi-Source Integration: Handles data from different email providers seamlessly. โœ… AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. โœ… Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. โœ… Time Efficiency: Processes emails in real time, improving productivity and response speed. *โœ… Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) ๐Ÿง  AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative โ€” all powered by AI logic, sir. --- ๐Ÿ’ก Key Advantages โšก Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. ๐Ÿง  AI Qualification Engine An OpenAI-powered Agent evaluates the leadโ€™s industry, region, and needs to generate a persona summary and routing rationale. ๐Ÿ“Š Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. ๐Ÿ’ฌ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. ๐Ÿ” Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- โš™๏ธ How It Works HubSpot Trigger โ€“ Captures a new lead as soon as itโ€™s created in HubSpot. Fetch Contact Data โ€“ Retrieves all relevant fields like name, company, and industry. Clean & Format Data โ€“ A Code node standardizes and structures the data for consistency. Airtable Record Creation โ€“ Logs the lead data into the โ€œLeadsโ€ table for centralized tracking. AI Agent Qualification โ€“ The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update โ€“ Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification โ€“ Sends a real-time message tagging the rep with lead info. Gmail Notification โ€“ Sends a personalized handoff email with context and follow-up actions. HubSpot Sync โ€“ Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- ๐Ÿ› ๏ธ Setup Steps Trigger Node: HubSpot โ†’ Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the โ€œLeadsโ€ table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- ๐Ÿ” Credentials Required HubSpot OAuth2 API โ€“ To fetch and update leads. Airtable Personal Access Token โ€“ To store and update lead data. OpenAI API โ€“ To power the AI qualification and matching logic. Slack OAuth2 โ€“ For sending team notifications. Gmail OAuth2 โ€“ For automatic email alerts to assigned reps, sir. --- ๐Ÿ‘ค Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- ๐Ÿ’ฌ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular โ€” perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113