Gmail module Send Emails stopped working, reauthorizing does not work

Getting Started
,
1

I established a connection between Make and my Gmail account, so I could send emails via the Gmail module Send Emails. After a couple of weeks it stopped working today, I got this message: Failed to verify connection ‘My Gmail Account’. Invalid refresh token. Please reauthorize the connection. I studied the documentation but cannot solve that. I tried to reauthorize all the connections in the Connections tab, still not working. Any help how can I reauthorize the connection?

2

Hello @Michal_Splho, you can delete the connection and create a new one that’s the best

3

Well, I did not find a way to delete the connection. I created new one instead of that, connecting to the same Gmail Account, but it did not work. I got the same error message.

4

Welcome to the Make community!

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.

    600×272 11.6 KB

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

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

Note: 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 insert both!

Note: You are also likely required to insert the legacy values below from the old Integromat system that might not have been migrated to Make yet (simply 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: 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!

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.

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

If you have any further questions, you can also repost in the Hire a Pro category if you find it easier to explain your problem over screenshare. There is only so much we can do for you on a text-based forum.

— @samliew

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

2 Likes
5

Thank you, it worked :slight_smile:

1 Like