Why does Google OAuth2 in n8n ask for another password/login after I already entered the Client ID and Client Secret and clicked “Sign in with Google”? What credentials should be used there when handling client accounts?

Questions
1

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:
3

@Mohammed_Rafeeq can u show error screen and what ask for

4

Welcome to the n8n community @Mohammed_Rafeeq
It’s important to understand that the Client ID/Secret identifies the application, while Google login identifies the account that is authorizing that application.
These documents may help you:

5

@Mohammed_Rafeeq the two prompts are for different things even though both involve Google. the Client ID + Client Secret you entered identify your n8n instance as the app requesting access — that’s the Google Cloud project you (the developer) created. the “Sign in with Google” prompt that follows is asking which Google account is granting access to its data, that’s the end user authorizing your app to read their calendar/gmail/whatever.

so for handling client accounts: each client signs in with their own Google account in that second prompt, n8n stores a separate refresh token per credential entry. you’d create one credential per client (descriptive names like “Calendar - ClientName”) and pick the right credential on each workflow node. one OAuth app, many user-account credentials.

heads up on the consent screen — if you leave it in Testing mode and just add clients as test users, their refresh tokens expire every 7 days and the workflow silently breaks. for real client work you need to publish the consent screen (go to In Production), or switch to a Google service account if your clients let you delegate. test users are fine for development only.