Google Drive folder picker returns 403: “unregistered callers”

Questions
1

:bullseye: What is your goal?

I want to create a Make scenario that creates a text file in my Google Drive.

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

I am using the Google Drive “Create a File from Text” module with a custom Google OAuth connection. Google authentication succeeds and the connection is created successfully. However, when I click “Click here to choose folder” in the module, the folder picker fails with a 403 error. I have also refreshed the connection and created a new connection with the same result.

:clipboard: Error messages or input/output bundles

[403] 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)

Screenshot_20260904-103808.png
Screenshot_20260904-103808.png1080×2520 274 KB

3

That 403 is coming from the folder picker request, so I’d first separate a picker problem from a Drive connection problem:

  1. Change the Folder field from “select from list” to Map / enter manually.
  2. Paste the folder ID from the Google Drive URL and run the module with a tiny text file.

If the file is created, your OAuth connection and Drive write permission are working; only the picker is failing. You can keep the mapped folder ID as a workaround and report the picker issue to Make Support.

If the run also fails, check the custom OAuth project against Make’s setup guide: Drive API enabled, the required Drive scopes added, the correct Make redirect URI, and your Google account added as a test user (or the app published). Then recreate the connection once after those settings are corrected:

Reauthorizing the same connection won’t help if the project configuration is unchanged, so the manual-folder test is the quickest way to isolate this.