HTTP Request Node Cannot Use Google Drive OAuth Credentials on n8n.cloud (Account Unavailable)

Questions
1

"Hello n8n Community and Support,

I am consistently unable to get the HTTP Request node to authenticate with my Google Drive OAuth credentials on my n8n.cloud instance. I have followed extensive troubleshooting steps, but the issue persists.

Problem: When configuring an HTTP Request node to call the Google Drive API (e.g., https://www.googleapis.com/drive/v3/files/...), I cannot select any of my working Google Drive OAuth credentials.

  • In the HTTP Request node’s ‘Authentication’ dropdown, my only relevant options are ‘Predefined’ or ‘Generic’.

  • If I select ‘Predefined’, and then ‘GoogleDrive OAuth’, the subsequent ‘Credential’ dropdown shows ‘Google Drive Account unavailable’ and prompts me to create a new credential (even though working ones exist).

  • The ‘Generic’ authentication option does not allow linking to existing OAuth2 credentials.
    I am working on the latest version.
    Relevant Credentials I Have Created (and which are connected/green):

  • Google Drive (Manual OAuth - Cloud) (created using the generic OAuth2 API type, with https://www.googleapis.com/auth/drive scope).

  • Google Drive (HTTP Node - Cloud) (created using the specific Google Drive OAuth type, with https://www.googleapis.com/auth/drive scope).

  • (Also have working Google Sheets OAuth 2 API and Google Docs OAuth 2 API credentials, both using the generic OAuth2 API type, which were also difficult to set up initially).

Steps I’ve Already Taken (Extensive Troubleshooting):

  1. Confirmed Google Drive API is enabled in Google Cloud Console.
  2. Confirmed all necessary scopes (https://www.googleapis.com/auth/drive, userinfo.email, userinfo.profile) are added to OAuth Consent Screen in Google Cloud Console and publishing status is correct (Testing with test users/In Production).
  3. Verified Client ID, Client Secret, and Redirect URI (https://oauth.n8n.cloud/oauth2/callback) are identical in Google Cloud Console and n8n credentials.
  4. Performed hard refreshes (Ctrl+Shift+R), cleared all browser cache/site data (Local Storage, Session Storage, IndexedDB, Cookies specifically for adastra-ai.app.n8n.cloud), and restarted Firefox and laptop multiple times.
  5. Deleted and recreated credentials from scratch multiple times.
  6. Updated my n8n.cloud instance to the latest stable version available in the trial.

Expected Behavior: I expect to be able to select one of my existing, working Google Drive OAuth credentials within the HTTP Request node’s authentication settings.

Thank you for your help.

2

Hi, do you have only one client set up in Google Cloud, or do you have more than one?

3

Hi Grot, after some struggle I was able to resolve the issue. Thanks a lot I appreciate you reaching out!

4

Hey Gretel, How did you fix it? I am having a similar problem. --Except, my credentials are not showing green. I will post anew.

5

I actually don’t remember now, I went through so much since then… but for me, trying to work with Google credentials and nodes, it was all about learning first and foremost how to create the "OAuth 2.0 Client ID"s on the Google Auth platform. Each of them needs to be set correctly. All menus Branding, Audience, Clients, Data Access, need to be explored and set correctly, otherwise once you get to n8n credentials, they will not connect. And, the scopes need to be accurate for each instance. I recommend starting there.