Beginner
How to configure Gmail integration on Make
Quick Answer
Make supports simple Gmail OAuth via UI for most users, but custom GCP setup with Gmail API, OAuth screen, and Client ID/Secret is required for advanced or Workspace accounts. Common errors like 403 Access Denied fix by adding test users and correct URIs. Setup takes 5-15 minutes.
Prerequisites
- Google account (preferably @gmail.com)
- Make.com account with scenario permissions
- Access to Google Cloud Console
- Make OAuth redirect URI: https://www.make.com/oauth/cb/google-custom
1
Log in to Make and create scenario
Go to
make.com, sign in, navigate to Scenarios in the left sidebar, and click Create a new scenario (blue button top-right). This opens the scenario editor where you'll add Gmail modules.2
Add Gmail module
Click the
+ icon to add the first module. Search for and select Gmail. Choose a module like Watch emails (trigger) or Send an email (action). The setup panel opens on the right.Tip
Triggers like Watch emails poll for new emails; actions like Send an email require recipient details.
3
Create connection in Make
In the module's Connection field (top of right panel), click Add. Enter optional Connection name (e.g.,
My Gmail Production). Click Continue or Sign in with Google for standard OAuth.Tip
Reuse connections across scenarios via dropdown.
4
Set up Google Cloud Platform project
In Google Cloud Console, create a new project or select existing. Enable Gmail API under APIs & Services > Library. This is required for custom connections avoiding '403 Access Not Configured'.
Tip
Use @gmail.com accounts for fewer restrictions.
5
Configure OAuth consent screen
Go to APIs & Services > OAuth consent screen. Choose External, fill app details, and add Authorized redirect URIs:
https://www.make.com/oauth/cb/google-custom. Add your email as test user if in Testing mode. Save and continue.Tip
Publish to Production to skip weekly reauthorizations.
6
Generate and add OAuth credentials
In APIs & Services > Credentials, create OAuth 2.0 Client ID (Web application). Copy Client ID and Client Secret. In Make connection popup, select Custom, paste credentials, and authorize with Google account.
7
Authorize and confirm connection
Sign in on Google's OAuth screen, review permissions (e.g., 'See, edit, create, and delete all your Google Mail'), and click Allow. Ignore 'unverified app' warning for personal accounts. Make redirects back; verify connection in dropdown.
Tip
For Google Workspace, enable third-party access via admin.
8
Configure module fields
Fill fields: To (
recipient@example.com, comma-separated), Subject (Automated Update), Body type (HTML/Plain text), Body contents (Hello, this is a test.). Use ID finder (magnifying glass) for Message/Thread ID. Add optional signature or attachments.Tip
Map variables from prior modules; attachments as file URL array.
9
Test the connection
Click OK to save. Click Run once to test. For triggers, use Pull data or send test email. Check logs for errors like 'Invalid credentials'.
10
Save and activate scenario
Click Save (top-left), name the scenario, then toggle the activation switch on. Your Gmail integration is now live.
Tip
Monitor executions in the scenario history.
Troubleshooting
403 Access Denied
Add exact Google account email as Test user in GCP OAuth consent screen > Test users. Publish app to Production or wait for verification.
403 Access Not Configured
Enable Gmail API in GCP project: APIs & Services > Library > Search Gmail API > Enable.
Invalid credentials (Failure)
Verify Client ID/Secret, redirect URI (
https://www.make.com/oauth/cb/google-custom), and scopes. Reauthorize connection.400 failedPrecondition: Mail service not enabled
Use @gmail.com or @googlemail.com account; non-Gmail accounts often fail.
Unverified app warning
Safe for personal use; reauthorize weekly until published. Add test users.
Ready to get started with Make?
Put this tutorial into practice. Visit Make and follow the steps above.
Visit Make →