Skip to main content

Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup

Workflow preview

Workflow preview
100%
Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This n8n workflow automatically retrieves the monthly CrUX (Chrome User Experience) Report from Google BigQuery and updates the data in NocoDB . It removes the previous month’s data before insertin...

Best for

  • Document Extraction automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.googlebigquery, n8n-nodes-base.nocodb, n8n-nodes-base.splitinbatches, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup
Workflow name
Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup

Overview

This n8n workflow automatically retrieves the monthly CrUX (Chrome User Experience) Report from Google BigQuery and updates the data in NocoDB.
It removes the previous month’s data before inserting the new dataset, ensuring your database always contains the latest CrUX rankings for website origins.
The flow is fully automated, using schedule triggers to handle both data cleanup and data insertion each month.


Tasks

  • ⏰ Runs automatically on a monthly schedule
  • 🔢 Converts the month name to a numeric value for table selection
  • 🧹 Deletes last month’s CrUX data from NocoDB
  • 🌐 Queries Google BigQuery for the latest monthly dataset
  • 💾 Inserts the new CrUX rankings into NocoDB
  • ⚙️ Keeps your database up to date with zero manual effort

🛠 How to Use

1️⃣ Set Up BigQuery Access

  • Connect your Google BigQuery credentials.
  • Make sure your project includes access to the chrome-ux-report public dataset.

2️⃣ Adjust the Query

  • In the Google BigQuery node, change the LIMIT value to control how many top-ranked sites are retrieved.
  • Ensure the {{ $json.table }} field correctly references the dataset for the desired month (e.g., 202509).

3️⃣ Prepare NocoDB Table

  • Create a table in NocoDB with fields: origin, crux_rank, and any additional metadata you wish to track.

4️⃣ Schedule Automation

  • The workflow includes two Schedule Trigger nodes:
    • One runs the data cleanup process (deletes last month).
    • One runs the data insertion for the new month.

5️⃣ Run or Activate the Workflow

  • Activate it to run automatically each month.
  • You can also run it manually to refresh data on demand.

📋 Prerequisites

Before running this workflow, make sure you complete the following setup steps:

  • 🧱 Enable BigQuery API

  • 📊 Access the Chrome UX Report Dataset

  • 🔑 Connect BigQuery to n8n

    • In n8n, create credentials for your Google BigQuery account using Service Account Authentication.
    • Ensure the account has permission to query the chrome-ux-report dataset.
  • 🗄️ Create a NocoDB Table

    • In NocoDB, create a new table to store your CrUX data with the following fields:
      • origin → Short text
      • crux_rank → Number
  • ⚙️ Connect NocoDB to n8n

    • Use your NocoDB API Token to connect and allow the workflow to read/write data.

What is CrUX Rank?

CrUX Rank (Chrome User Experience Rank) is a metric from Google’s Chrome UX Report (CrUX) dataset that indicates a website’s popularity based on real user visits.
It reflects how frequently an origin (website) is loaded by Chrome users around the world.

  • A lower rank number means the site is more popular (e.g., rank 1 = top site).
  • The data is collected from anonymized Chrome usage statistics, aggregated monthly.
  • This rank helps you track site popularity trends and compare your domain’s visibility over time.

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 - Google BigQuery

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

Block 2 - Get Last Month Data

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 3 - Delete in NocoDB

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 4 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 5 - Append Crux Data into NocoDB

Type / Role
n8n-nodes-base.nocoDb - nocoDb
Config choices
Version 3

Block 6 - Convert month name to number

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

Block 7 - Edit Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Monthly Trigger1

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 13 - Monthly Trigger2

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 14 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup
Complexity intermediate
Nodes 14
Categories Document Extraction
Author Nima Salimi
Published 08 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/9368/9368.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

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

  4. 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. 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.

Frequently asked questions

What does Automate monthly CrUX report transfer from BigQuery to NocoDB with data cleanup do?

This n8n workflow automatically retrieves the monthly CrUX (Chrome User Experience) Report from Google BigQuery and updates the data in NocoDB . It removes the previous month’s data before insertin...

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