Problem with several APIs

Questions
1

Hello everyone,

I have encountered a problem when creating credentials in the Gmail, Google Sheets, and Google Calendar APIs.

The problem is that when I want to create credentials for the aforementioned APIs, the OAuth 2.0 fields for entering a client_id and client_secret do not appear. I have tried with Google Drive, and in this case it works.

I have version 1.114.4 and am using n8n cloud.

Does anyone know why this is happening? It didn’t happen before.

Example:

Gmail

image
image1320×521 25.9 KB

Google calendar

image
image1324×618 27.8 KB

Drive:

image
image1315×645 32.5 KB

Regards

2

This is a change in n8n’s OAuth credential handling for certain Google services. Here’s what’s happening:

Issue

n8n has implemented two different OAuth approaches for Google services:

  1. Simplified OAuth (Gmail, Google Calendar, Google Sheets):

    • Only shows “Sign in with Google” button

    • n8n handles the OAuth app credentials in the background

    • You don’t need to create your own Google Cloud project

  2. Manual OAuth (Google Drive, some others):

    • Shows Client ID and Client Secret fields

    • You must create and configure your own Google Cloud project

Why this is happening

n8n made Gmail, Calendar, and Sheets simpler to set up by using their own OAuth application. However, this means:

  • :cross_mark: You can’t use your own OAuth credentials

  • :cross_mark: You’re limited by n8n’s OAuth quotas

  • :cross_mark: Less control over the OAuth consent screen

Suggested solutions

  1. Use the built-in OAuth

Just click “Sign in with Google” - it should work for most use cases.

  1. Force Manual OAuth Configuration

If you need to use your own OAuth credentials, you can try:

  1. Use the generic OAuth2 credential instead:

    • Create a new credential

    • Select “OAuth2 API” (generic)

    • Manually configure it for Gmail/Calendar/Sheets

  2. Check for credential type variants:

    • Look for credential types like “Gmail OAuth2 API” vs “Gmail account”

    • Some might still have manual fields

  3. Use environment variables (self-hosted only):

    • You can set custom OAuth credentials via environment variables if you’re self-hosting
  1. Contact n8n cloud support

Since you’re on n8n Cloud version 1.114.4, this might be intentional for their managed service. You can:

  • Reach out to n8n support at https://support.n8n.io

  • Request manual OAuth configuration for these services

  • Ask if there’s a way to override this behavior

Suggested workaround for you

If you absolutely need custom OAuth credentials:

  1. Export your workflow from n8n Cloud

  2. Self-host n8n (you’ll have full control)

  3. Configure custom OAuth credentials there