Unable to create Google Sheets OAuth2 API Connection in n8n Cloud? Error 400: redirect_uri_mismatch?
Hi all,
I’ve looked at a couple different variations of this problem here, and am unsure how to move forward. Effectively, every other time I’ve tried to set up a Google Sheets OAuth2 API credential in n8n, I’ve been given the option to enter a client ID and client secret. However, I am now no longer able to do so. I’m now greeted with this screen:
I’ve tried following the steps in this video, but am really at a loss given that I don’t even get the opportunity to enter credentials before the authorization process fails. Any help would be GREATLY appreciated. Thanks!
I am getting the same exact error. This is not only happening to my account, this is happening to any other google account I try to connect (workspace or personal). I have reached out to support and created ticket T-30470. This happened right after I updated my version to 2.1.2
No, I was contracted by someone to do some work for them involving n8n, and am attempting to connect n8n to their Google environment. They just signed up for n8n Cloud today.
I am also having the same issue with this. I followed all these steps and there is no URI available to paste in Google Cloud. I am unable to sign in and I was in the motion of getting Google Sheets to function correctly. Please help us.
Hi @lrp I would recommend going the Service Account route as this avoids you having to refresh the login from time to time. This way you can also avoid trying to find the callback url to use for cloud.
Seeing as this is for a client, you can then also impersonate a user on the clients account. Useful when trying to send gmail mails as a certain account instead of the logged in one
PS, just remember to share any google drive folders and files with the service account email which gets generated
That is a good work around @Wouter_Nigrini There are some tools (like Google Calendar) that does not support the service account option hence, this is a big problem. Guide with types of accounts that can use the service account is here.
I have the same issue! earlier it wasn’t like that. now I have updated to version 2.1.3 and it gave me that new error message. looking forward to fix this asap