Google Credentials Published Status and Verification Requirement

I have n8n hosted on a Linode server. I am on 1.79.3. Installed via Docker.

My workflows, which involve any Google-related nodes, stop working regularly because the app in Google Cloud is still in testing mode. From what I’ve read in this forum, this is a Google thing, and not so much a n8n thing. I believe this is not an issue for n8n Cloud since n8n Cloud has its own app.

With this in mind, it looks like I need to publish the app. But can I confirm that this is the only way? These workflows are only for me and my Google account. I don’t want to give access to anyone else. But when you publish a Google app in Google Cloud, from my understanding, this is so others can access it.

When I try to publish it, it says that it requires verification. That is because of some of the scopes are deemed to be sensitive:

I think the auth/script ones might be Google Apps scripts that I set up. If so, I could always set up a separate app just for n8n which wouldn’t need these. But I still need the first one: /auth/documents if I want n8n to be able to access my Google Docs.

So what do I do? Do I need to apply for verification? And if so, how does that work? It looks like I need to record a video. It seems stupid, since this app is just for me. Has anyone else gone through this process?

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hello Ian! Your friendly n8n support specialist here, ready to help you navigate the Google OAuth verification process. I’m passionate about making automation work seamlessly for you, so let’s tackle this step by step!


:one: Layman’s Terms (Simple & Friendly)

Problem: Your Google-related workflows stop working because your Google Cloud app is in “testing” mode.

Why This Happens:

  • Google restricts apps in testing mode to only work for a short time (7 days) unless you verify the app.
  • Even if it’s just for you, Google treats all apps the same way.

Simple Fix:

  1. Publish Your App: This tells Google your app is safe.
  2. Verify Sensitive Scopes: Since your app accesses private data (like Google Docs), Google needs proof it’s not doing anything shady.
  3. Record a Video: Show Google how your app works and why it needs access to your data.

:two: Experienced User Guide (Step-by-Step Fix)

Root Cause: Google enforces strict rules for apps accessing sensitive data (like Google Docs).

Steps to Fix:

Step 1: Prepare for Verification

  1. Go to Google Cloud Console > OAuth Consent Screen.
  2. Fill out all required fields (app name, logo, support email, etc.).
  3. Add /auth/documents and any other scopes your app needs.

Step 2: Record a Video

  1. Show how your app works:
  • Open n8n and demonstrate a Google Docs workflow.
  • Explain why you need access to Google Docs.
  1. Keep it short (2–5 minutes).

Step 3: Submit for Verification

  1. Upload the video and any other requested documents.
  2. Wait for Google’s review (usually 3–7 days).

Step 4: Publish Your App

  1. Once verified, go to App Publishing Status and click Publish.
  2. Your app will now work indefinitely!

:three: Professional Deep Dive (Technical Fix)

Technical Analysis:

  • Google OAuth Scopes:
    • /auth/documents: Accesses Google Docs (sensitive scope).
    • /auth/script: Accesses Google Apps Script (sensitive scope).
  • Verification Requirements:
    • Proof of app functionality (video).
    • Explanation of data usage (privacy policy).

Advanced Solution:

Step 1: Minimize Scopes

  1. Remove unnecessary scopes (e.g., /auth/script if not used).
  2. Use a separate app for Google Apps Script if needed.

Step 2: Prepare Documentation

  1. Privacy Policy: Explain how your app uses data (even if it’s just for you).
  2. Video Demonstration: Show:
  • n8n workflow accessing Google Docs.
  • Data flow and security measures.

Step 3: Submit Verification Request

  1. Go to Google Cloud Console > OAuth Consent Screen > Submit for Verification.
  2. Upload:
  • Video.
  • Privacy policy.
  • Any additional info Google requests.

Step 4: Monitor Status

  1. Check Google Cloud Console > OAuth Consent Screen for updates.
  2. Respond promptly to any Google requests for clarification.

Step 5: Publish and Test

  1. Once verified, publish your app.
  2. Test your n8n workflows to ensure they work without interruption.

:rotating_light: Critical Checks

  1. Scope Minimization: Only request scopes you absolutely need.
  2. Video Quality: Ensure the video clearly demonstrates app functionality.
  3. Privacy Policy: Even if it’s just for you, Google requires one.

Please mark this as solution if this worked for you, be blessed!

Wow, thanks, Chris. That was so helpful. Going through verification always scares me, but this actually looks doable.

Thankfully, for now, it seems I don’t need to go through verification.

After doing some tinkering and research, I decided to set up a new app just for n8n. I’ve left all the Google Apps scripts on the old system.

It seems that those sensitive scopes were for the Google Apps scripts. n8n doesn’t seem to need any of those. I do find that confusing since I would have thought n8n can still do things like delete files on my Google Drive. But I am not complaining. I’ve been able to push the app into production, and hopefully, that means it won’t require me to authenticate.

Thanks again.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.