Skip to main content

Fetch full Google Ads account audit data as merged JSON

Workflow preview

Workflow preview
100%
Fetch full Google Ads account audit data as merged JSON preview
Open on n8n.io

1. Workflow Overview

Quick overview Runs manually to pull read only Google Ads reporting for one account: campaign, ad group, keyword, ad and search term performance over a chosen date range, plus a current state snaps...

Best for

  • Market Research automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.wait

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Fetch full Google Ads account audit data as merged JSON
Workflow name
Fetch full Google Ads account audit data as merged JSON

Quick overview

Runs manually to pull read-only Google Ads reporting for one account: campaign, ad group, keyword, ad and search-term performance over a chosen date range, plus a current-state snapshot of negative keywords, ad group targeting and campaign assets. Returns everything as one merged JSON object.

How it works

  1. Starts when you manually execute the workflow.
  2. Loads your Google Ads customer ID, developer token, API version and reporting date range from a Set node.
  3. Queries the Google Ads API (searchStream) for campaign performance, settings and bidding strategy over the date range.
  4. Queries ad groups, keywords (including Quality Score fields) and the top 300 search terms by spend for the same date range.
  5. Queries ads (including RSA headlines/descriptions and approval status) over the date range.
  6. Pulls current-state data not bound by the date range: campaign-level negative keywords, ad group targeting criteria, and campaign assets (call, callout, sitelink).
  7. Merges all eight datasets into a single JSON object, keyed by section.

Setup

  1. Create a Google Ads OAuth2 credential in n8n with access to the target customer account and attach it to the HTTP Request nodes.
  2. Get a Google Ads developer token from your Google Ads Manager (MCC) account → Tools → API Center, and set it in the .env node.
  3. Set the customer ID (sub-account, no dashes) and api_version (v23 tested).
  4. Set DATE_FROM and DATE_TO using fixed dates or the provided expressions to control the reporting period. Note: the negative keyword, audience and asset queries return current state and ignore this range.

Requirements

  • Google Ads account with API access enabled
  • Google Ads OAuth2 credential configured in n8n
  • Google Ads developer token

Customization

  • Edit the GAQL queries to add/remove fields or change filters (e.g. include REMOVED entities).
  • Change the Search Terms ORDER BY/LIMIT (currently top 300 by cost).
  • Add segments.date to the negative keyword, audience or asset queries to date-bound them too.

Additional info

Read-only, every node is a SELECT query; the workflow makes no changes to the account. The "Audience Segments" node returns all ad group targeting criteria, not only audience segments.

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 - overview

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

Block 2 - sec_setup

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

Block 3 - sec_pull

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

Block 4 - sec_merge

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

Block 5 - When clicking ‘Execute workflow’

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

Block 6 - Merge All Outputs

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

Block 7 - 1. Campaigns

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 8 - 2. Ad Groups

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 9 - 3. Keywords

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 10 - 4. Search Terms

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 11 - 5. Ads

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 12 - 6. Negative Keywords

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 13 - 7. Audience Segments

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 14 - 8. Extensions & Assets

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 15 - .env

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

Block 16 - Wait

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 17 - Sticky Note

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

Block 18 - Sticky Note1

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

3. Summary Table

Workflow Fetch full Google Ads account audit data as merged JSON
Complexity advanced
Nodes 18
Categories Market Research
Author Sobek
Published 12 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16310/16310.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 Fetch full Google Ads account audit data as merged JSON do?

Quick overview Runs manually to pull read only Google Ads reporting for one account: campaign, ad group, keyword, ad and search term performance over a chosen date range, plus a current state snaps...

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.