Version v17 is deprecated. Requests to this version will be blocked.

Feature Requests
1

Aquí está el ticket completo para soporte de n8n:

The idea is:

Update the Google Ads node to use Google Ads API v18 instead of the deprecated v17. The current node is using v17 which has been deprecated by Google and is now blocking all requests.

My use case:

I need to connect to Google Ads API to retrieve campaign data, manage ads, and automate marketing workflows. Currently, I cannot use the Google Ads node at all because it’s trying to use API v17 which Google has completely blocked. This is preventing me from:

  • Retrieving campaign performance metrics
  • Managing ad campaigns programmatically
  • Automating reporting workflows
  • Integrating Google Ads data with other tools in my workflows

I attempted to use the HTTP Request node as a workaround to directly call Google Ads API v18, but encountered authentication issues (403 Permission Denied errors) even with proper OAuth2 setup and correct headers. This makes the native Google Ads node even more critical since it handles authentication complexity internally.

I think it would be beneficial to add this because:

  1. Critical Breaking Issue: The Google Ads node is completely non-functional for all users due to the deprecated API version
  2. No Workaround in Cloud Version: Users on n8n cloud cannot update nodes themselves and are stuck without Google Ads functionality
  3. Business Impact: Many businesses rely on Google Ads automation for their marketing operations
  4. Google’s Timeline: Google has already deprecated v17 and is blocking requests, making this an urgent issue
  5. Complex Authentication: The HTTP Request workaround requires complex OAuth2 configuration that many users struggle with, making the native node essential
  6. Production Workflows Broken: Existing workflows that were working are now completely broken with no immediate solution

Any resources to support this?

Error Details from Google Ads Node:

json

{
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT",
    "details": [{
      "@type": "type.googleapis.com/google.ads.googleads.v17.errors.GoogleAdsFailure",
      "errors": [{
        "errorCode": {
          "requestError": "UNSUPPORTED_VERSION"
        },
        "message": "Version v17 is deprecated. Requests to this version will be blocked."
      }]
    }]
  }
}

Attempted Workaround Issues: When trying to use HTTP Request node with Google Ads API v18, I encountered:

  • 403 Permission Denied errors despite correct OAuth2 configuration
  • Complex header requirements (developer-token, login-customer-id)
  • Authentication flow issues that the native node should handle automatically

Environment:

  • Node type: n8n-nodes-base.googleAds
  • Node version: 1 (Latest)
  • n8n version: 1.94.1 (Self Hosted)
  • Date: December 6, 2025
  • Manager Customer ID: 168-690-9958
  • Client Customer ID: 551-195-9787

Are you willing to work on this?

I would be willing to test the updated node once available. This is a critical issue affecting production workflows. I can provide test credentials and real-world use cases to ensure the updated node works correctly.

Urgent Request: Please prioritize this update as it’s a complete breaking change affecting all Google Ads users on n8n. Our marketing automation workflows are currently non-functional, impacting business operations.

2

Same problem