How to Connect Google Services to Make.com with a Custom OAuth Client

This guide explains how to connect Google services to make.com using your own custom OAuth client so you can build secure, compliant workflows that you fully control.

By using a custom OAuth client instead of the default connection, you can manage your own Google Cloud project, follow your organization’s security policies, and keep better oversight of which apps are connected to your Google account.

Why Use a Custom Google OAuth Client on Make.com

When you connect Google services to an automation platform, Google may display unverified app warnings or require additional review. Setting up a custom OAuth client within your own Google Cloud project helps address these issues and gives you more control.

Using a custom client with make.com provides several advantages:

Control which Google project and credentials are used.
Align with corporate security standards and policies.
Reduce untrusted app prompts during consent screens.
Clearly see and manage access in your Google account.

This approach is especially helpful for organizations that must comply with stricter guidelines or manage many users and automations.

Before You Start: Requirements for Make.com and Google

Before configuring a custom OAuth client for make.com, confirm you have:

A Google account with access to Google Cloud Console.
Permission to create and configure projects and OAuth consent screens.
Administrator or sufficient access rights to manage connections in your make.com scenarios.

You will also need to decide which Google APIs you plan to use, such as:

Google Drive API
Google Sheets API
Gmail API
Google Calendar API

This helps you enable the correct services in your Google Cloud project so that your connection works properly with make.com modules.

Step 1: Create a Google Cloud Project for Make.com

The first step is to create or select a Google Cloud project that will hold your OAuth credentials used by make.com.

Visit the Google Cloud Console and sign in with your Google account.
Open the project selector at the top of the console.
Create a new project or select an existing one dedicated to automations used by make.com.
Give the project a clear name (for example, “Automation OAuth for Make”).

Using a dedicated project will make it easier to track access, logs, and configuration related to your automation workflows.

Step 2: Configure the OAuth Consent Screen for Make.com

Next, set up the OAuth consent screen so Google can show users what access the connection will request when they use it through make.com.

In the Google Cloud Console, open the APIs & Services section.
Select OAuth consent screen.
Choose the appropriate user type (for example, Internal for corporate domains or External if needed).
Fill in application details such as:
- App name
- Support email
- Developer contact information
Specify the scopes your app will request. These should match the permissions required by the Google modules you plan to use on make.com.
Save and continue through the remaining steps. If you use sensitive or restricted scopes, you may need to follow Google’s verification process.

Make sure the consent screen reflects how the connection will be used by your workflows so users clearly understand what is being authorized.

Step 3: Create OAuth Client Credentials for Make.com

Now create the OAuth client ID and secret that make.com will use to authorize access to Google services.

In the same project, go to APIs & Services > Credentials.
Click Create credentials and select OAuth client ID.
Choose Web application as the application type (this is required for use with an external automation platform such as make.com).
Enter a name that clearly indicates its purpose, for example, “Make Web OAuth Client”.
Configure the Authorized redirect URIs. You must enter the redirect URL provided in the Google connection settings within make.com. This URL tells Google where to send users after they grant access.
Save your client. Copy the generated Client ID and Client secret and store them securely. You will use both in the connection configuration on make.com.

Do not share these credentials publicly. Treat them like passwords, as they allow applications to request access tokens on behalf of your app.

Step 4: Enable the Required Google APIs for Make.com

Your custom OAuth client will only work with APIs that are enabled in the Google Cloud project. Activate any Google services that your make.com scenarios will use.

In the Google Cloud Console, open APIs & Services > Library.
Search for each API that matches the modules you plan to use. Examples include:
- Google Drive API
- Google Sheets API
- Gmail API
- Google Calendar API
Open each API and click Enable.

If a required API is not enabled, your modules on make.com may return authorization or permission errors when you run your scenarios.

Step 5: Add the Custom OAuth Client in Make.com

After your Google Cloud project and OAuth client are ready, configure the connection inside the automation platform so your Google modules use the new credentials.

Sign in to your make.com account.
Open or create a scenario that uses a Google module, such as Google Drive or Google Sheets.
Click to add or edit a Google connection in the module configuration.
Choose the option to use a custom OAuth client (sometimes labeled as a custom app or custom OAuth settings).
Enter the Client ID and Client secret from your Google Cloud project.
Confirm that the redirect URI shown in make.com matches the one configured in the Google OAuth client. If it does not match, update the URI in Google Cloud accordingly.
Save the connection and follow the Google sign-in flow to grant access with the new custom OAuth client.

Once authorization is complete, the connection will appear in your list of available connections, and you can reuse it across multiple scenarios.

Troubleshooting Google OAuth Connections on Make.com

If you encounter issues while connecting Google services through your custom OAuth setup, review the following areas:

Redirect URI mismatch: Ensure the redirect URI registered in Google Cloud exactly matches the URI required by make.com.
Missing APIs: Verify that all relevant APIs are enabled in your Google Cloud project.
Scopes and consent: Confirm that the scopes requested by the modules are included in your OAuth consent screen configuration.
Verification requirements: If you use sensitive or restricted scopes, check whether Google requires app verification and follow the steps described in the Google Cloud Console.

You can also compare your configuration with Google’s official documentation or revisit the original guide from make.com support at this reference page.

Best Practices for Managing Make.com Google Integrations

To keep your automations reliable and secure over time, adopt these practices when working with Google connections and make.com:

Use a dedicated Google Cloud project for automation to simplify auditing and maintenance.
Regularly review authorized scopes and remove those you no longer need.
Rotate your client secret if you suspect it has been exposed.
Document your OAuth configuration so team members can reproduce or update it when needed.
Test changes in a non-production environment or with a separate project before rolling them out to critical workflows.

Following these guidelines helps prevent interruptions and maintains trust with users who authorize your automations.

Learn More About Automations Beyond Make.com

If you need strategic help planning or scaling automations around make.com, consider exploring expert resources such as Consultevo, which offers consulting and implementation services for complex integration projects.

For the most authoritative technical details about custom OAuth configuration with Google services, always refer to the Google Cloud documentation in combination with the dedicated help resources from make.com.

By carefully following the steps above, you can connect Google services to make.com using a custom OAuth client, maintain strong security controls, and build reliable, long-term automation workflows.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help

Connect Google to Make.com