Error 400: redirect_uri_mismatch when connection to Gmail

Avril_xu · March 18, 2025, 10:34am

already follow main guide on how to set up a custom OAuth 2.0 custom app in Make.still can not work

samliew · March 18, 2025, 12:02pm

… and what are your redirect uris? How did you set them up?

You have not yet provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any error(s).

image457×216 17.3 KB

Click on this link.

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.

Avril_xu · March 19, 2025, 2:52am

Error 400: redirect_uri_mismatch

You can’t sign in to this application because it doesn’t comply with Google’s OAuth 2.0 policy.

If you are the developer of this application, please register a redirect URI in the Google Cloud Console.

Request details: redirect_uri=https://www.integromat.com/oauth/cb/google-restricted flowName=GeneralOAuthFlow
Related developer documentation

samliew · March 19, 2025, 3:09am

You have not yet provided sufficient information to demonstrate the problem. How did you set up the Google Cloud project?

Please provide screenshots of your redirect URIs in your custom Google Cloud project to show that you have inserted the above redirect_uri.

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.

Avril_xu · March 19, 2025, 3:26am

samliew · March 19, 2025, 3:37am

Your redirect URIs is not complete. You should have 24 entries.

How to Connect and Use Google APIs in Make

0. Prerequisites

0.1. You need to have a Google account

Make sure you can sign in to Google Cloud Console with this.
0.2. Create a Google Cloud Platform (GCP) project

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

1. Enable Google APIs

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

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

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:

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.

Avril_xu · March 19, 2025, 3:47am

why?

samliew · March 19, 2025, 3:56am

This is normal, as described in the section “Enter your credentials”.

For more information, see the Google Workspace Admin page in the Make Help Centre.

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.

Avril_xu · March 19, 2025, 4:03am

where can I do this “as described in the section “Enter your credentials”.”??

Avril_xu · March 19, 2025, 6:58am

HOW to do it ? thanks so much

already added before

samliew · March 19, 2025, 8:08am

Please read section 2b again.

Avril_xu · March 20, 2025, 2:55am

Already insert all the link

samliew · March 20, 2025, 3:49am

I said this is normal. Click the link to continue.

Avril_xu · March 21, 2025, 9:05am

Thank you very much, solved follow your Follow your method:grinning_face:

Topic		Replies	Views
Redirect uri mismatch error Getting Started error	6	2865	March 15, 2024
Help Needed: "redirect_uri_mismatch" Error for Gmail Integration How To connections , api , error	2	171	January 20, 2025
Gmail connection How To connections , api , google	8	114	February 17, 2025
Error coming while connecting with gmail Features connections , error	3	23	April 24, 2025
Problem with connecting to Google Drive Getting Started google-drive	5	109	February 12, 2025

Error 400: redirect_uri_mismatch when connection to Gmail

How to Connect and Use Google APIs in Make

0. Prerequisites

0.1. You need to have a Google account

0.2. Create a Google Cloud Platform (GCP) project

1. Enable Google APIs

1.1. Enable the relevant APIs that you want to use

2. OAuth Client

2a. Create “OAuth client ID” Credentials

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

Insert All Google Redirect URIs

Including These Google Redirect URIs

3. OAuth consent screen

3a. Insert Two Authorised Domains

3b. Add All Scopes

3c. Step through and go to dashboard

3d. Publish your GCP OAuth2 app

4. Create New Connection (HTTP, or respective Google module)

4a. Specific Google module (Sheets, Docs, Drive, Gmail, etc.)

4b. HTTP OAuth 2.0 Request module

Related topics