I have a selfhosted n8n instance, that I’ve setup recently, and it was integrated with a google project.
While I was using this integration over a Oauth 2.0 web application still on testing, I had to relogin once a week from n8n side, but when I had the workflows using that google application a lot more (using gmail, google sheets and google drive), I decided to put that on production from google web application.
After doing that I noticed right away that within one hour or a few hours that the integration was breaking regarding steps related just with google drive, and the only way to fix this was to sign-in again on n8n over that credential related with google drive only and not the rest.
These are the login popups that I get from google when I login from n8n (not sure if could be useful):
Hi @marafado88 I had the same issue, it got resolved when i created a new google console project and added that app integration as a fresh instance and then published it, let me know if this works for you.
This is a classic Google OAuth2 refresh token issue. When you moved from “Testing” to “Production” in Google Cloud Console, the OAuth consent screen publishing status might not have fully propagated, or your refresh tokens may have been invalidated during the transition.
**Most common causes & fixes:**
1. **Check your publishing status** in Google Cloud Console → APIs & Services → OAuth consent screen:
Make sure it says “In production” (not “Testing”)
If you just changed it, wait 10-15 minutes for propagation
2. **Force a complete re-authentication:**
In n8n, delete ALL existing Google Drive credentials
In your Google account (myaccount.google.com → Security → Third-party apps), revoke access for your n8n app
Go back to n8n and create a fresh credential - this will generate a new refresh token
3. **Verify your OAuth scopes** haven’t changed between Testing and Production. Google can invalidate tokens if the scopes differ.
4. **Check if you need to submit for verification:** If you’re using sensitive scopes (like Gmail or certain Drive scopes) and your app shows “Needs verification,” tokens will expire quickly until verified.
The fact that only Google Drive is affected (not Gmail/Sheets) suggests the Drive-specific scope may need re-authorization. Try the complete re-auth in step 2 first — that usually resolves it.
Let me know if you’re still seeing issues after this!
Have created a new project now, and in meantime I have been testing another workflow and have noticed that seems this situation is only happening with this step:
@marafado88 please consider using inbuilt Drive node it is far easier to setup and easy to debug in all cases , i would not say it is related to particularly that issue but sometimes things just does not work with console so creating a new project make things work again , not related to n8n but it is something off from Google console. Please again use Drive node for interacting with Google drive services:
After switching that with the Upload File from Google Drive, the builtin one, it worked. I was using that because it came with a template that I’ve used, but since it was the first step using google drive, I thought that there was something more related. So after switching those that I had before with Google Drive builtin one, it worked with the other credentials that I was using already! Thank you!
