400 redirect_

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:

When I attempt to “Sign in with Google”, I am immediately greeted with this screen, prior to ever entering credentials:

When I look at the error details, I see the following:

The Authorized redirect URIs appear accurate in my Google Cloud config:

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!

2 Likes

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

1 Like

Thank you for letting me know; I was pulling my hair out here!

1 Like

Did it happen to you after updating to the newest version?

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.

Hey do you guys have an update or any fixes on this? Im having the exact same issue across all my google accounts personal and workspace

2 Likes

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.

I don’t even have a Redirect URL. What can I do??

2 Likes

I am also experiencing the same problem with Google Docs.

2 Likes

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

I’m experiencing the exact same issue and it’s driving me crazy!

1 Like

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.

It is driving me crazy too, we are on the same boat.

By the way, this seems to be an n8n issue only. I tried connecting my google calendar account in make.com and got through with no issues.

There seems to be quite a few similar issues logged on the forums. I have given a reply here but users are saying its still a bug.

This seems to be fixed under update 2.1.3

Well - Not quite…

It allows me to select my account and then enter my password. When the permissions are granted, I get error” something went wrong, please try again.

1 Like

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

1 Like

seems its the problem from n8n, i hope they fix this asap!

1 Like

@amirsrtp this has been resolved in the latest n8n version

Thanks for telling! Just updated, it works✌️