Hi everyone,
I am trying to connect Google OAuth2 in n8n.
I already added the Google Client ID and Client Secret correctly. But when I click “Sign in with Google”, it asks for a client password/login again, and I am confused about what credentials it needs.
My doubt:
Should I use my Google account password?
Or is there another password related to Google Cloud Console?
How do agencies or developers handle this when working for clients?
I want to understand the correct workflow for handling Google OAuth2 credentials for client projects in n8n.
Thanks.
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.)
This is to make sure the Client ID and Secret are tied to the correct Google account.
If your Client ID and Secret are meant for account A, you do not want account B to access it, do you?
The Client ID and Secret are from your Google Cloud Console app - they identify your application, not any user account. When n8n opens the “Sign in with Google” screen, it’s asking which Google account should be authorized to use that app. For client work, the flow is: you build the Google Cloud project (Client ID/Secret), then the client logs in with their own Google account during that OAuth screen. The resulting credential in n8n is tied to the client’s account data. A cleaner agency setup is to have the client create the Google Cloud project themselves and share the Client ID/Secret with you - that way the credential and quota belong to them from the start.
In sign in it ask for the Google account.which i used to create client id and client secret.so the account belongs to client.so how I ask clients google password.if i already add myself admin in client google console cloud for their project. I created credentials and enable needed api .and copy and fill in my n8n instance.then it ask sign-in.so I need to sign in with the account I used to create google console cloud.so that is client account.is it ask clients google account.if it really ask that .how I manage that.
Although you have configure n8n with the Client ID and Client Secret. Even then authorization is required, the client still signs in with their own Google account to approve access.
You may ask the client to perform the Google sign-in themselves, either by screen sharing or remote session.
good morning @Mohammed_Rafeeq
the Client ID and Client Secret only identify the application in Google Cloud.
the Google account login, “Sign in with Google”, Google is asking which account will authorize this application. Don’t ask for the client’s password, what I’ve seen is consulting creates/configures the OAuth app, client logs in directly to Google, client authorizes the scopes, Google returns OAuth token to n8n. It will all depend on who owns the data at the time of login. Being an admin does not allow you to have access as an admin to the user’s apps and data.
@Mohammed_Rafeeq if you want to avoid the sign-in step entirely, consider using a Google Service Account instead of OAuth2. Create a Service Account in Google Cloud Console, download the JSON key file, and use n8n’s “Google Service Account” credential type. The service account authenticates server-to-server without any sign-in popup - you just share the relevant Google Drive folders/Sheets with the service account email and it has access. This is cleaner for client workflows where you don’t want to involve the client’s credentials at all.
