Error 403: Google OAuth Access Denied - Request Test User Access

Questions
2

Hey @GEOTUNELES Welcome to the n8n community!

That 403 access_denied message is coming directly from Google it means the OAuth app you’re trying to use has not completed Google’s verification process, so Google blocks anyone who isn’t listed as an approved tester from signing in. This is a common issue when the OAuth consent screen is still in Testing mode.

What you should check in your Google Cloud Console

  1. OAuth Consent Screen setup

    • Go to APIs & Services > OAuth consent screen in the Google Cloud Console.

    • Ensure the consent screen is fully filled out (app name, email, scopes, etc.).

    • If it’s still in Testing mode, only test users can authenticate.

  2. Add your Google account as a test user

    • In the Audience or Test users section of the OAuth consent screen, add your email (geotunelessas@gmail.com) under Test users.

    • Save and retry the OAuth flow in n8n.cloud this often resolves the access_denied error without full verification.

  3. Plublish the OAuth app , you can consider this too

    • If you want anyone (not just test users) to connect to Google APIs, you can publish the OAuth app from Testing to Production in the OAuth consent screen. That triggers Google’s verification process for sensitive scopes (Google Drive, Sheets, etc.).

    • Verification can take several days and might require a privacy policy, app description, and demonstration video.

  4. Check enabled APIs

    • Make sure the specific Google APIs you’re trying to use (Drive, Sheets, Gmail, etc.) are enabled under APIs & Services > Library for your project.

  5. Authorized redirect URI

    • Confirm that the redirect URI from n8n.cloud is exactly listed under your OAuth credentials Authorized redirect URIs

By addressing these your n8n cloud instance should be able to get connected with your google service, hope it helps