Google Drive Authentication Error

Questions
,
1

Hi there

I have been having issues authenticating my Google Drive

I have gone through the process of:

From there I go back to n8n, and add credentials and as soon as I sign in with Google I get Google hasn’t verified the app

image
image471×312 13.5 KB

And when I continue I get this error:

image
image483×212 5.18 KB

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

Please help, has anyone come across this issue recently?

5

I have the same problem, it worked well until today, when suddenly it fails exactly in the same way you describe - I re-created Google API credentials and re-created the n8n credential from scratch but still same result

6

My intended workflow was to access Google Drive, locate a Google Doc, download and push to Pine Cone Vector. But with the download failing I opted swopping out the Google Doc for PDF. This seems to work fine. But I would still prefer downloading a Google Doc in order to mark up the Doc itself

8

Hi @Jacques.Grobler
what version of n8n are you using? I just tried using n8n 1.79.1 and I have no issues
could you also try resetting your client secret and see if that helps?

9

Hi @Shireen

I have changed over to version 1.79.1 and I have reset my client secret a few times, still the same result

image
image473×154 3.89 KB

10

Has anyone else managed to resolve this yet?

1 Like
11

Hey @Jacques.Grobler!

I’ve just tried to use Google Drive on v1.81.2 and it worked as expected for me.

Have you set up the Google redirect URL to point to your cloud instance and added the n8n cloud domain as authorized?
This may be why you’re getting the “Google hasn’t verified this app” message.

CleanShot 2025-02-28 at 16.17.59
CleanShot 2025-02-28 at 16.17.59526×132 11.4 KB

CleanShot 2025-02-28 at 16.14.13
CleanShot 2025-02-28 at 16.14.13559×298 18.8 KB

Can you try to update to the latest version of n8n and check if it works?

Thanks!

12

Hey Marc

Thanks for your response

I have n8n.cloud as auth domain:
image

And I have a URI with my base url added to the auth URIs:
image

And I am still not able to access Google Drive

13

I have the same issue using localhost,

http://localhost:5678/rest/oauth2-credential/callback

Debug info

core

  • n8nVersion: 1.81.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.3
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId:
14

I have the same issue when downloading a file from Google Drive API.

“Forbidden - perhaps check your credentials?
Request failed with status code 403”

This workflow used to work perfectly fine until n8n v 1.8.x

Has anyone found a fix?

15

I worked around this by configuring a reserve proxy

16

hey, I also tried everything and getting this message:

Google hasn’t verified this app

The app is requesting access to sensitive info in your Google Account. Until the developer verifies this app with Google, you shouldn’t use it.

If you’re the developer, submit a verification request to remove this screen. Learn more

1 Like
17

I have a similar problem. Every time I start n8n in my local environment (using Docker) and access the platform, I encounter a persistent issue with Google credential authentication. When trying to execute any operation that requires integration with Google services (e.g., Google Docs), the following error occurs:

“The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.”

image
image886×417 72.2 KB

This error indicates that the authorization flow with the Google credentials is not completing correctly due to an issue with the authentication token or the redirection URI configuration.

Environment details:

  • I’m using ngrok with a fixed domain to create a redirection tunnel.
  • n8n is set up locally with Docker (version 1.78.1).
  • The error persists regardless of which Google service I try to authenticate. After each n8n startup, the Google credentials fail to authenticate, and I always receive this error message.

Additionally, even though the Google Docs account shows as “connected” in the n8n interface (as seen in the attached screenshot), the issue remains when trying to perform tasks with Google Docs. Despite the interface indicating the account is connected, authentication continues to fail. This suggests there might be a discrepancy with the tokens or credential synchronization, even though n8n recognizes the account as connected.

image
image1844×413 27.6 KB

Has anyone experienced a similar issue or have any suggestions on how to fix it?

18

Hi I also came across this problem earlier before.

I found out one of the issues for that is the google cloud project is on test mode and you might have to approve your email to make it work by adding it in under the test user section.

I managed to make it work after adding that in so hope this helps those who face this same issue as well!

Screenshot 2025-03-22 at 3.19.43 PM
Screenshot 2025-03-22 at 3.19.43 PM1536×1118 91.7 KB

4 Likes
19

Hey- Have you managed to fix it?

20

I’m also on this ‘party’. It seems like there’s a requirement to verify the app. Although my ‘app’ has no real users - it’s a fully automated flow, yet, since it’s using ‘sensitive scopes’ (gdrive, etc.) google requires to verify your “app”. I haven’t yet managed to pass their verification yet.

1 Like
21

this doesn’t seems to work for me… why google made all this so difficult, feel like a god damn endless maze… don’t know what to do now…

1 Like
23

Ihi, wouldn’t you be able to use a service account instead?

1 Like