The error “Access blocked: n8n.cloud has not completed the Google verification process” occurs because the OAuth app used by n8n.cloud is in Google’s “Testing” mode, not fully verified. This is a Google security requirement. You have four solutions: (1) Add your email as a Test User (fastest – add your Google email in Google Cloud Console under OAuth consent screen > Test users), (2) Publish the app to Production (if you own the Google Cloud project, change status from Testing to Production), (3) Self-host n8n (use your own verified Google credentials), or (4) Wait for n8n to complete verification (they’re working on it). For most n8n.cloud users, Solution 1 is the quickest workaround: the app owner must add your email as a test user in their Google Cloud Console.
1. What Does This Error Mean? {#what-error-means}
When you see this error while trying to connect Google services (Drive, Docs, Sheets, Gmail, Calendar) in n8n.cloud:
“Access blocked: n8n.cloud has not completed the Google verification process. The app is currently being tested and can only be accessed by developer-approved testers.”
It means that the Google OAuth application used by n8n.cloud is still in Google’s “Testing” mode and hasn’t completed Google’s formal verification process .
The Error Message Breakdown
| Error Component | What It Means |
|---|---|
| Error 403: access_denied | Google rejected the authorization request |
| “App is currently being tested” | The OAuth app is in Testing mode, not Production |
| “Only accessible by developer-approved testers” | Only emails added to the Test Users list can use it |
What This Is NOT
| It is NOT… | Explanation |
|---|---|
| An n8n bug | This is Google’s security requirement |
| Your fault | You didn’t misconfigure anything |
| Permanent | There are workarounds |
2. Why This Happens – The Technical Explanation {#why-this-happens}
Google’s Security Requirements
Google requires all OAuth applications that access sensitive user data (like Google Drive, Docs, or Gmail) to complete a verification process. Until verification is complete, the app remains in “Testing” mode and can only be used by explicitly approved test users .
The n8n.cloud Situation
n8n.cloud uses its own Google OAuth application to provide Google integrations to all users. This application is still in the testing and verification process with Google. As a result:
The Two Paths to Fixing This
| Path | Responsible Party | Effort |
|---|---|---|
| Add you as a test user | n8n or app owner | Low (you just ask) |
| Verify/publish the app | n8n (their Google Cloud project) | Ongoing (n8n is working on it) |
3. Solution 1: Add Your Email as a Test User (Fastest) {#solution-test-user}
This is the quickest workaround if you’re using n8n.cloud with their default Google credentials .
Who Can Do This?
| Scenario | Can You Add Test User? |
|---|---|
| You are the n8n workspace owner and have access to n8n’s Google Cloud project | ✅ Yes |
| You’re just a user on someone else’s workspace | ❌ No – contact the workspace admin |
| You’re using n8n.cloud as an individual with no custom credentials | ❌ No – you can’t access their Google Cloud project |
If You Have Access to the Google Cloud Project
Step-by-Step:
| Step | Action |
|---|---|
| 1 | Go to Google Cloud Console |
| 2 | Select the project that contains the n8n OAuth app |
| 3 | Navigate to APIs & Services → OAuth consent screen |
| 4 | Scroll down to the Test users section |
| 5 | Click Add Users |
| 6 | Enter the email address you use to sign in to n8n |
| 7 | Click Save |
After adding your email, wait 2-5 minutes for changes to propagate, then retry the OAuth connection in n8n.
If You Don’t Have Access
Your options:
- Contact your n8n workspace administrator and ask them to add your email
- Contact n8n support directly (they sometimes add test users on request)
- Move to Solution 3 (self-host) or Solution 4 (create your own credentials)
4. Solution 2: Publish the Google App to Production {#solution-publish}
If you own the Google Cloud project (either n8n’s team or you’re using your own custom credentials), changing the app status from “Testing” to “Production” resolves the issue permanently .
Steps to Publish
| Step | Action |
|---|---|
| 1 | Go to Google Cloud Console → APIs & Services → OAuth consent screen |
| 2 | Review your app information (name, logo, support email, privacy policy URL) |
| 3 | Ensure all required fields are complete |
| 4 | Click Publish App (or “Submit for Verification” if required) |
Important Note About Verification
“If your app accesses sensitive scopes (like Google Docs), Google may require a formal verification process including a video demonstration of your app’s functionality”
For many simple setups with limited scopes, Google may show: “Verification not required. Your consent screen is being shown, but your app has not been reviewed”
In this case, you can still publish without formal verification.
Why n8n Can’t Just Publish Immediately
Google’s verification process can take weeks or months for apps with broad user bases. n8n is actively working on completing this verification .
5. Solution 3: Self-Host n8n with Your Own Credentials {#solution-self-host}
This is the most reliable long-term solution if you need guaranteed Google access and have the technical resources.
Why Self-Hosting Works
When you self-host n8n, you create your own Google Cloud Project and OAuth credentials. You control the verification status. And you can:
- Add yourself as a test user immediately
- Publish your app (even without full verification for personal use)
- Never worry about n8n’s verification timeline
Requirements
| Requirement | Details |
|---|---|
| Technical skill | Basic server/docker knowledge |
| Hosting | Any VPS (DigitalOcean, Linode, AWS) or local server |
| Google Cloud Project | Free to create |
| n8n instance | Self-hosted (free, open-source) |
Quick Self-Host Setup
bash
# Docker command (simplest) docker run -d --name n8n \ -p 5678:5678 \ -v n8n_data:/home/node/.n8n \ -e N8N_SECURE_COOKIE=false \ n8nio/n8n # Access at http://localhost:5678
Then follow the steps in Section 7 to create your own Google OAuth credentials.
Cost Comparison
| Option | Monthly Cost | Control Over Google Access |
|---|---|---|
| n8n.cloud | $20-50+ | None (wait for n8n) |
| Self-host (VPS) | $5-15 (DigitalOcean) | Full control |
6. Solution 4: Contact n8n Support {#solution-support}
If you’re an n8n.cloud customer and need immediate access, contacting support may help .
What to Include in Your Request
| Information | Example |
|---|---|
| Your n8n workspace ID | Found in workspace settings |
| Your email address | The Google account you’re trying to connect |
| Which Google service | Drive, Docs, Sheets, Gmail, Calendar |
| Error screenshot | Attach if possible |
Contact Methods
| Method | Details |
|---|---|
| support@n8n.io | |
| Community forum | community.n8n.io |
| In-app chat | Available on paid plans |
Response Time Expectations
| Plan | Expected Response |
|---|---|
| Free tier | Community support only (slower) |
| Paid plans | 24-48 hours for initial response |
Note: Support may not be able to add you as a test user immediately – this depends on their current verification status with Google .
7. Step-by-Step: Creating Your Own Google OAuth Credentials {#create-credentials}
If you choose Solution 3 (self-host n8n) or want to use custom credentials with n8n.cloud, follow these steps.
Prerequisites
- A Google Cloud Platform account (free)
- A self-hosted n8n instance OR n8n.cloud account
- Your n8n instance URL (e.g.,
https://your-n8n-domain.com)
Step 1: Create a Google Cloud Project
| Action | Details |
|---|---|
| 1 | Go to Google Cloud Console |
| 2 | Click the project dropdown (top bar) |
| 3 | Click New Project |
| 4 | Name your project (e.g., “n8n-google-integration”) |
| 5 | Click Create |
Step 2: Enable Required APIs
| Action | Details |
|---|---|
| 1 | Navigate to APIs & Services → Library |
| 2 | Search for and enable the APIs you need: |
| – Google Drive API | |
| – Google Docs API | |
| – Google Sheets API | |
| – Gmail API (if needed) |
Step 3: Configure OAuth Consent Screen
Step 4: Create OAuth 2.0 Credentials
| Action | Details |
|---|---|
| 1 | Navigate to APIs & Services → Credentials |
| 2 | Click + Create Credentials → OAuth Client ID |
| 3 | Application type: Web application |
| 4 | Name: “n8n OAuth Client” |
| 5 | Authorized redirect URIs: Add your n8n callback URL |
Callback URLs by n8n Type
| n8n Type | Redirect URI |
|---|---|
| Self-hosted | https://your-n8n-domain.com/rest/oauth2-credential/callback |
| Local development | http://localhost:5678/rest/oauth2-credential/callback |
| n8n.cloud | https://api.n8n.cloud/oauth2-credential/callback |
Step 5: Copy Client ID and Secret
| Action | Details |
|---|---|
| 1 | After creation, copy the Client ID and Client Secret |
| 2 | Store them securely |
Step 6: Add Credentials in n8n
| Action | Details |
|---|---|
| 1 | Open your n8n instance |
| 2 | Go to Credentials → + Add Credential |
| 3 | Search for your Google service (e.g., “Google Drive”) |
| 4 | Select OAuth2 as the authentication method |
| 5 | Paste your Client ID and Client Secret |
| 6 | Click Connect my account |
| 7 | Authorize the app in the Google popup |
| 8 | Save the credential |
8. Comparison Table: Solutions at a Glance {#comparison-table}
| Solution | Time to Fix | Technical Skill | Works for n8n.cloud? | Permanent Fix? |
|---|---|---|---|---|
| Add as Test User | 5 minutes | Low | ✅ Yes (if admin) | ⚠️ (7-day expiry) |
| Publish App | 10 minutes + possible verification delay | Medium | ❌ (n8n owns project) | ✅ Yes |
| Self-Host n8n | 1-2 hours | Medium-High | N/A (different platform) | ✅ Yes |
| Contact Support | Days-weeks | Low | ✅ Yes | ❌ (depends on n8n) |
| Create Custom Credentials | 30 minutes | Medium | ✅ Yes (n8n.cloud plus) | ✅ Yes |
Recommendation by User Type
| User Type | Recommended Solution |
|---|---|
| n8n.cloud user, workspace admin | Add your email as test user (immediate) |
| n8n.cloud user, not admin | Ask admin to add you, or contact support |
| Technical user, willing to self-host | Self-host n8n (full control) |
| n8n.cloud paid plan user | Create custom OAuth credentials |
| Anyone needing production reliability | Self-host OR custom credentials in n8n.cloud |
9. 7-Day Token Expiration Issue {#token-expiration}
Even after getting access via Test User mode, there’s another limitation: OAuth tokens expire every 7 days for apps in Testing mode .
What Happens Every 7 Days
| Event | Impact |
|---|---|
| Token expires | Your Google-connected workflows will fail |
| Need to re-authenticate | Manual reconnection required |
| No automated refresh | Must click “Reconnect” in n8n |
How to Fix the 7-Day Expiry
| Solution | How to Implement |
|---|---|
| Publish the app | Change OAuth consent screen status to “Production” |
| Use your own credentials | Create custom OAuth app (you control publishing) |
Why This Happens
“If your app remains in Testing mode with User type set to External, consent and tokens expire after seven days, requiring you to reconnect periodically. Setting the app to Production resolves this limitation.”
This is Google’s security policy – testing mode tokens are intentionally short-lived to encourage proper app verification.
10. Frequently Asked Questions {#faq}
What causes the “Access blocked: n8n.cloud has not completed Google verification” error?
The error occurs because the Google OAuth application used by n8n.cloud is still in Google’s “Testing” mode and hasn’t completed Google’s formal verification process. Google requires this verification for apps accessing sensitive user data (Drive, Docs, Gmail, etc.) .
How do I fix this error in n8n.cloud?
Four solutions: (1) Add your email as a test user in the Google Cloud Console (fastest), (2) Publish the app to Production if you own the project, (3) Self-host n8n with your own credentials, or (4) Contact n8n support to request access .
Can I use n8n with Google Drive without this error?
Yes – by self-hosting n8n and creating your own Google OAuth credentials, or by using custom OAuth credentials in n8n.cloud (paid plans). Both give you full control over the verification status .
Why doesn’t n8n just complete Google’s verification?
n8n is actively working on completing Google’s verification process. However, for apps with broad user bases, Google’s verification can take weeks or months. The process requires demonstrating how the app uses sensitive data and may require video recordings of the application in action .
What’s the difference between “Testing” and “Production” mode?
Testing mode limits the app to approved test users only and tokens expire after 7 days. Production mode allows any Google user to authorize the app and tokens don’t have the 7-day expiration .
Do I need Google verification for personal use?
Not necessarily. If you create your own Google Cloud project and only add yourself as a test user, you don’t need full verification. Google will show “Verification not required” – you can still use the app, though it may show an “unverified app” warning screen .
How long does Google’s verification take?
For simple apps, 3-7 days. For apps with sensitive scopes and large user bases, several weeks to months. The process requires submitting a video demonstration and detailed documentation of how user data is handled .
Can I use n8n with Google services for free without this error?
Yes – by self-hosting n8n (free) and creating your own Google Cloud project (free tier). You can add yourself as a test user and ignore the verification warning for personal use .
Will n8n.cloud ever complete Google verification?
Likely yes – n8n is actively working on the verification process. However, there’s no confirmed timeline. For production-critical workflows, self-hosting or custom credentials are more reliable .
I’m getting a 404 error during OAuth callback. What’s wrong?
This typically indicates your redirect URI is incorrect. For n8n.cloud, use https://api.n8n.cloud/oauth2-credential/callback. For self-hosted, use https://your-domain.com/rest/oauth2-credential/callback .
The Bottom Line
| Your Situation | Best Action |
|---|---|
| Need immediate access in n8n.cloud | Ask your workspace admin to add your email as a test user |
| You’re the n8n workspace admin | Add your email (and team emails) as test users in Google Cloud Console |
| Need long-term reliability | Self-host n8n OR create custom OAuth credentials in n8n.cloud |
| Just testing/learning | Use the test user workaround – tokens expire in 7 days but you can reconnect |
| Production workflows | Self-host n8n with published OAuth app (full control, no 7-day expiry) |
The most important takeaway: This is not an n8n bug – it’s Google’s security requirement. The workarounds are well-documented, and for production use, self-hosting or custom credentials give you complete control .
Action Steps for Today
- Identify your user type – are you an n8n.cloud user or self-hosting?
- If n8n.cloud user, contact your workspace admin to be added as a test user
- If you are the admin, follow Solution 1 to add your team’s emails
- For production needs, consider self-hosting n8n (Solution 3)
- Bookmark this guide – the 7-day expiry means you may need to reconnect periodically
Explore More on Coggnix.io
- Best AI Tool for Proposal Writing: 7 Tools Tested & Compared (2026 Guide)
Best Free AI Image Generator With No Restrictions: 7 Tools That Actually Work (2026) - Best Free AI Workflow Automation Tools: 8 Tools That Save Hours Every Day (2026)
- Best AI Video Generator Free No Sign Up No Limits
This article contains affiliate links. Coggnix.io may earn a commission if you purchase through these links, at no additional cost to you. We only recommend tools we have tested and believe deliver value.
Follow us one Facebook for more Educational Content
Last updated: May 2026
