Our verdict
For most small teams the decision is simple. Use Make's Version 4 Gmail app and sign in with Google. Make says this app does not need a Google Cloud project for personal Gmail accounts. [2] Version 4 is now the default Gmail app. [1]
Build your own OAuth client only when you have a reason, such as keeping legacy Gmail modules running on a personal account, which Make says requires a custom OAuth client for @gmail and @googlemail addresses. [5] In the current app, your own client credentials are an optional Advanced setting. [1] If you do use your own client, publish it to In production so it does not expire every week. [3] [4]
Decision flow
Find your row, then follow the connection method and expect the reauthorization cycle shown.
| Your situation | How to connect | Expect to reauthorize |
|---|---|---|
| Personal @gmail.com, new scenario | Gmail app V4, Sign in with Google [2] | Every 6 months; Google limits access for personal accounts [1] |
| Personal @gmail.com, old scenario on legacy modules | Legacy modules need your own OAuth client for @gmail and @googlemail [5]; consider replacing them with V4 modules | Every 7 days while your client is in Testing [3] [4]; publishing it to In production removes the weekly reauthorization [3] |
| Google Workspace address | Gmail app V4, Sign in with Google; your own client credentials are optional [1] | Make says the 7-day expiry error affects non-Workspace accounts [4] |
| Any account, own OAuth client in Testing | Advanced settings with your Client ID and secret [3] | Every week [3] [9] |
| Any account, own OAuth client In production | Same, after publishing the app [9] | No weekly reauthorization [3] |
Setting up your own OAuth client, if you need one
Make's Gmail project guide lists the steps. You need the serviceusage.services.enable permission in Google Cloud, or someone who can grant it. [3]
- Create a Google Cloud project and enable the Gmail API under APIs and Services, Library. [3]
- Configure the OAuth consent screen with the app name Make, your Gmail address and the External audience. [3]
- Add the authorized domains make.com and integromat.com. [3]
- Add the scopes gmail.modify, gmail.readonly, gmail.compose and gmail.send. [3]
- Create a Web application OAuth client with the Google email redirect URI that Make's connection guide lists (copy it exactly from that page) and keep the Client ID and Client secret. [3]
- In Make, add a Gmail module, open Advanced settings, paste both values and sign in with Google. [3]
- Publish the app to In production. If Google shows Needs verification, you can go through verification or connect to the unverified app. Make warns it cannot guarantee Google will allow unverified apps indefinitely. [3] [9]
Errors you are likely to see
Three errors cover most failed Gmail connections. [4]
| Error | Cause | Fix |
|---|---|---|
| 400 Failed to verify a connection | The token expired: 7 days for an unpublished app on a non-Workspace account [4] | Publish the app to In production, or reauthorize weekly [4] |
| 403 Access denied | The project is in Testing and the account is not a test user [4] | Add the address under Test users and save [4] |
| 403 Access not configured | The Gmail API is disabled in the project [4] | Enable the Gmail API again [4] |
| Restricted scopes with @gmail.com accounts | Usually the required scopes were not added to the project [9] | Add the scopes on the Data Access screen [9] |
Gmail sending limits apply to your scenario
Make does not raise Google's limits. For a personal account, Google says the You have reached a limit for sending mail error can appear when you send more than 500 emails in a day or an email to more than 500 recipients, and you should be able to send again within 1 to 24 hours. [7]
Workspace limits are higher but still finite, and they are measured over a rolling 24 hours. Users who exceed one cannot send new messages for up to 24 hours, though they can still receive mail. [8]
| Limit | Personal Gmail | Google Workspace |
|---|---|---|
| Messages per day | More than 500 can trigger the limit [7] | 2,000 per user; 500 on trial accounts [8] |
| Recipients per message | More than 500 can trigger the limit [7] | 2,000 total, at most 500 external; 500 via the Gmail API [8] |
| External recipients per day | Not stated separately | 3,000 [8] |
| Unique recipients per day | Not stated separately | 3,000 total, 2,000 external [8] |
| Recovery time | 1 to 24 hours [7] | Up to 24 hours [8] |
Practical rules for Gmail in scenarios
Gmail is a good fit for notifications to yourself, replies to individual customers and small internal alerts. It is a poor fit for newsletters or anything that may grow past a few hundred messages a day, because hitting a limit stops all sending from that mailbox for up to a day. [7] [8]
- Put a calendar reminder 5 months after connecting a personal account so the 6-month expiry does not surprise you. [1]
- Watch emails and Search emails accept a Limit of up to 500 per run. [6]
- Use a separate mailbox for automated sending so a limit does not block your own email.
- Send bulk email through an email service, not Gmail.
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
Do I need a Google Cloud project to use Gmail in Make?
Not with the Version 4 Gmail app on a personal account; Make says it does not require a Google Cloud project or OAuth credentials for personal Gmail accounts. The legacy Gmail modules did require one for @gmail and @googlemail addresses.
Why does my Gmail connection in Make stop working every week?
Your own OAuth client is probably still in Testing status. Google limits unpublished apps to a 7-day authorization period. Publish the app to In production, or reauthorize the connection every week.
How many emails can a Make scenario send through Gmail?
Google's limits apply, not Make's. A personal account can hit a limit at more than 500 emails a day or more than 500 recipients in one email. A Workspace user can send 2,000 messages a day, or 500 during a trial.
What does Error 403 access denied mean when connecting Gmail?
Make says it happens when your Google Cloud project is in Testing status and the account you are connecting is not listed as a test user. Add the address under Test users on the OAuth consent screen.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make Apps: Gmail Accessed 30 Oct 2026
- Make Help: New Gmail app is now available Accessed 30 Oct 2026
- Make Apps: Create and configure a Google Cloud Platform project for Gmail Accessed 30 Oct 2026
- Make Apps: Gmail troubleshooting Accessed 30 Oct 2026
- Make Apps: Gmail (Legacy) Accessed 30 Oct 2026
- Make Apps: Gmail modules Accessed 30 Oct 2026
- Gmail Help: Sending limits Accessed 30 Oct 2026
- Google Workspace Admin Help: Gmail sending limits in Google Workspace Accessed 30 Oct 2026
- Make Help: Connect to Google services using a custom OAuth client Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.