Google connections keep asking for verification

Beginner Questions
,
1

Since last week, Google keeps asking me to verify. Before it was once a week, and now it’s once every few days. Also, I can’t seem to get my connections verified. I think to be able to not have to approve on your connection every week, you need to publish your app. But once I publish my app, at the end it asks me for some sort of YouTube video in which I show how to handle permissions or something. And obviously I think for the use case that I’m using Make for with a Google connection that’s not relevant.

Are there other people who actually verify their application using a free Google account, and if so, how did you manage to verify? It seems that they ask a lot of questions which are not relevant to this specific connection. I’ve already set all settings in the Google Cloud console, I also established a My HTTP OAuth 2.0 connection and and added lots of redirect URLs.

I’ve seen a lot of articles about this in the community, but I couldn’t quite figure out even with those articles what is the way to go here.

Google Drive connection requires verification?
3

No, you do not need to verify your app. All it needs is to be published.

4

You are right. I completely overlooked the option to go to the advanced settings and just continue without verifying.

image
image809×609 28.6 KB

5

That’s also correct. See the full instructions below.

How to Connect and Use Google APIs in Make!

0. Prerequisites

1. Enable Google APIs

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

    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:

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

— @samliew

6

The instruction was clear. I just overlooked the screen with the big X where you could just click on. Thanks for your help!