Google Ads to Google Sheets, campaign lookups simplified
Campaign questions come in nonstop. “What’s the ID for the Brand Search campaign?” “Which campaign is paused?” “Can you pull the full list again?” And you end up bouncing between Google Ads tabs, exporting CSVs, then second-guessing if you grabbed the right thing.
This Google Ads lookups automation hits PPC managers first, but marketing ops and client-facing agency leads feel it too. The goal is simple: one place to search campaign details fast, without copy-paste mistakes.
You’ll set up an n8n workflow that can fetch a full campaign list or pull one campaign on demand, then send the results into Google Sheets (and optionally Excel/Drive). It’s the difference between “give me a minute” and “here you go.”
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Ads to Google Sheets, campaign lookups simplified
flowchart LR
subgraph sg0["Google Ads Tool MCP Server Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Google Ads Tool MCP Server", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Get many campaigns", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Get a campaign", pos: "b", h: 48 }
n2 -.-> n0
n1 -.-> n0
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
Why This Matters: Campaign Lookups Become a Daily Time Leak
Google Ads is great at running campaigns. It’s not great at answering quick, repeated questions across a team. If you’ve ever had someone ask for a campaign ID while you’re mid-optimization, you know the drill: open the account, find the right view, filter, click into the campaign, copy the resource name or ID, then hope you didn’t grab the wrong “Brand – Exact” from three similar ones. Do that a few times a day and it quietly eats a chunk of your week. Worse, the wrong ID in a report or a workflow can break downstream tracking and turn a small lookup into a mini incident.
The friction compounds. It’s not one big task, it’s dozens of tiny interruptions that pull you out of real work.
- People keep asking the same campaign questions because there’s no shared source of truth they can search.
- Manual copy-paste invites errors, especially with similar campaign names across regions or product lines.
- Quick exports become “temporary spreadsheets” that go stale fast, so the team stops trusting them.
- When an ID is wrong in a dashboard or a script, you lose time diagnosing instead of optimizing.
What You’ll Build: An AI-Ready Google Ads Campaign Lookup Feed
This workflow turns campaign lookups into an on-demand service you can reuse anywhere. It starts with an MCP Server Trigger in n8n, which exposes a clean endpoint your tools (and AI agents) can call when they need Google Ads campaign data. From there, you choose the path: either retrieve a list of campaigns for the account, or fetch one specific campaign when you already have an identifier. The workflow uses the native n8n Google Ads Tool operations, so you’re not stitching together brittle HTTP calls or reinventing error handling. Once you get the response, you can push the key fields into Google Sheets for fast searching and consistent reporting answers. Optionally, you can mirror that into Excel or store files in Google Drive if that’s how your team works.
The workflow begins when your system (or an AI agent) hits the MCP endpoint. n8n then calls the Google Ads Tool operation you need, returns structured campaign details, and logs the result so you have a reliable audit trail. Finally, the data lands in a spreadsheet your team can actually use.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say your team answers campaign questions 5 times a day. Manually, a “quick lookup” is rarely quick: maybe 10 minutes of opening Google Ads, searching, confirming, then pasting into Slack or a report, which is close to an hour daily. With this workflow, you trigger a lookup and write the result to Google Sheets in a couple minutes, then everyone can search the sheet instantly after that. Over a week, that’s about 3 hours back, plus fewer interruptions.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Ads account access with campaign read permissions.
- Google Sheets to store a searchable campaign lookup table.
- Google Ads credentials (set up in n8n’s Google Ads Tool).
Skill level: Intermediate. You won’t code, but you will connect credentials and map a few fields into a sheet.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
An MCP endpoint receives the request. The MCP Server Trigger acts like a “front door” for campaign lookups, so an AI agent or another workflow can ask for a campaign list or a single campaign record.
The workflow decides what you meant. Based on the input, n8n routes the request to the right Google Ads Tool operation: either retrieve many campaigns (for refreshes and audits) or fetch one campaign (for fast answers).
Google Ads returns the canonical data. The Google Ads Tool node pulls the real campaign details straight from the account, which means you’re not relying on last week’s export or someone’s memory.
The result gets stored where people can use it. Map the response into Google Sheets so anyone can search campaign IDs, names, and statuses without opening Ads. If you want, you can also send a copy into Excel 365 or file outputs into Google Drive for internal documentation.
You can easily modify what fields you write to Google Sheets based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the MCP Trigger
Set up the MCP endpoint that initiates the workflow when the MCP Ads tool is called.
- Add the MCP Ads Trigger node as the workflow trigger.
- Set the Path to
google-ads-tool-mcp. - Leave Flowpast Branding as a visual note node (no configuration required for execution).
Step 2: Connect Google Ads
Both Google Ads tool nodes must authenticate with Google Ads to query campaigns.
- Open Retrieve Campaign List and add credentials.
- Credential Required: Connect your googleAdsOAuth2Api credentials.
- Open Fetch Single Campaign and add credentials.
- Credential Required: Connect your googleAdsOAuth2Api credentials.
Step 3: Set Up Retrieve Campaign List
Configure the Google Ads tool to fetch a list of campaigns using MCP-provided fields.
- In Retrieve Campaign List, set Campaigs Notice to
{{ $fromAI('Campaigs_Notice', ``, 'string') }}. - Set Client Customer Id to
{{ $fromAI('Client_Customer_Id', ``, 'string') }}. - Set Manager Customer Id to
{{ $fromAI('Manager_Customer_Id', ``, 'string') }}.
Step 4: Configure Fetch Single Campaign
Set the campaign lookup tool to fetch a specific campaign by ID.
- Open Fetch Single Campaign and set Operation to
get. - Set Campaign Id to
{{ $fromAI('Campaign_Id', ``, 'string') }}. - Set Campaigs Notice to
{{ $fromAI('Campaigs_Notice', ``, 'string') }}. - Set Client Customer Id to
{{ $fromAI('Client_Customer_Id', ``, 'string') }}. - Set Manager Customer Id to
{{ $fromAI('Manager_Customer_Id', ``, 'string') }}.
Step 5: Test and Activate Your Workflow
Validate the MCP trigger and Google Ads tools before activating the workflow.
- Click Execute Workflow and send a test MCP request to the MCP Ads Trigger path.
- Confirm Retrieve Campaign List returns a campaign list and Fetch Single Campaign returns the specified campaign.
- If successful, toggle the workflow Active to enable it for production use.
Troubleshooting Tips
- Google Ads credentials can expire or need specific permissions. If things break, check the Google Ads credential in n8n (and the Google account’s access level in Ads) first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your Google Ads access is ready.
No. You’ll mostly connect credentials and map a few fields into Google Sheets.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google Ads API access costs (usually $0, but subject to Google’s policies and quotas).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you probably should. You can keep the same MCP Ads Trigger and swap what happens after it, like writing different fields to Google Sheets, sending the response to Slack, or storing a refresh export in Google Drive. Many teams also add a simple Switch so “get many campaigns” runs nightly, while “get a campaign” runs on demand during the day.
Usually it’s permissions or expired credentials. Re-check the Google Ads credential in n8n, then confirm the Google account has access to the right Ads account (or manager account). If it fails only sometimes, it can be quota limits or too many requests too quickly, so spacing requests out helps. Also confirm you’re passing a valid campaign resource identifier when using the “Fetch Single Campaign” operation.
A typical setup can handle dozens of lookups per day comfortably, and bulk “get many campaigns” refreshes as needed.
For this use case, n8n is often the better fit because it can expose an MCP-style endpoint, handle more complex branching without inflating costs, and supports self-hosting when you want unlimited executions. Zapier and Make can still work if you only need a simple “export campaigns to a sheet” job. The big difference is flexibility: with n8n you can turn the same workflow into a reusable internal service, not just a one-off automation. If you’re deciding between tools, think about who will call this workflow (humans, dashboards, AI agents, other automations) and how often. Talk to an automation expert if you’re not sure which fits.
Once this is in place, campaign lookups stop being a mini task that derails your day. Your spreadsheet stays consistent, your answers stay fast, and your team stops guessing.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
