n8n tagged [email protected] on 19 August 2026. This is a stable patch, not a prerelease. The change that hits extract jobs first is the Google Ads node: campaign reads against API v25 now select the renamed video views metric instead of a field Google dropped in v22.
The full release notes and downloads are on the GitHub release page. The compare range against [email protected] lists four commits: two bug fixes and two features.
Google Ads campaign queries on API v25 ¶
Campaign operations campaign:get and campaign:getAll build a GAQL SELECT. Google Ads Query Language requires every selected field to resolve. If one name is unknown, the entire googleAds:search request fails rather than omitting that column.
The node had already moved to API v25. The field list still selected metrics.video_views. That field was removed in v22 and renamed to metrics.video_trueview_views. Live campaign reads were failing outright.
#36414 (a8b2716) updates the selected field and the JSON key on the item. The old key was videoViews. The new key is videoTrueviewViews. v25 does not return the old name under any alias.
The other 19 selected fields on campaign, campaign budget, and remaining metrics were checked against the v22 through v25 protos. Only the video views field was stale. Workflows that never read videoViews get working campaign rows again. Workflows that map that key need a remap before the next scheduled run.
Discover endpoint returns request schemas ¶
Public API clients that call /api/v1/discover?include=schemas were getting route entries with no requestSchema for decorator controllers. buildDecoratorEndpoints() never set the field. Routes backed by express-openapi-validator still exposed a schema from the committed spec.
#36497 (fa781db) converts the @Body DTO already used to validate the request into JSON Schema. The conversion uses the same generator that writes the committed OpenAPI files, so /discover and the published spec cannot drift on body shape. As more public routes move onto decorator controllers, that field would have stayed empty without this fill.
Four routes declare a body DTO today and were missing the schema:
POST /roles(CreateRoleDto)PUT /roles/{slug}(UpdateRolePublicDto)POST /role-mapping-rules(CreateRoleMappingRuleDto)PUT /workflows/{workflowId}/tags(TagIdsPublicDto)
The last path is how the public API retags a workflow. Contract tests and generated clients that treated requestSchema as always present will start seeing it for these decorator routes. The tags payload is an array of objects with a required id string and additionalProperties set to false.
Managed OAuth scopes and setup telemetry ¶
Scope fields on managed OAuth credentials stay hidden by default when a credential type is overwritten. That hide is intentional. Some self hosted installs still need to edit scopes on generic types such as googleOAuth2Api.
#36397 (d8e3ee6) adds N8N_MANAGED_OAUTH_SHOW_SCOPES. Set it to the credential type name to show the scope field again, for example N8N_MANAGED_OAUTH_SHOW_SCOPES=googleOAuth2Api. The flag is opt in. If you do not set it, credentials that use an overwrite keep scopes hidden.
The second feature is not pipeline code. #36464 (7f7f0a1) adds AI Assistant setup funnel telemetry on self hosted instances: setup page views, model and sandbox saves, connection failures, and a one time setup completed event. Failure text strips URL query strings and is capped at 512 characters. The events are not emitted on cloud or proxy deployments. Operators who already allow n8n telemetry should expect new event names on that channel.
Upgrade notes ¶
The release notes do not list a migration guide. The Google Ads key change is still a contract break for any workflow that reads videoViews from campaign:get or campaign:getAll. Point those mappings at videoTrueviewViews after the upgrade, and pin fixture data again if it stored the old key.
N8N_MANAGED_OAUTH_SHOW_SCOPES does not change default behavior. Leave it unset unless you need to customize scopes on a managed credential type.
The discover change is additive. Existing routes gain a requestSchema field they previously omitted. Clients that ignore unknown fields are unaffected.