I have existing workflow on N8N where I am using Google sheet trigger to authorize reading data from my google sheet located on google drive. This account and workflow was working fine for past few days and now I am unable to reauthenticate the Google sheet credentials, all of a sudden.
I already tried creating new Oauth client in my GCP account, a well as tried adding new credentials in my N8N account. When I generate the GCP oauth token using postman, it works fine and I get valid token. But N8N credentials integration keeps failing with Unauthorized error.
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Please find the additional details:
- n8n version: 1.18.0
- Database (default: SQLite): default
- n8n EXECUTIONS_PROCESS setting (default: own, main): default
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: Ubuntu, hosted on EC2
Hi @gsonal Welcome to the community
For Google Cloud apps with Publishing status set to Testing and User type set to External , consent and tokens expire after seven days - could this be what you’re running into? If you re-authorise the application, does it work?
Hi @EmeraldHerald , Thanks for your reply !!!
The token did expire after seven days, but we have been running it in Testing mode, as we have not been able to enable SSL yet over our N8N docker instance. Since last two months, every week we will re-authorize and it would work.
But this time at the last step of Google Sign-in it keeps giving “Unauthorized” error. There is no error in N8N or GCP logs. Lastly, as I stated in my original post, we are able to generate token using Postman.
Our automation is completely blocked as Google sheet trigger is the first step.
I tested my automation again and still google authorization step is failing at last step after specific google API permissions are added. Due to lack of errors, I am unable to use N8N anymore and have moved my automation to another platform. It would have been better if this issue could be resolved, as N8N being self-hosted was more preferrable as a No-code tool for our business.
Hi @gsonal
sorry to hear this
You posted earlier you were running on n8n version 1.18.0
…
I would like to know if you would still experience this issue on a recent version. Do you think you could try again after updating?
Hi @ria ,
Thanks for your reply.
At this point, since I already moved my automation outside N8N, this activity of attempting Google sheet authentication on latest N8N version is becoming a low priority for my team, hence I dont know when I will be able to give this a try at my end.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.