Google OAuth redirect_uri_mismatch on n8n Cloud – inconsistent redirect URIs

Questions
, , ,
1

I’m experiencing a persistent issue when connecting Google credentials (Google Docs / Drive / Sheets) on n8n Cloud.
No matter how I configure Google OAuth, I always end up with a redirect_uri_mismatch (Error 400), and after a full day of troubleshooting I believe the issue is caused by inconsistent redirect URIs generated by n8n Cloud.
:red_circle: The problem
In the n8n credential UI, the OAuth Redirect URL shown is:
https://oauth.n8n.cloud/oauth2/callback
However, when the OAuth flow fails, Google’s error details show that n8n actually sends:
https://eartigas.app.n8n.cloud/rest/oauth2-credential/callback
This means:
The redirect URI displayed by n8n ≠ the redirect URI actually used during the OAuth flow.
Google rejects the request with:
Error 400: redirect_uri_mismatch
:red_circle: Exact Google error message
Error 400: redirect_uri_mismatch
The redirect URI in the request does not match the authorized redirect URIs.
Request details:
redirect_uri=https://eartigas.app.n8n.cloud/rest/oauth2-credential/callback
flowName=GeneralOAuthFlow
What I already tried
Created multiple new Google Cloud projects
Created new OAuth Client IDs
Correctly configured OAuth Consent Screen
Added both redirect URIs to Google Cloud:
https://oauth.n8n.cloud/oauth2/callback
https://eartigas.app.n8n.cloud/rest/oauth2-credential/callback
Cleared browser cache & cookies
Tried in private/incognito mode
Restarted sessions and credentials
Verified domain authorization and test users
Verified Client ID / Client Secret
Verified scopes (Drive, Docs, Drive.file)

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.1.2
  • Database (default: SQLite): PostgreSQL (managed by n8n Cloud)
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
  • Operating system: n8n Cloud (managed environment)
2 Likes
2

Exact same problem how do we get someone to fix this? ive seen this issue a few times now from different users and i havent seen a solution posted

2 Likes
3

+1 exact situation happen at my case. must be n8n and google’s integration goes wrong

4

same issue here

5

Try updating your n8n version to 2.1.4 or later. It was a known issue that should be fixed if you update the version. Fingers crossed!

1 Like
6

I struggled with this for a work day. This fixed handled it!

Thank you,

1 Like
7

I’m very happy it worked for you @Seniors_Helping_Seni!! Hopefully this helps @Esteve_Artigas_Fonta as well! If it does, please make sure to mark my post as the solution :slight_smile:

8

Same issue here. How does one fix this issue if we are using the cloud version? Shouldn’t it be using the latest update by default?

9

Hi @Alexandre_Saussier, nono.. you need to update it manually. Go to the Admin panel, and look for the n8n version there. Hopefully this works for you :slight_smile:

10

It worked, thank you!

1 Like