What breaks if I don't upgrade n8n past 2.34.6?

Workflows using the Google Ads node are calling Google's v21 API, which is sunset. Once Google stops serving it those workflows stop returning data. In an automation this usually surfaces as an empty result or a failed step in an error branch rather than anything anyone notices immediately.

Should I install 2.34.6 or 2.35.x?

2.34.6 is the stable release and is the one that carries the Google Ads migration. A 2.35.x pre-release shipped the same day; pre-releases are not where you want a production automation instance.

Where are n8n's current release notes?

The GitHub releases page. The changelog on docs.n8n.io is archived and stops at July 1, 2026, so it is not a reliable source for anything recent — a trap if you check the docs site first, as most people do.

Why was the Microsoft Teams OAuth scope changed?

The Group.ReadWrite.All scope was restored in 2.34.6 after previously being removed. If your Teams credential was authorised during that window, it may need re-consent before group write operations work.

n8n's Google Ads Node Moves Off a Dead API

Gloved hands sliding a clean new module into a live server rack, the old unit on the bench — AutomationAugust 14, 2026·2 min read·By the Automation Squad Research
n8n's Google Ads Node Moves Off a Dead API
Sunset APIs don't fail loudly. They fail into an error branch nobody is watching.

By Robert MacKelfresh

Founder, Automation Squad · August 14, 2026

The short answer

n8n 2.34.6, released August 14, 2026, migrates the Google Ads node from Google's sunset v21 API to v25. If you self-host n8n and any workflow uses the Google Ads node, upgrading to 2.34.6 or later is what keeps it working. The release also restores the Group.ReadWrite.All OAuth2 scope on the Microsoft Teams node.

Upgrade checklist

What's in 2.34.6, who needs it, and how to confirm it worked

Three fixes, one of which is a genuine break-if-you-ignore-it. Fifteen minutes including the verification run.

Check whether any workflow uses the Google Ads node
Search your instance rather than trusting memory. Reporting workflows built months ago are exactly the ones nobody remembers, and exactly the ones that break quietly.
Note your current n8n version before you touch anything
You want the number to roll back to if something unrelated regresses. 2.34.6 is a stable release; the 2.35.x line shipping the same day is pre-release and is not what you want here.
Upgrade to 2.34.6 or later
Standard upgrade path for however you self-host — Docker image tag, npm, or your managed deployment's update flow.
Re-authenticate the Microsoft Teams credential if you use it
The Group.ReadWrite.All scope was restored in this release. A credential authorised while the scope was missing may need re-consent before group writes work again.
Execute each Google Ads workflow manually, once
Do not wait for the schedule. Run it by hand and confirm real data comes back — not just that the node goes green. A node can succeed and return an empty set.
Check your error branches while you are in there
The core fix in this release allows the `details` field in continueErrorOutput mode. If you route failures somewhere, you now get more information in them, which is worth a look at whatever consumes that output.

Fix	PR	Who it affects
Google Ads node: v21 (sunset) → v25 API	#36260	Anyone using the Google Ads node
Microsoft Teams: Group.ReadWrite.All scope restored	#36187	Teams workflows that write to groups
Core: allow `details` field in continueErrorOutput mode	#36229	Workflows using error outputs

Take it with you

n8n 2.34.6 UPGRADE CHECKLIST — released Aug 14, 2026
Source: https://automationsquad.com/news/n8n-google-ads-node-v25/

WHAT'S IN IT
  #36260  Google Ads node: sunset v21 API -> v25        <- the important one
  #36187  Microsoft Teams: Group.ReadWrite.All scope restored
  #36229  Core: allow `details` field in continueErrorOutput mode

CHECKLIST
[ ] Search my instance for workflows using the Google Ads node
    (don't trust memory — old reporting workflows are the risk)
[ ] Write down my current n8n version for rollback
[ ] Upgrade to 2.34.6 STABLE
    (2.35.x shipped the same day but is PRE-RELEASE — not this)
[ ] Re-authenticate the Microsoft Teams credential if I use it
[ ] Run each Google Ads workflow MANUALLY once
[ ] Confirm real data came back — a green node can still return nothing
[ ] Check whatever consumes my error branches (details field is richer now)

NOTE ON DOCS
docs.n8n.io/changelog/release-notes-2.x is ARCHIVED and stops at 1 Jul 2026.
Use the GitHub releases page for anything recent.

n8n published stable release 2.34.6 on August 14, 2026. It contains three bug fixes, one of which is a required migration rather than an improvement.

The facts: the Google Ads node moves from Google's sunset v21 API to v25 (#36260). The Microsoft Teams node has its Group.ReadWrite.All OAuth2 scope restored (#36187). And in core, the `details` field is now allowed in continueErrorOutput mode (#36229), so error branches carry more information than they did. A 2.35.x pre-release shipped the same day and is not the release to put in front of production. One practical note for anyone checking sources: the changelog on docs.n8n.io is archived and stops at July 1, 2026, so the GitHub releases page is the only current record.

Automation Squad's take: this is the least glamorous category of AI news and the one most likely to cost you something. A sunset API does not throw an alert into your inbox — it degrades, returns nothing, or fails into a branch that writes to a log nobody reads. The workflows most exposed are always the same ones: built months ago, running on a schedule, feeding a report someone glances at. By the time the gap is noticed, the question is not "what broke" but "how long has this been empty". Fifteen minutes today is cheap insurance against that conversation.

Run this now: search your n8n instance for the Google Ads node rather than trying to remember where you used it. Note your current version, upgrade to 2.34.6 stable, and then execute each affected workflow manually — do not wait for its schedule. Check that real data comes back, not merely that the node turns green, because an empty result set is a success as far as the node is concerned. If you use the Microsoft Teams node for group writes, re-authenticate that credential while you are in there.

Questions people are asking

What breaks if I don't upgrade n8n past 2.34.6?: Workflows using the Google Ads node are calling Google's v21 API, which is sunset. Once Google stops serving it those workflows stop returning data. In an automation this usually surfaces as an empty result or a failed step in an error branch rather than anything anyone notices immediately.
Should I install 2.34.6 or 2.35.x?: 2.34.6 is the stable release and is the one that carries the Google Ads migration. A 2.35.x pre-release shipped the same day; pre-releases are not where you want a production automation instance.
Where are n8n's current release notes?: The GitHub releases page. The changelog on docs.n8n.io is archived and stops at July 1, 2026, so it is not a reliable source for anything recent — a trap if you check the docs site first, as most people do.
Why was the Microsoft Teams OAuth scope changed?: The Group.ReadWrite.All scope was restored in 2.34.6 after previously being removed. If your Teams credential was authorised during that window, it may need re-consent before group write operations work.