Hello community!
I’ve been an n8n lover for a few years and there’s one thing that bothers me about Google.
After connecting via oAuth, after a few days, the flow presents an error and forces me to reconnect to Google (to use Google sheets for example).
Does everyone have this problem?
Is there a way to fix this so that the flow doesn’t give an error due to a lack of connection?
n8n Self-hosted
It looks like your topic is missing some important information. Could you provide the following if applicable.
I’m facing the same problem with google storage oauth credentials. I saw this clarification in the docs but I’m using an internal consent screen. This is the second time it happened (I’m new in n8n) and first time I though I might have done something wrong and reconnected the google storage credential. Now happened the same and fixed it by reconnecting the google storage oauth credentials.
n8n cloud version
mac
google storage node
It will happen for internal as well, You will need to mark it as in production. You don’t need to go through the verification that is just something that is nice to do but isn’t a requirement.
Thank you Jon for your response. Are you sure you can mark it as production if it’s an internal consent screen?
I’ve been playing around with the screen and the only way to mark it as “production” is to “make it external” in the first place.
@tomilagom that is a good spot, looks like it does need to be external to be set as in production. Looks like there could be another option somewhere for internal apps, I will do some digging through googles docs later to see if I can find anything.
Hi, should this be identified as a bug to be followed up by developers?
Hi Jon. I hope to find you well.
Some information that may help you help us…
To place the application as External (Published) on Google, depending on the API, it must undergo verification…
To avoid verification, I removed the “Logo”… (Yes, the logo)… And the requests that needed public information.
I’ll monitor if I have to log in again and I’ll come back here…
But one fact that intrigues me is why Make doesn’t expire with this authorization. Maybe you know.
Thank you and I’ll come back with information about the Application “without having to publish” on Google, it’s more stable…
Now I am in the process of doing the consent screen “External” and “Production” to avoid the Token refresh issue. It is hard and has a lot of unnecessary requirements for a use case that n8n should solve natively.
In my case, I can’t wait to have a response here. So I created a Google Cloud Function and solved the issue. It’s a little bit disappointing that my second paid SaaS month has gone through without n8n adding value as a service, I will ask for a refund and pause my subscription until I get another use case.
Morning @tomilagom & @Evandro_Caruso,
Sadly there is not an n8n issue here, If you are self hosting n8n and you are using a Google app you will need to set it up as being for Production this is something that Google control not us. Marking it as being for production doens’t need extensive validation or to actually be published and all that will happen is if you have other people logging in to your n8n instance they will be able to authenticate their own account to access thier own data.
The reason Make won’t have this issue will be the same as why n8n Cloud shouldn’t have this issue for most Google Apps, We have an app set up for Cloud which is the same as what self hosted users need to set up the only difference is on cloud we overwrite the key and secret so all you need to do is press the button to log in.
Hi Jon, I have a n8n Cloud subscription and I am required to set up my own Consent Screen. N8n does not facilitate a consent screen to make this easy for N8n customers.
Please let me know if this is not correct.
Hey @tomilagom,
It all depends on the Google resource you are using, Some of them like Google Sheets should show the one click option like this:
The list of Google services that should support this are:
Ok. Thanks for letting me know. I’m using google storage.
That will be it, So in that case you need to follow the rules laid out by Google.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
