# Problems with google oauth credentials

**URL:** <https://community.n8n.io/t/problems-with-google-oauth-credentials/240822>\
**Category:** Questions\
**Created:** [December 24, 2025, 10:58pm UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822 "2025-12-24T22:58:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Diego\_Villar\_Garcia](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/diego_villar_garcia/32/51966_2.png) [@Diego\_Villar\_Garcia](https://community.n8n.io/u/Diego_Villar_Garcia)\
**Post date:** [December 24, 2025, 10:58pm UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/1 "2025-12-24T22:58:26Z")

</div>

# Access blocked: This app’s request is invalid

[avasystemsai@gmail.com](mailto:avasystemsai@gmail.com)

You can’t sign in because this app sent an invalid request. You can try again later, or contact the developer about this issue. **[Learn more about this error](https://developers.google.com/identity/protocols/oauth2/web-server#authorization-errors-redirect-uri-mismatch)**

If you are a developer of this app, see **error details**.

Error 400: redirect\_uri\_mismatch

This shows on my screen every time I try and get OAuth for any google credential. I have tried everything, and made the correct steps in Google Cloud Console. We really need n8n to fix their redirection urls ASAP.

I noticed this issue yesterday but I dont know if these kinds of issues are happening frequently to users.

## Describe the problem/error/question

## What is the error message (if any)?

## Please share your workflow

```auto
(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:**
- **Database (default: SQLite):**
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app):**
- **Operating system:**

---

<div class="post-metadata">

**Author:** ![iamYannC](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/iamyannc/32/147549_2.png) [@iamYannC](https://community.n8n.io/u/iamYannC)\
**Post date:** [December 25, 2025, 12:58am UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/2 "2025-12-25T00:58:07Z")

</div>

Hey man. I had the exact same problem and my solution was to create a service account in google console, and just use it for my google nodes (for me specifically it was Drive). No matter what I tried, the auth just didnt work. im actually glad to see its not just me.  
Anyway, go create a google service account. If you’re struggling I’ll add some SC of how i did it & linked to n8n

Pick Credentials (I’m assuming you know how to get here)

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/d/2d00d726bf814b59d4e25305a9f0724b3a4a81ba.png)

Then click to create a new service account

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/8/5/85d29802d96c3cf62035ee5ca88cdaa54c4def14.png)

Theres a shor 4-step creation process. I believe you will manage it.

You will be given a private key that starts with —-BEGIN PRIVATE KEY \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* — END PRIVATE KEY (or something similar). this, including the hyphens, IS YOUR PRIVATE KEY (lol). store it

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/e/0/e0a0b8925e7cf25aa2c666398fd806abafed02e0.png)

This worked for me, even after the normal auth didnt. why? who the heck knows

---

<div class="post-metadata">

**Author:** ![NangAnhIUH](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/nanganhiuh/32/78159_2.png) [@NangAnhIUH](https://community.n8n.io/u/NangAnhIUH)\
**Post date:** [December 25, 2025, 1:53am UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/3 "2025-12-25T01:53:23Z")

</div>

Dear YannC,

I encountered the same problem. It may be an issue with the REST API.  
The only thing we can do is wait for a fix in the new version.  
If you need to refresh your credentials, you can probably roll back to version 1.x.

---

<div class="post-metadata">

**Author:** ![Diego\_Villar\_Garcia](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/diego_villar_garcia/32/51966_2.png) [@Diego\_Villar\_Garcia](https://community.n8n.io/u/Diego_Villar_Garcia)\
**Post date:** [December 25, 2025, 6:41pm UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/4 "2025-12-25T18:41:22Z")

</div>

Thanks a lot Yann. I’ll see if this helps.

---

<div class="post-metadata">

**Author:** ![ailinwerner](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ailinwerner/32/131720_2.png) [@ailinwerner](https://community.n8n.io/u/ailinwerner)\
**Post date:** [December 26, 2025, 12:36pm UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/5 "2025-12-26T12:36:06Z")

</div>

Go to your n8n Cloud dashboard (Admin Panel) and check if an update is available. Upgrading to 2.1.4 or later should immediately fix the redirect\_uri\_mismatch error without you needing to change anything in Google Cloud.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [March 26, 2026, 12:37pm UTC](https://community.n8n.io/t/problems-with-google-oauth-credentials/240822/6 "2026-03-26T12:37:02Z")

</div>

Closed on March 26, 2026, 12:37pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
