n8n Google Ads Automation: From Daily Pull to AI Action

Every Monday, somewhere, a marketing manager opens Google Ads, copies numbers into a spreadsheet, opens Facebook Ads, copies more numbers, and only then starts thinking. One manager on r/PPC put it plainly: "I literally spend the first half of every Monday just copy-pasting numbers before I can start actual work." The copying isn't the job. It's the tax you pay before the job.

n8n Google Ads automation removes that tax. n8n is an open-source workflow tool, and its Google Ads node plus an OpenAI node can pull yesterday's metrics, decide which campaigns are bleeding, and email you the fix before you've finished your coffee. Not a dashboard you still have to read. An answer.

Most guides stop at the pull. This one goes to the action.

What you can automate

• Pulling daily campaign metrics from Google Ads on a schedule, no manual export
• Merging Google Ads with Facebook Ads so cross-channel spend sits in one view
• Flagging underperforming campaigns automatically instead of eyeballing a sheet
• Generating a specific recommendation per campaign with AI ("pause", "raise bid", "shift budget")
• Emailing an actionable daily report so you act before wasting another day of spend
• Logging history to Google Sheets for week-over-week trend tracking

The official Google Ads integration page (n8n.io) confirms the node exists and connects to 1,000+ services, but it's a hub page with no campaign-analysis or cross-channel examples. The popular AI marketing report template (n8n.io) does pull Google Ads, Analytics, and Meta Ads together and emails a year-over-year table, but it stops at summarization. By its own description it offers no campaign flagging and no optimization recommendations. That last mile is the gap.

The Google Ads optimization pipeline

Schedule Trigger → Fetch Google Ads + Facebook Ads → Normalize
   → OpenAI (flag underperformers + recommend) → Email report
   → Log to Sheets

The shape looks like a reporting workflow. The OpenAI step is what makes it an optimization workflow.

1. Fetch the metrics

A scheduleTrigger v1.2 node fires daily, before work hours. The Google Ads node pulls campaign-level metrics (spend, clicks, conversions, CPA, ROAS) for the prior day. For Facebook, a parallel branch hits the Marketing API. Both use OAuth2 credentials configured once in n8n. Anything the Google Ads node doesn't expose, an httpRequest v4.2 node can query against the Google Ads API directly, so you're never blocked waiting on a connector feature.

2. Normalize into one shape

Google Ads and Facebook report different field names for the same idea. A n8n-nodes-base.code v2 node with jsCode maps both into a common schema: campaign, channel, spend, conversions, cpa, roas. Now a single downstream node can reason across both platforms without caring where a row came from. This normalization step is what makes the AI prompt clean instead of conditional.

3. Let AI flag and recommend

Feed the normalized array to the @n8n/n8n-nodes-langchain.openAi v2.1 node. Prompt it to identify underperformers against your targets and return a recommendation per flagged campaign. The node returns output at $json.output[0].content[0].text — the older n8n-nodes-base.openAi path silently breaks if you lift it from a 2023 tutorial, so check the version. The model writes "CPA on Brand-Search is 3.1x target, pause and reallocate," not just a red cell. That's the difference the summarize-only templates don't deliver.

4. Email the report, log the history

A Gmail node sends the daily report: the flagged campaigns up top, the AI recommendations next, the full table below. A Google Sheets node appends the day's metrics so you build a trend record over weeks. The log is dull and you'll be glad it exists the first time someone asks whether last month's CPA spike was a blip or a pattern.

Implementation patterns

Pattern 1: Cross-channel single report. Pull both platforms, normalize, report once. A media buyer running Google and Facebook shouldn't open two tabs to answer "where's the waste." One workflow, one email, both channels. The AI marketing report template gets the multi-source pull right; what it lacks is the diagnostic layer on top.

Google Ads + Facebook Ads → Code (normalize) → OpenAI (analyze) → Gmail

Pattern 2: Anomaly alert, not full report. A leaner variant runs more often on a narrow metric set and only fires when spend or CPA crosses a threshold. No daily email when nothing's wrong; a Telegram ping the moment something is. Good for accounts where a runaway campaign can burn the budget by lunch.

Schedule → Fetch metrics → Filter (CPA > threshold) → Telegram alert

Pattern 3: Recommendation log for trend review. Append every AI recommendation to Sheets alongside the metrics. Over a month you can see whether the model keeps flagging the same campaign, which usually means a structural problem the daily fix never addresses. Data that compounds.

n8n nodes you'll use most

Getting started

1. Run n8n (self-hosted or Cloud) and create a new workflow.
2. Set up the Google Ads OAuth2 credential and test a small report query through the node.
3. Add a Facebook Ads branch (node or httpRequest) if you run both channels.
4. Add a Code node that normalizes both payloads into one campaign schema.
5. Wire the OpenAI node with a prompt that flags underperformers and recommends an action per campaign.
6. Add a Gmail node for the report and a Google Sheets append for the history.
7. Drop a scheduleTrigger at the front, set it to fire daily, and run a full test.

The exact normalization shape and the AI recommendation prompt are documented on the Ad Performance Optimizer page.

The same pull-normalize-analyze backbone underpins broader ad performance automation and the Facebook-specific build in Meta Ads automation. Swap the data source and the analysis layer stays put. For teams whose reporting also covers organic search, the Market Trend Analyzer shows the same schedule-fetch-AI pattern applied to demand signals.