Gmail connections defaulting to google-restricted for a Google Workspace account

Questions
1

:bullseye: What is your goal?

Adding a connection from a google-email:ActionSendEmail module should create a google-email connection with full Gmail OAuth scopes (gmail.send, gmail.compose, gmail.modify, etc.), regardless of whether the user account is personal Gmail or Google Workspace.

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

WHAT I HAVE TRIED

  1. From inside the google-email:ActionSendEmail module’s Connection dropdown, clicked “Add”. OAuth window opened, I authenticated . Make stored the result as a google-restricted connection with 2 Drive scopes only — no Gmail scopes were requested or granted.

  2. Configured Make as a Trusted app in Google Workspace Admin Console under Security → Access and data control → API controls → App Access Control → Manage third-party app access. The Make app’s status panel now shows “Overridden” with the Trusted radio button selected.

  3. Verified in the same Admin Console that Make is permitted to request the full set of Gmail scopes — the Gmail service detail page for Make shows scopes including “Send email on your behalf”, “Manage drafts and send emails”, and “Read, compose, send, and permanently delete all your email” listed as available.

  4. Re-attempted step 1 (Add a Gmail connection from inside the Send Emails scenario) after the Trusted policy was set. Result: another google-restricted connection was created (ID 8556883), again with 2 scopes only. The OAuth consent screen presented to me did not request Gmail scopes — only Drive.

:clipboard: Error messages or input/output bundles

Make creates a google-restricted connection requesting only Drive-related OAuth scopes. The Gmail Send Email module therefore fails when it tries to use this connection (gmail.send scope not present).