Issue with Google Sheets Module: Error 403 “Method doesn't allow unregistered callers"

Questions
,
1

I am unable to connect any app that uses Google OAuth authentication in Make.

:thinking: What is the problem & what have you tried?

I keep getting a 403: PERMISSION_DENIED error when trying to select a spreadsheet in the “Spreadsheet Name” field.
What I have already tried:

  1. I enabled both the Google Sheets API and Google Drive API in my Google Cloud Console.
  2. I configured the OAuth consent screen and created a new OAuth 2.0 Client ID (Web application type).
  3. I set up a new connection in Make using my custom Client ID and Client Secret via Advanced Settings.
    Despite doing all of this, the error still occurs as soon as I click on the Spreadsheet Name field.

Additional Issue / Critical Clue (Even Incognito Mode Bypasses Login):

I noticed another major issue: the Google login pop-up window doesn’t even appear properly.

When I click Create a connection and then click Sign in with Google, the browser does not open the Google account selection screen at all. It just skips the login page entirely and immediately saves the connection with the old, broken session.

I have already tried using an Incognito (Secret) Window to force a fresh login, but the exact same problem occurs. Even in Incognito mode, the Google login pop-up simply won’t open and completely bypasses the authentication step.

I tried connecting a different app (Inoreader) as well, and it has the exact same issue. It feels like Make is caching an old, incorrect authentication session at the system level and refusing to trigger a fresh Google OAuth login prompt, which might be why the 403 error persists.

:clipboard: Error messages or input/output bundles

Error Message:
403: PERMISSION_DENIED - Method doesn’t allow unregistered callers (callers without established identity). Please use API Key or other form of API consumer identity to call this API.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

IMG_2451
IMG_24512514×1473 210 KB

IMG_2452.jpeg
IMG_2452.jpeg911×1334 210 KB

2

Hi @seungwonh05

I understand this must be really frustrating.

In simpler terms this means Google servers are certainly receiving an API request from make.com but somehow Google is unable to verify the identity of the project making that request.

This is honestly complex and I suspect 3 potential causes. Let’s start from the least.

  1. Make could be having internal technical issues which could be resolved ASAP. This is highly unlikely but should the problem persist then the next two potential causes might be suspected.

  2. This is based on my experience with APIs generally. The fact that your browser bypasses login prompts even when you use other apps/incognito plus the “unregistered caller” error could mean default or empty credentials are being passed behind the scenes instead of your custom configuration, since that pop up helps to bundle your client ID and secret into a OAuth request. Try checking your “Credentials” page on Make and if anything related to this specific integration is saved there please remove it and retry the entire integration afresh.

  3. My third suspect is potentially a misconfiguration on the Google cloud side of things. You should try to add Make’s official redirect URL. Also check if your OAuth Consent screen publishing status is still in “testing” mode. If yes, you might need to manually add the Gmail address as one of the Test users just to be extremely sure. Because if it’s not added Google might not recognize the Gmail as part of that project. and hence the identity problem.

Is there more information from your troubleshooting?

3

Welcome to the Make community!

Please see Step 2: Create OAuth Client, Step 3b: OAuth Scopes, Step 3d: Publish App below.

How to Connect and Use Google APIs in Make!

0. Prerequisites

1. Enable Google APIs

2. Create OAuth Client

Direct Link: https://console.cloud.google.com/apis/credentials

  • 2a. Create “OAuth client ID” Credentials

    455×206 15.2 KB

  • 2b. Insert all the Google Redirect URIs for your app

    302×200 7.32 KB

    Insert All Google Redirect URIs

    Here are some commonly-needed redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.

    https://www.make.com/oauth/cb/oauth2
https://www.make.com/oauth/cb/google
https://www.make.com/oauth/cb/google/
https://www.make.com/oauth/cb/google-email
https://www.make.com/oauth/cb/google-custom
https://www.make.com/oauth/cb/google-restricted
https://www.make.com/oauth/cb/google-cloud-speech
https://www.make.com/oauth/cb/google-search-console
https://www.make.com/oauth/cb/google-analytics-4
https://www.make.com/oauth/cb/google-ads2
https://www.make.com/oauth/cb/google-ads2/
https://www.make.com/oauth/cb/youtube
https://www.make.com/oauth/cb/chrome

    Including These Google Redirect URIs

    You are also required to insert the legacy URLs below from the old Integromat system that not been migrated to Make yet (same as the above list, but replace “make” with “integromat”):

    https://www.integromat.com/oauth/cb/oauth2
https://www.integromat.com/oauth/cb/google
https://www.integromat.com/oauth/cb/google/
https://www.integromat.com/oauth/cb/google-email
https://www.integromat.com/oauth/cb/google-custom
https://www.integromat.com/oauth/cb/google-restricted
https://www.integromat.com/oauth/cb/google-cloud-speech
https://www.integromat.com/oauth/cb/google-search-console
https://www.integromat.com/oauth/cb/google-analytics-4
https://www.integromat.com/oauth/cb/google-ads2
https://www.integromat.com/oauth/cb/google-ads2/
https://www.integromat.com/oauth/cb/youtube
https://www.integromat.com/oauth/cb/chrome

    Note 1: Due to inconsistencies in Make’s implementation of the connections, there are two separate entries where has one is google and another ending in a forward slash google/ - you might need one or the other, so we have to use both!

    Note 2: Once you’ve set these up, you can use/reuse the same Google OAuth App ID + Secret for all the supported Google connections and modules on Make - you’ll just have to enable the relevant Google APIs!

3. OAuth consent screen

Direct Link: https://console.cloud.google.com/apis/credentials/consent/edit

  • 3a. Insert Two Authorised Domains

    • Insert make.com and integromat.com

    • Fill in other required fields

    • Click “Save and Continue”.

      390×301 14.1 KB

  • 3b. Add All Scopes

    • Click “Add or Remove Scopes”

    • Select 100 “Rows per page”, for each page, check all the rows, OR

    • Manually type in the scopes you need

    • Click “Update” at the bottom

    1476×1156 182 KB

  • 3c. Skip Verification

    • Step through until you reach back to the dashboard

    • At the last step/page, click “BACK TO DASHBOARD” instead of “Prepare for Verification”

  • 3d. Publish the GCP OAuth2 app

    You will need to set your OAuth application to “Production”, otherwise the credentials expire very frequently.

    • To do this, go back to “OAuth consent screen”

    • Then click the “PUBLISH APP” button

    • Then click the “CONFIRM” button

    479×206 9.36 KB

4. Create New Connection (HTTP, or respective Google module)

You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the callback URLs in step 2:

471×488 18.6 KB

  • 4a. Specific Google module (Sheets, Docs, Drive, Gmail, etc.)

    Insert the GCP app client ID and secret here BEFORE clicking “Sign in”

    (Gmail example)

    525×643 65.1 KB

    OR,

  • 4b. HTTP OAuth 2.0 Request module

    708×401 44.2 KB

    You need a “Authorize Parameters” key of redirect_uri with the above Make OAuth2 callback URL.

    597×904 61.2 KB

Also see related topic: Gmail/Google Drive verification issues (error 400): how to solve

— @samliew