How to Call Google APIs in Make.com with HTTP OAuth 2.0

This guide explains how to connect Google services to make.com and call Google APIs using the HTTP > Make an OAuth 2.0 request module. You will learn how to configure the connection, set up scopes, and build secure automations step by step.

What You Need Before Connecting Google to Make.com

Before you start, prepare the following items so that you can configure the HTTP OAuth 2.0 module smoothly inside make.com.

A Google account with access to the Google service you want to use
A Google Cloud project where you can create OAuth 2.0 credentials
Client ID and Client Secret from the Google Cloud Console
The exact API endpoint and method you intend to call
The required OAuth 2.0 scopes for the specific Google API

Having these pieces ready will make the connection between Google and make.com fast and reliable.

Set Up OAuth Credentials for Make.com in Google Cloud

To let make.com authenticate against Google APIs, you must configure OAuth 2.0 credentials in the Google Cloud Console.

Sign in to Google Cloud Console and open your project.
Go to APIs & Services > Credentials.
Click Create Credentials and choose OAuth client ID.
Select Web application as the application type.
Enter a recognizable name such as Make.com Google API OAuth.
Add the authorized redirect URI shown in the HTTP > Make an OAuth 2.0 request module in make.com. Copy it exactly.
Save and copy the Client ID and Client Secret for later use in make.com.

The redirect URI must match what make.com provides. Any mismatch will cause the OAuth flow to fail.

Configure the HTTP OAuth 2.0 Module in Make.com

Once you have the OAuth credentials, configure the HTTP > Make an OAuth 2.0 request module in your scenario inside make.com.

Create the HTTP OAuth 2.0 Module in Make.com

Open your scenario in make.com and click the plus icon to add a module.
Select HTTP from the list of apps.
Choose the Make an OAuth 2.0 request action.
Click Add to create a new connection so that make.com can authorize to Google.

This module lets you call any supported Google REST endpoint while handling OAuth 2.0 automatically.

Enter Google OAuth 2.0 Details in Make.com

In the connection configuration window, fill in the required Google OAuth 2.0 fields that make.com needs.

Authorization URL: The Google OAuth 2.0 authorization endpoint (for example, https://accounts.google.com/o/oauth2/v2/auth).
Token URL: The Google OAuth 2.0 token endpoint (for example, https://oauth2.googleapis.com/token).
Client ID: Paste the Client ID from your Google Cloud project.
Client Secret: Paste the Client Secret from your Google Cloud project.
Scope: Enter the scopes required by the Google API you are calling.
Redirect URL: Use the redirect URL supplied in the make.com connection dialog. This should already match what you set in Google Cloud.

After saving, make.com will redirect you to Google so you can grant access to the chosen scopes.

Choose the Correct Google API Scopes for Make.com

Scopes determine which Google resources make.com can access on your behalf. Use only the minimum scopes necessary for security and compliance.

Read-only scopes: Use these when you just need to list or retrieve data.
Read-write scopes: Required for creating, updating, or deleting resources.
Service-specific scopes: For example, Gmail, Google Drive, Calendar, or Sheets each have their own scope set.

Consult the official Google API documentation for the exact scope strings. Enter them in the Scope field in the make.com connection, separated by spaces if you need multiple scopes.

Build a Google API Request in Make.com

With the OAuth 2.0 connection in place, you can define the actual HTTP request that make.com will send to Google.

Set the HTTP Method and URL

Open the HTTP > Make an OAuth 2.0 request module in your scenario.
Choose the Method that matches the Google API documentation (GET, POST, PUT, PATCH, DELETE).
Enter the URL of the specific Google endpoint, including any required path parameters.

Make sure the URL matches the version and base path required by the Google API you are using.

Configure Headers and Query Parameters in Make.com

The module automatically applies the Authorization header using the OAuth token, so you do not need to set it manually. However, you may need other headers or query parameters.

Content-Type: Often set to application/json for POST or PATCH requests.
Accept: Usually application/json to receive JSON output.
Query parameters: For filtering, pagination, or additional options as defined in the Google API reference.

Use the interface in make.com to add each header and query parameter separately so that requests remain structured and easy to maintain.

Send Request Body Data from Make.com

For POST, PUT, or PATCH methods, configure the request body according to the Google API specification.

Select the Body type (for example, Raw for JSON or Form for x-www-form-urlencoded).
If using JSON, enter a valid JSON object in the Body field.
Map variables from previous modules in your make.com scenario into the body using the mapping panel.
Verify that required properties match the field names and data types expected by the Google API.

Valid request bodies are essential for avoiding 4xx errors when make.com communicates with Google.

Test and Troubleshoot Google Calls from Make.com

After configuration, always test the HTTP OAuth 2.0 module within make.com to confirm that it interacts correctly with Google APIs.

Run a Scenario Test in Make.com

Click Run once in your scenario editor.
Trigger the scenario input (for example, a webhook or scheduled run).
Inspect the output bundle from the HTTP OAuth 2.0 module.
Check the Status code, Headers, and Body returned from the Google API.

A successful status code (such as 200 or 201) indicates that make.com has connected and authenticated properly.

Common Error Patterns When Using Make.com with Google

401 Unauthorized: Usually caused by invalid or expired tokens or misconfigured OAuth credentials. Reconnect the account in make.com and confirm the Client ID, Client Secret, and redirect URI.
403 Forbidden: Often indicates missing permissions or insufficient scopes. Update the scopes in the connection and reauthorize Google access for make.com.
400 Bad Request: Typically caused by invalid query parameters or request body fields. Double-check your JSON structure and parameter names.
404 Not Found: The endpoint URL may be incorrect, or the resource does not exist. Compare the URL with Google API documentation.

If an error response includes an error message from Google, use it to adjust the configuration inside make.com accordingly.

Best Practices for Secure Google Integrations in Make.com

To keep your automations robust and secure, follow these practices when you work with Google APIs in make.com.

Limit OAuth scopes to the minimum your workflow requires.
Use separate connections in make.com for production and testing environments.
Document which scenarios depend on each Google connection.
Monitor quota usage in the Google Cloud Console to prevent unexpected limits.
Handle errors gracefully using routers and error handlers in make.com scenarios.

These habits help you maintain reliable operations even as your make.com automations grow more complex.

Additional Resources for Make.com and Google APIs

For deeper reference on this topic, review the official documentation and support resources.

By following the steps in this tutorial, you can reliably call Google APIs from make.com, automate complex workflows, and integrate Google services into your broader automation ecosystem.

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

How to use Make.com with Google APIs