Unable to connect Gmail to Make.com using custom Google OAuth credentials due to restricted Gmail scopes and OAuth authentication errors

Questions
, ,
1

:bullseye: What is your goal?

I want to send emails from Make.com using my personal Gmail account with a custom Google OAuth app/client ID and client secret created in Google Cloud Console.

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

I created a Google Cloud project and configured OAuth 2.0 for Make

i completed all steps but still gmail not connecting with make

Added redirect URI:
https://www.make.com/oauth/cb/google

http://make.com/oauth/cb/app

However, when trying to connect Gmail in Make.com, I receive these errors:

Access blocked: This app’s request is invalid

and

[401] Request is missing required authentication credential.
Expected OAuth 2 access token, login cookie or other valid authentication credential.

:clipboard: Error messages or input/output bundles

I am using a personal Gmail account (@gmail.com), not Google Workspace.

I want to know:

Is custom Gmail OAuth no longer supported for personal Gmail accounts in Make.com?
Do I need Google Workspace?
Should I use SMTP with App Password instead?
Is there any workaround for restricted Gmail scopes with personal Gmail accounts?

3

For personal Gmail, restricted scopes are the usual blocker. If your Google OAuth app isn’t verified for Gmail scopes, Google can block the consent flow even if the redirect URI looks right. For sending only, SMTP + app password can be simpler, but that depends on whether 2FA/app passwords are enabled. I’d first confirm the exact Gmail module/scopes Make is requesting, then decide between verified OAuth, Workspace, or SMTP

4

Welcome to the Make community!

You did not complete ALL the steps exactly. Please see Step 2: Create OAuth Client, Step 3b: OAuth Scopes 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

Related Topics:

— @samliew