Contents
- The Short Answer
- Whose App Is "Not Verified"?
- The 4 Causes at a Glance
- Cause 1: The App Is in Testing and You Are Not a Test User
- Cause 2: The OAuth Client Is in a Project You Do Not Control
- Cause 3: On n8n Cloud, You Did Not Need Your Own Client
- Cause 4: It Worked, Then Broke a Week Later
- Still Broken? Check These in Order
- How to Stop It Coming Back
- Sources
- FAQ
The Short Answer
You selected Sign in with Google on an n8n Google credential and Google answered with this screen:
Access blocked: n8n.cloud has not completed the Google verification process
Error 403: access_denied
Google adds that the app is being tested and is only accessible to testers approved by the developer. "The developer" is you. When you created an OAuth client in Google Cloud with the External audience, the n8n docs note that the app defaults to Testing mode, and only test users you add by hand can sign in.
The fix:
- In Google Cloud Console, select the project that owns the Client ID in your n8n credential.
- Open Google Auth Platform and go to Audience. Google moved Publishing status and Test users there in 2025. Older guides say APIs & Services > OAuth consent screen, which now redirects to the same place.
- Under Test users, select Add users and enter the exact Google account you sign in with.
- Back in n8n, open the credential and select Sign in with Google again.
That is the accepted answer in the main community thread and in an older one answered by the n8n team.
Whose App Is "Not Verified"?
Not n8n's. An n8n team member explains the error refers to the OAuth app registered in your Google Cloud project, whose redirect URL ends in n8n.cloud. In a 2025 thread another states "Our app is verified". Two wrong fixes come from misreading this:
- Asking n8n to add you as a tester. n8n cannot. Test users live in the Google Cloud project that owns the client, which is yours.
- Enabling the Google Drive API and stopping there. The node needs it (Docs, Sheets and Slides need the Drive API too), but in thread 83176 enabling it did not clear the block. Sign-in is not about which APIs are on.
The 4 Causes at a Glance
| Symptom | Cause | Fix | How to confirm |
|---|---|---|---|
| Blocked on the first sign-in | App in Testing, your account not a test user | Add the account under Audience, Test users | Audience shows Publishing status: Testing and your address is missing from the list |
| No Test users section you can edit | The Client ID belongs to someone else's Google Cloud project | Create your own project and OAuth client | The Client ID in n8n is not listed under Credentials in any project you own |
| Blocked on n8n Cloud for a common Google node | Custom OAuth2 used where Managed OAuth2 is available | Use Managed OAuth2 (Sign in with Google with no Google Cloud setup) | The node is on the Managed OAuth2 list below |
| Sign-in worked, then the credential fails about a week later | Testing-mode tokens for External apps expire after seven days | Publish the app, or use an Internal app on Workspace | Status is Testing and the break lines up with seven days after you connected |
If Google instead shows Error 400: redirect_uri_mismatch, the redirect URL in Google Cloud does not match the one n8n shows. That is a different problem, covered in our redirect_uri_mismatch guide.
Cause 1: The App Is in Testing and You Are Not a Test User
Google's documentation on app audience is direct: an app in the Testing publishing status is limited to up to 100 test users listed on the consent screen. Anyone not on that list is refused.
How to confirm it: open console.cloud.google.com/auth/audience with the right project selected. If Publishing status says Testing and the account you are signing in with is not under Test users, this is your cause.
The fix: add the account, then reconnect in n8n. Watch for these slips:
- The wrong Google account. If your browser holds several Google sessions, the sign-in popup may use a different one from the address you added. Pick the account explicitly in the popup.
- The wrong project. Check the project selector in the top bar before adding users.
- A second error after adding yourself. One user in the older thread got a new error after adding the test user, and deleting and recreating the n8n credential cleared it.
Test users then see an unverified app warning before the consent screen. That is expected.
Cause 2: The OAuth Client Is in a Project You Do Not Control
In one thread a user could not add test users because he was not the app developer. That happens when the Client ID and Secret in the credential came from someone else's project.
How to confirm it: in Google Cloud Console, go to Credentials in each project you own and look for the Client ID that is in your n8n credential. If it is not there, it is not yours.
The fix: create your own client, following the n8n Google OAuth2 docs:
- Create a project and enable the API for your node under APIs & Services > Library.
- Open APIs & Services > OAuth consent screen, select Get started, enter the app name and support email, and pick an Audience.
- Under Branding, add
n8n.cloudto Authorized domains on n8n Cloud, or your own domain if self-hosted. - Go to Credentials > + Create credentials > OAuth client ID, choose Web application, and paste the OAuth Redirect URL from the n8n credential into Authorized redirect URIs.
- Copy the Client ID and Client Secret into n8n, add yourself as a test user (Cause 1), and select Sign in with Google.
On a self-hosted server the OAuth Redirect URL should show your public HTTPS domain. If it shows localhost, fix that first: see the redirect URI guide.
Cause 3: On n8n Cloud, You Did Not Need Your Own Client
The n8n Google credentials page describes Managed OAuth2: sign in with Google directly on n8n, with no setup required in Google Cloud Console. It is available on n8n Cloud only, for these nodes:
Google Calendar, Google Calendar Trigger, Google Chat, Google Contacts,
Google Docs, Google Drive, Google Drive Trigger, Google Mail,
Google Mail Trigger, Google Sheets, Google Sheets Trigger,
Google Slides, Google Tasks, YouTube
The managed app is n8n's verified app, so there is no test user list to be missing from.
How to confirm it: you are on n8n Cloud, your node is in the list above, and your credential contains a Client ID and Secret you created yourself.
The fix: create a fresh credential for the node and use the managed sign-in. Nodes outside the list, such as Google Ads in one of the threads, still need a custom client, so Causes 1 and 2 apply to them. Self-hosted n8n has no managed option at all.
Cause 4: It Worked, Then Broke a Week Later
A test user gets in, but not for good. Google's OAuth documentation says an external-user-type project in Testing is issued refresh tokens that expire in seven days, unless the only scopes requested are name, email and profile. The n8n docs say the same, and that you then reconnect from the credential.
How to confirm it: the workflow ran for about a week after you connected, then the Google node started failing, and the app is still in Testing.
The fix, one of three:
- Publish the app. On the Audience page, select Publish app. Google's audience docs say an unverified app requesting sensitive or restricted scopes shows an unverified app warning and is capped at 100 new users over the project's lifetime. Usually acceptable for a small team.
- Use an Internal app. Internal limits sign-in to members of your Google Cloud organization, so it needs Google Workspace. The n8n docs suggest it for avoiding the unverified warning, with the credential created from the same account you authenticate.
- Use Managed OAuth2 on n8n Cloud, if your node supports it (Cause 3).
Google lists other reasons refresh tokens die, including revoked access, six months unused, and a password change on a token with Gmail scopes. For credential failures after sign-in, see Unable to sign without access token.
Still Broken? Check These in Order
- The project selector in Google Cloud shows the project that owns your Client ID.
- Audience shows the status you expect (Testing or In production).
- If Testing, the exact account you pick in the Google popup is under Test users.
- The APIs your node needs are enabled, including the Drive API for Docs, Sheets and Slides.
- Authorized domains under Branding includes
n8n.cloudor your domain. - The Client ID and Secret were pasted without extra spaces (the docs list
invalid_clientas the error when they do not match). - You deleted and recreated the n8n credential after changing anything in Google Cloud.
How to Stop It Coming Back
One Google Cloud project per n8n instance, owned by a shared account, not a personal one that leaves with the person.
Decide Testing versus published on day one. Testing is fine for a demo. Anything that must run unattended past a week needs a published app, an Internal app, or Managed OAuth2.
Build client workflows in the client's Google Cloud project. If the client ID lives in your project, the client depends on you for access, and you hit Cause 2 at handover.
Set an error workflow with the Error Trigger node, so an expired credential messages you instead of failing silently. See error handling.
For a Google build to practise on, see our n8n AI agent with Google Sheets tutorial, and for the platform overall, the n8n review. The n8n AI Agents course covers what comes after sign-in: giving an agent tools, memory, error handling and human fallback, and deploying and handing a workflow over to a client.
Sources
Checked against n8n's and Google's documentation and the n8n community forum on 17 November 2026.
- n8n docs: Google OAuth2 single service - setup steps, Testing mode, seven-day expiry, Managed OAuth2 node list, troubleshooting.
- n8n docs: Google credentials - Managed OAuth2 is Cloud only.
- Google: Using OAuth 2.0, refresh token expiration - seven-day tokens in Testing.
- Google Cloud Help: Manage app audience - 100 test users, publishing, unverified app cap.
- n8n community: thread 83176 - accepted answer, and the 2025 move to Audience.
- n8n community: thread 18638 - n8n team explanation of whose app it is.
- n8n community: thread 184037 - n8n team: "Our app is verified".
FAQ
- Why does the message say n8n.cloud when I created the app?
- n8n's team explain that the message refers to the OAuth app registered in your Google Cloud project, whose redirect URL is on n8n.cloud. It is your app, in Testing, not n8n's own app. n8n staff have confirmed their own Google app is verified.
- Where do I add test users in Google Cloud now?
- Open Google Auth Platform and go to Audience. Publishing status and Test users moved there in 2025. The old path, APIs & Services > OAuth consent screen, redirects to Google Auth Platform. Select Add users under Test users and enter the account you sign in with.
- Can n8n support add me as a test user?
- No. Test users belong to the Google Cloud project that owns the Client ID in your credential. Only someone who manages that project can add them. If that is not you, create your own project and OAuth client.
- Why does my Google credential stop working every seven days?
- Google issues refresh tokens that expire in seven days to External apps in Testing status. Publish the app, use an Internal app on Google Workspace, or on n8n Cloud use Managed OAuth2 for supported nodes.
- Do I need Google verification to publish my app?
- Not to publish it. Google says an unverified published app requesting sensitive or restricted scopes shows an unverified app warning and is capped at 100 new users over the project's lifetime. For a handful of internal users that is often fine. Wider use needs verification.
- Is Managed OAuth2 available on self-hosted n8n?
- No. The n8n docs say Managed OAuth2 is available for n8n Cloud users only, for 14 Google nodes. Self-hosted instances use a custom OAuth2 client from your own Google Cloud project.
If this resonated
Module 02 is the long version of this post.
Eval set, refusal pattern, kill switch. Build it in a weekend.
