OpenClaw VPC to Google Workspace Connection Error.
✅Solved
Hey everyone! 
I'm trying to connect my OpenClaw instance (running headless on a VPC) to Google Workspace (Gmail/Drive/Calendar) and hitting some walls with authentication.
My Setup:
• OS: Ubuntu Linux (VPC, Headless)
• Version: OpenClaw 2026.1.29
• Install Method: npm install -g openclaw
• Interface: Interacting via Telegram (using openclaw-telegram plugin).
The Goal:
I want to enable the google-workspace (or similar) skill so my agent can read emails and access Google Drive files. Since I'm headless, I need a way to authenticate without a local browser popup.
What I've Tried:
1. Manual OAuth: Created a GCP Project, got Client ID/Secret. Tried running a Python script with run_console(), but got blocked by Google's "App not verified" error (even with myself added as a Test User).
2. Antigravity: Tried to force the antigravity flow by editing openclaw.json (adding "provider": { "google": ... }), but this crashed the gateway with Unrecognized key: "provider".
The Question:
What is the canonical way to set up Google Auth on a headless server in v2026.1.29?
• Is there a CLI command to trigger the "Antigravity" URL generation?
• Is there a specific config key I should be using?
• Or should I just stick to App Passwords + IMAP if I only really need email?
Any pointers would be appreciated! Thanks.
I'm trying to connect my OpenClaw instance (running headless on a VPC) to Google Workspace (Gmail/Drive/Calendar) and hitting some walls with authentication.
My Setup:
• OS: Ubuntu Linux (VPC, Headless)
• Version: OpenClaw 2026.1.29
• Install Method: npm install -g openclaw
• Interface: Interacting via Telegram (using openclaw-telegram plugin).
The Goal:
I want to enable the google-workspace (or similar) skill so my agent can read emails and access Google Drive files. Since I'm headless, I need a way to authenticate without a local browser popup.
What I've Tried:
1. Manual OAuth: Created a GCP Project, got Client ID/Secret. Tried running a Python script with run_console(), but got blocked by Google's "App not verified" error (even with myself added as a Test User).
2. Antigravity: Tried to force the antigravity flow by editing openclaw.json (adding "provider": { "google": ... }), but this crashed the gateway with Unrecognized key: "provider".
The Question:
What is the canonical way to set up Google Auth on a headless server in v2026.1.29?
• Is there a CLI command to trigger the "Antigravity" URL generation?
• Is there a specific config key I should be using?
• Or should I just stick to App Passwords + IMAP if I only really need email?
Any pointers would be appreciated! Thanks.
Solution
[SOLVED] How to connect Google Workspace (Gmail/Calendar) on a Headless VPC
Context:
I'm running OpenClaw on a headless Linux VPS and wanted to connect it to my personal Gmail using the google-workspace skill. I hit two major walls:
1. "Access Blocked: App not verified" (Google 403 error).
2. Library Crashes: The Python script would crash with Warning: Scope has changed if I didn't grant every permission (e.g. if I wanted to allow Gmail but deny Drive).
The Solution:
1. Google Cloud Console Setup (The "Happy Path")
• Create a new Project.
• OAuth Consent Screen: Set to "External" (for personal Gmail).
• Test Users: You MUST add your exact email address here. • Tip: If you get "Ineligible Account", verify you typed the email exactly as it appears in your Google Account profile.
• Credentials: Create "OAuth Client ID" -> "Desktop App". Download the JSON.
2. The "Access Blocked" Fix
Even with "Test Users" set, Google kept blocking me.
• The Fix: Open the generated Auth URL in an Incognito/Private Window.
• This forces a fresh login and bypasses stale session cookies that might be flagging the "Unverified App" check.
• You will still see a warning, but you can click "Advanced" -> "Go to [App Name] (unsafe)" to proceed.
3. The Headless Script Modification (Crucial)
The default google-auth-oauthlib flow tries to launch a local browser (impossible on VPS) or crashes if you don't accept all scopes. We modified the auth script to:
1. Print the URL to the console (for manual copy-paste).
2. Relax Token Scope: Allow the script to continue even if the user denies some permissions (like Drive).
Outcome:
I now have a working token.pickle on my headless server. OpenClaw can read/send emails via the official API without needing a browser relay or third-party middleware.
Context:
I'm running OpenClaw on a headless Linux VPS and wanted to connect it to my personal Gmail using the google-workspace skill. I hit two major walls:
1. "Access Blocked: App not verified" (Google 403 error).
2. Library Crashes: The Python script would crash with Warning: Scope has changed if I didn't grant every permission (e.g. if I wanted to allow Gmail but deny Drive).
The Solution:
1. Google Cloud Console Setup (The "Happy Path")
• Create a new Project.
• OAuth Consent Screen: Set to "External" (for personal Gmail).
• Test Users: You MUST add your exact email address here. • Tip: If you get "Ineligible Account", verify you typed the email exactly as it appears in your Google Account profile.
• Credentials: Create "OAuth Client ID" -> "Desktop App". Download the JSON.
2. The "Access Blocked" Fix
Even with "Test Users" set, Google kept blocking me.
• The Fix: Open the generated Auth URL in an Incognito/Private Window.
• This forces a fresh login and bypasses stale session cookies that might be flagging the "Unverified App" check.
• You will still see a warning, but you can click "Advanced" -> "Go to [App Name] (unsafe)" to proceed.
3. The Headless Script Modification (Crucial)
The default google-auth-oauthlib flow tries to launch a local browser (impossible on VPS) or crashes if you don't accept all scopes. We modified the auth script to:
1. Print the URL to the console (for manual copy-paste).
2. Relax Token Scope: Allow the script to continue even if the user denies some permissions (like Drive).
Outcome:
I now have a working token.pickle on my headless server. OpenClaw can read/send emails via the official API without needing a browser relay or third-party middleware.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
