Google Connection in Make or n8n Expires After 7 Days: Testing Mode Explained
Short answer: When you connect Make or n8n to Google using your own OAuth client, that client belongs to a Google Cloud project with a consent screen. If the consent screen's user type is External and its publishing status is Testing, Google issues refresh tokens that expire after seven days, so the connection breaks every week. Fix it by switching the user type to Internal if you are on Google Workspace and only your organisation uses it, or by publishing the app to production. For Sheets and Drive jobs that do not need to act as a person, a service account avoids user tokens altogether.
Why the connection dies on day seven
In Google's OAuth model, your automation tool gets two things when you click "Sign in with Google": a short-lived access token and a longer-lived refresh token it uses to get new access tokens. Google's OAuth 2.0 overview states that a project with an external user type and a publishing status of Testing receives refresh tokens that expire in seven days.
So the symptom is very regular: the scenario or workflow runs fine for a week, then fails with an error such as invalid_grant, "Token has been expired or revoked", or a prompt to reauthorise the connection. Reconnecting fixes it for another seven days.
This mostly affects people who created their own client ID, which is common when:
- You self-host n8n, which needs your own Google credentials.
- Make asked you to supply a custom OAuth client for Gmail or Google Drive, for example when connecting a personal Gmail account.
- A developer set up the project quickly in testing mode and never came back to it.
Find your project's settings
- Open the Google Cloud console with the account that created the OAuth client.
- Select the project whose client ID you pasted into Make or n8n. If you are not sure, compare client IDs under APIs and Services, then Credentials.
- Open the OAuth consent screen section, which Google now groups under Google Auth Platform with Branding, Audience and Clients pages.
- Note two things: the user type (Internal or External) and the publishing status (Testing or In production).
Fix 1: Use Internal user type (Workspace only)
If you use Google Workspace and everyone who will connect belongs to the same organisation, set the user type to Internal. Internal apps:
- Are available only to accounts in your Workspace organisation
- Do not need Google's app verification
- Are not subject to the seven-day testing expiry
This is the cleanest fix for a business automating its own Workspace Gmail, Sheets or Calendar. It is not available for personal Gmail accounts.
Fix 2: Publish the app to production
For personal Gmail accounts, or if people outside your organisation must connect, switch the publishing status from Testing to In production on the Audience page.
What happens next depends on the scopes you request:
| Scope type | Examples | What publishing means |
|---|---|---|
| Non-sensitive | Basic profile, email address | Can usually publish without review |
| Sensitive | Some Calendar or Sheets access | Verification review if you want to remove warnings |
| Restricted | Full Gmail read access, full Drive | Stricter verification, possibly a security assessment |
You can publish without completing verification. Users then see a "Google hasn't verified this app" warning when connecting, and must choose Advanced and continue to proceed. For an internal automation used by you and a few colleagues, that is often acceptable, and tokens then last until revoked or unused for a long period. Google limits how many users an unverified app can have, so this route suits small internal use, not a public product.
When answering any verification questions, describe honestly what the app does and why it needs each scope. Request only the scopes your automation actually uses; asking for full Gmail access when you only send mail invites a harder review.
Fix 3: Use a service account for Sheets and Drive
A service account is a robot identity belonging to your Cloud project. It does not use the consent screen at all, so no weekly expiry. Google's service account guide covers creating one and its key.
How it works in practice:
- Create a service account in the project and generate a JSON key.
- Add the key in Make or n8n where the Google module offers a service account option.
- Share the specific spreadsheet or Drive folder with the service account's email address, like you would share with a colleague.
Limits to know:
- It can only see files shared with it.
- It cannot read a personal Gmail inbox. For Gmail on Workspace, an administrator can set up domain-wide delegation, which is powerful and should be restricted to the minimum scopes.
- Store the key file safely, as you would a password. Never paste it into shared documents.
Fix 4: Use the platform's own verified connection
Some automation platforms offer their own verified Google app for certain services. If yours does, and your security policy allows it, connecting through it avoids managing a Cloud project at all. Check your platform's documentation for which Google services and account types this covers.
After fixing: reconnect once
Changing the publishing status does not repair existing tokens. Delete or reauthorise the connection in Make or n8n, sign in again, and run the scenario. Then put a reminder in your calendar for eight days later to confirm it is still connected.
FAQ
Why did it work for exactly one week?
Your OAuth app is in Testing with an External user type. Refresh tokens from such apps expire after seven days.
Does publishing to production need Google's approval?
Not always. You can publish and accept the unverified app warning for small internal use. Verification is needed to remove warnings or exceed user limits.
Can a service account read Gmail?
Only on Google Workspace with domain-wide delegation configured by an admin. It cannot read personal Gmail.
Is Internal user type available for Gmail accounts?
No. It requires a Google Workspace organisation.
Weekly reconnecting is avoidable, and we are happy to set up the project and connections properly for you once.