403 (insufficientPermissions): Insufficient Permission GoogleMail Connection

Getting Started
, ,
1

I’ve just managed it to solve my last problem with the “Failed to verify connection. Status Code Error: 400” by reauthorizing my connections and verifying them, but now I am getting this 403 error as mentioned above. I am on a free google plan and didn’t publish it in my google cloud console so far as I just want to explore some mail-automation use cases for now.

Can anybody help me?

2

You can try creating new credential on console and see if that works.

1 Like
3

Welcome to the Make community!

You will have to create a GCP account & app either way if you want to use your personal Gmail account.

Follow this main guide on how to set up a custom OAuth 2.0 custom app in Make.

Provided below are additional supplementary instructions in case the above isn’t clear enough.

Enable APIs

1. Enable the relevant APIs that you want to use

Search for the relevant Google API here: https://console.cloud.google.com/apis/library

  • Go to each API page that you want to use, end click “Enable”

  • Usually you’ll want to enable at least Drive (includes Docs/Sheets) and Gmail.

OAuth Client

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

2a. Create “OAuth client ID” Credentials

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

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/google
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/youtube
https://www.make.com/oauth/cb/oauth2
https://www.integromat.com/oauth/cb/oauth2

Note: Once you’ve set these up, you can use/reuse the same Make connection for all the supported Google apps & modules on Make - you’ll only have to enable the APIs for your custom app.

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”.

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. Step through and go to dashboard

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

3d. Publish your 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

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:

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

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

4

I’ve tried this, but this led to another error message. I had to delete and re-set up the connection, which was actually easier than expected because everything in GCP was already set up. I’ve just created a new secret key.

Thank you very much for your quick help!

5

I have the same problem, so did it help?