Google OAuth — n8n Credentials Reference
Maps Google Cloud OAuth clients to n8n credentials and the workflows that use them. Last updated: 2026-06-15 (bms-4 migration + redirect URI registration).
Accounts & Projects
radieu@gmail.com — Project N8N-documentsProcessing
GCP project ID: n8n-documentsprocessing
| OAuth Client | Client ID prefix | Purpose |
|---|---|---|
n8n-rkm-local-docker | 616687203473-ggg4... | Local dev only — not used in production |
p24-n8n-bms-4 | 616687203473-a8ic... | bms-4 n8n main client (renamed from p24-n8n-hostinger-2y) |
N8N-Gdrive-P24 | 616687203473-vrfp... | Google Drive + Sheets workflows |
Both p24-n8n-bms-4 and N8N-Gdrive-P24 have registered:
- JavaScript origin:
https://n8n.bms-4.infra.zintegrowana.online - Redirect URI:
https://n8n.bms-4.infra.zintegrowana.online/rest/oauth2-credential/callback
n8n credentials (bms-4) using this account:
| Credential name | n8n ID | Type | Used by workflows |
|---|---|---|---|
Gmail account - radieu@gmail.com | P1dYU1OR6Z1qQ0Zu | gmailOAuth2 | invoices registration 2 pinbox |
Google Drive account | RKpUbgQMTZtErvur | googleDriveOAuth2Api | atrax/kravag, Tronik GPS upload |
Google Sheets account | Hw0yWyWfKHTEwaIW | googleSheetsOAuth2Api | atrax/kravag, interrcars, Update Fleet From Driver Reports |
Google Calendar account | WkDtkOZCeCUOkO7j | googleCalendarOAuth2Api | — |
YouTube account | LJEBoS3T9q9QRkwD | youTubeOAuth2Api | — |
ecotrans.automation@gmail.com — Project et-n8n-automation
GCP project ID: et-n8n-automation
| OAuth Client | Client ID prefix | Purpose |
|---|---|---|
n8n-ecotrans-automation-gmail-web-client | 1096943796691-kg2... | Gmail triggers for Tronik GPS workflows |
Klient na komputerze 1 | 1096943796691-8cm... | Desktop client — unused in current workflows |
n8n-ecotrans-automation-gmail-web-client has registered:
- Redirect URI:
https://n8n.bms-4.infra.zintegrowana.online/rest/oauth2-credential/callback
n8n credentials (bms-4) using this account:
| Credential name | n8n ID | Type | Used by workflows |
|---|---|---|---|
Gmail ecotrans.automation@gmail.com | tD8Cz6GiF3zmrtki | gmailOAuth2 | Tronik GPS - Kierowcy, Tronik GPS - Serwisant mobilny |
Re-authorization was required during bms-4 migration (2026-06-15) — new client secret created, credential reconnected.
Re-authorization Procedure
If a Google credential on bms-4 shows 'undefined' errors in n8n logs:
- Open
https://n8n.bms-4.infra.zintegrowana.online→ Credentials - Find the failing credential → Edit
- Check the Client ID to identify which GCP project/client it uses (table above)
- If client secret is needed: GCP Console → project → Klienty → client → Add secret (old secrets can’t be viewed)
- Paste new secret into n8n credential → Save → Reconnect
Planned: Document Processing Migration to bms-4
Document processing workflows are currently running on a separate cloud instance.
Migration target: bms-4 n8n (n8n.bms-4.infra.zintegrowana.online).
When migrating:
- All redirect URIs are already registered in both GCP projects — no Google Console changes needed
- Identify which GCP client the document processing credentials use (check Client ID in n8n UI)
- Re-authorize credentials through bms-4 n8n UI after migration
- Relevant GCP project for document processing: likely
N8N-documentsProcessing(radieu@gmail.com)