Google Sheets OAuth2 API

[kothireddy_venkatesh]

Hello!

I am trying to create new credential using OAuth2, After selecting OAuth2 I don’t see redirecting uri, client ID & Secret key. How can I resolve this?

Thanks in advance

[Mookie_Lian]

Cloud users do not have to enter fields like Redirect URI, Client ID/Secret; n8n handles this automatically when you Sign in with Google.

[kothireddy_venkatesh]

Tried that way as well but didn’t work, it was showing access blocked error message.

[Jekylls]

Hello @kothireddy_venkatesh !

Could you help me understand a few things please:

1. is this self hosted (via local or docker?) or via provider such as hostinger?
2. have you tried via incognito

It appears there’s an issue with the popup authentication window that should appear immediately after selecting the ‘sign in with google’ - this could be blocked with simple internet permissions or that the browser does not allow popups. check the permissions of your browser here

Let us know how this goes for you we’re here on stand by,

Best,

Jake

[Mookie_Lian]

It was an issue yesterday, redirect_mismatch error, but the fix was released shortly after. You have to upgrade your instance from the admin panel. You can access it from the link I provided, or from this button shown in the image.

[kothireddy_venkatesh]

I’ve tried them all but didn’t work. The issue remains same.

[kothireddy_venkatesh]

I am on 14 day free trial.
I am facing an issue in connecting to my google drive/sheet which halted my research.
Could you suggest me a solution asap?

[Mookie_Lian]

What’s the issue?

[kothireddy_venkatesh]

There is no redirecting uri, client ID,secret key.
When I am trying to connect my google account directly this is the error message popped up

[Mookie_Lian]

As I mentioned above, cloud users do not have to enter client ID, secret or other parameters manually; they are handled automatically by n8n. It’s normal if you do not see them.

The error you are facing, redirect_uri_mismatch is related to a bug that was recently fixed. The fix got released along with the new version of n8n. Upgrade your instance to 2.1.4 from the admin panel.

[kothireddy_venkatesh]

Great!!!
It is now connected, thank you.

[Mookie_Lian]

Nice, you can mark as solution.

Feel free to reach out whenever you have a question!