How can I resolve the 403 error when connecting the Google Ads node in n8n?

Below is some guidance based on the n8n documentation for the Google Ads node:

Troubleshooting the 403 Error

A 403 error (“Request failed with status code 403”) usually indicates a permissions issue or that the credentials provided are not authorized to access the requested resource. Here are a few points to review:

1. Check Your Credentials
   Make sure you’ve correctly set up your Google Ads credentials. The documentation recommends reviewing the guidance on Google Ads credentials. Confirm that:

   • Your developer API token is active.
   • The token has the correct permissions to access your Google Ads data.
   • There are no restrictions on your credentials that might block access (e.g. using a test account or a token that only has limited access).

2. Developer Access Token (Test Account)
   If you’re using a “test account” developer token:

   • Test tokens often have limitations or might not be allowed to access production endpoints.
   • Verify whether a test token is supported for the operation you’re attempting. In some cases, you might need to apply for full access or use a production token.

3. Account Type (Google Workspace / MCC)

   • A Google Workspace account shouldn’t directly cause a Google Ads integration error.
   • However, if you’re using an MCC (manager) account that is linked to a test environment, check with Google Ads’ developer documentation to ensure that it’s allowed to issue API calls under the current configuration.

Next Steps

• Review the API Permissions: Double-check the access levels and scopes granted to your developer token.
• Confirm with Google Ads API Requirements: If your token is from an MCC test account, it may be subject to additional limitations. The Google Ads developer documentation can provide details on whether your token is allowed to retrieve data in the way you’re requesting.
• Use Production Credentials if Needed: If possible, consider switching to full production credentials to rule out restrictions imposed on test tokens.

If after checking these points the issue persists, it may be worthwhile to reach out to both Google support (to verify that the access token is valid for the desired operations) and the n8n community forum for further troubleshooting insights.

Feel free to share additional details (if you’re comfortable with that) in the n8n community, and make sure to avoid sharing sensitive credential information publicly.