After creating OAuth App I still have issues with connecting personal Gmail

Hi everyone,

I tried to make a connection with my personal Gmail account as I need it for learning purposes.

I created an app in Google Cloud following steps listed here: https://www.make.com/en/help/connections/connecting-to-google-services-using-a-custom-oauth-client?_gl=1*nqkq14*_gcl_au*MjAzNTUyMjcxNS4xNzIzMTk3MDY1*_ga*MTQ1NzA5OTI5Mi4xNzIzMTk3MDY0*_ga_MY0CJTCDSF*MTcyNDIyNDk2My4xNy4xLjE3MjQyMjUwNzAuNjAuMC4w

Nevertheless, I’ve got this problem when I tried to connect Gmail using client credentials:

What should I do in this case?

Hi Illia,
You need to use your own OAuth credentials.
Follow the directions on Make’s Gmail documentation for step by step instructions on how to do so.

1 Like

Did you “Publish” the app to production?

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

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

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.


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)

OR,

4b. HTTP OAuth 2.0 Request module

You need a “Authorize Parameters” key of redirect_uri with the above Make OAuth2 callback URL.

Hope this helps! Let me know if there are any further questions or issues.
Note: I see hundreds of posts, notifications, and messages daily on this forum, so if I missed your reply, please message me to look at your reply.

@samliew


P.S.: Did you know, the concepts of about 70% of questions asked on this forum are already covered in the Make Academy. Investing some effort into it will save you lots of time and frustration using Make later!

1 Like

Hi

connecting google apps is a bit cumbersome. I recommend taking some time and trying it when you’re fresh and full of energy. Fortunately most apps are easier to connect to.

The help page you mentioned above lists all the necessary steps.

There is one thing that I do differently and that is to remain the app in the “testing” status. This will make it a lot easier. A published app has higher requirements since Google feels they need to secure it properly before they allow you to offer it to the public. But if you just want to read/edit your own emails and files, there is no need to publish it. Just remember to add the testing email addresses that are allowed to access the app.

There may be a drawback this method I would like to read from more experienced users about this.

Cheers

1 Like

Thank you everyone for your advice! I will try to implement what you said to see if I can fix the problem.