The Google Sheets module returns 403 PERMISSION_DENIED when selecting a spreadsheet name

Beginner Questions
,
1

:bullseye: What is your goal?

Hello, Make Support. I am unable to use the Google Sheets module because clicking “Click here to choose file” next to the spreadsheet name in the spreadsheet name field always displays the following error.

:thinking: What is the problem?

403: PERMISSION_DENIED – The method does not allow unregistered callers (callers without established identity). Please use API key or other API consumer ID to call this API. I am using Make on an iPhone (Safari) and have connected my personal Google account.

:test_tube: What have you tried so far?

The following troubleshooting steps have already been completed:

However, the error is reproducible every time. Here are the reproduction steps:

  1. Create a new scenario in Make.
  2. Add Google Sheets → Add a row.
  3. Create a Google connection using custom OAuth Client ID and Client Secret.
  4. Complete Google authentication.
  5. Click “Click here to choose file” below the spreadsheet name.
  6. The 403 PERMISSION_DENIED error appears immediately.

Therefore, the failure occurs when Make attempts to fetch/select the Google Spreadsheet file, not during the initial Google OAuth login. I also found another Make Community report describing substantially the same error: Issue with Google Sheets module – Error 403: The method does not allow unregistered callers. Could you please investigate from the Make side, specifically verifying:

  • Whether the Google Sheets file picker/API request is being sent without the correct API consumer ID.
  • Whether Make is actually using my custom OAuth client ID for the file selection request.
  • Whether old/default/empty credentials are being used internally despite creating a new custom OAuth connection.
  • Whether there is a known issue with the Google Sheets module or Google file picker causing this 403 error.
  • Server-side logs for the failed Google Sheets request, if available.

Additionally, I would appreciate confirmation of the exact current OAuth configuration required for Google Sheets connections in Make in 2026. I can provide screenshots of the error and my Google Cloud OAuth settings if needed. Thank you.

2

Hey there,

this is not an official Make support channel. This community is driven by users such as yourself, trying to help fellow makers.

With that said, did you try following Sam’s guide on how to connect a personal google account?

3

Usually “Add a row” isn’t the first module that users will add to a scenario.

Try performing the Sheets connection with another Sheets module first, like watch rows, search rows, etc.

This might resolve the scope/permission on the connection.

4

Thanks for the suggestion.
I tried creating a new Google Sheets connection using Search Rows instead of Add a Row.

Unfortunately, the same error still occurs:

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.

The Spreadsheet Name field also shows “Failed to load data!”

So the issue also occurs with Search Rows, not only Add a Row.

I can provide a screenshot of this error if helpful.

image
image750×1334 162 KB

5

Hello,

Have you tried @samliew’s tutorial, the one @Stoyan_Vatov linked below?

Specifically, did you add all the redirect URIs, including the duplicates with a /?

You can also try using the map toggle and provide the hardcoded spreadsheet ID (for Spreadsheet Name to check if the connection works.

If it does, add the https://www.googleapis.com/auth/spreadsheets.readonly and https://www.googleapis.com/auth/drive.readonly scopes - most likely these are used to fetch spreadsheet data?

Have a nice day,
Michal

6

This sounds like the OAuth authentication itself is working, but the file-picker request is failing when Make tries to retrieve the spreadsheet list. Since the connection authenticates successfully and the 403 happens specifically when selecting the file, I’d focus on the Drive API/file-picker request rather than recreating the OAuth connection repeatedly.

It may also be worth testing with Make’s default Google connection instead of the custom OAuth client, just to isolate whether the issue is related to the custom credentials or the Google Sheets module itself. If the same 403 occurs, that would provide stronger evidence of a Make-side or Google API issue.

7

Hey there,

could you please explain to me how is the authentication working but the error message in the screenshot is clearly stating that the error is due to an issue with the authentication?

8

Yes, that’s a fair point. What I meant is that the Google OAuth login itself appears to complete successfully, but the error occurs afterward when Make tries to access/select the spreadsheet.

So there may be a distinction between successful OAuth authentication and the API request being properly authenticated/authorized. A connection can be created successfully while a subsequent Google Drive/Sheets API request fails with 403 PERMISSION_DENIED.

That’s why I suggested checking the file-picker/API request specifically, including whether the correct OAuth client or API consumer identity is being passed. The error message definitely indicates an authentication/authorization-related failure at that stage.