🚀 How I Gave My openclaw Assistant Access to Google Workspace (On Hostinger VPS)

The complete guide to integrating Gmail, Calendar, Drive, and Sheets with your self-hosted Openclaw assistant

Picture this: You're lying in bed at 11 PM, and you suddenly remember you need to check if you have any meetings tomorrow. Instead of reaching for your phone, opening Google Calendar, and squinting at the screen, you simply ask your openclaw Telegram bot:

That's the power of integrating Google Workspace with your self-hosted Openclaw assistant. And I'm going to show you exactly how I did it without spending a fortune or needing a computer science degree.

💡 The Challenge

How do you integrate Google Workspace with an Openclaw running in a Docker container on a headless Linux server,when all the official tutorials assume you have a graphical interface and macOS?

Official Installation: "Install via Homebrew: brew install steipete/tap/gogcli"

🎯 The Three-Part Strategy

1 Download the Linux Binary

First, I grabbed the official gogcli Linux binary from GitHub releases:

# Download latest Linux release
curl -L https://github.com/steipete/gogcli/releases/download/v0.11.0/gogcli_0.11.0_linux_amd64.tar.gz -o /tmp/gogcli.tar.gz

# Extract it
tar -xzf /tmp/gogcli.tar.gz -C /tmp/

# You now have the 'gog' binary

2 Install to Persistent Docker Volume

Here's the trick: Docker containers reset on restart. But Docker volumes persist. I placed the binary in OpenClaw's persistent config directory:

# Copy to persistent volume location
docker cp /tmp/gog openclaw-container:/home/node/.openclaw/gog

# Make it executable
docker exec openclaw-container chmod +x /home/node/.openclaw/gog
docker exec openclaw-container chown node:node /home/node/.openclaw/gog

# Create symlink so it's in PATH
docker exec openclaw-container ln -sf /home/node/.openclaw/gog /usr/local/bin/gog

# Test it works
docker exec openclaw-container gog --version
# Output: v0.11.0

3 Automate Symlink Creation

To make the binary permanently accessible after restarts, I added one line to my docker-compose.yml startup script:

command:
  - sh
  - -c
  - |
    # ... existing startup code ...
    chown -R node:node /home/node/.openclaw
    
    # ✨ This is the magic line
    [ -f /home/node/.openclaw/gog ] && ln -sf /home/node/.openclaw/gog /usr/local/bin/gog
    
    # ... rest of startup ...
    exec su node -s /bin/sh -c "node dist/index.js gateway"

Now, every time the container starts, it checks if the binary exists and creates the symlink automatically. No manual intervention needed.

4 Set Up Google OAuth (The Fun Part)

This is where it gets interesting. OAuth on a headless server? Most people think it's impossible because OAuth wants to redirect to localhost in your browser. But gog has a clever solution: the remote authentication flow.

4a. Create Google Cloud Project

1. Go to console.cloud.google.com
2. Create a new project (e.g., "My AI Assistant")
3. Go to APIs & Services → Credentials
4. Click "+ CREATE CREDENTIALS" → "OAuth client ID"
5. Application type: Desktop app
6. Name it: "OpenClaw Integration"
7. Download the client_secret.json file

4b. Enable the APIs

Go to APIs & Services → Library and enable:

• Gmail API
• Google Calendar API
• Google Drive API
• Google Sheets API
• Google Docs API
• People API (Contacts)

4c. Add Yourself as Test User

Go to OAuth consent screen → Test users → + ADD USERS and add your Gmail address. This lets you use the OAuth flow while the app is in "Testing" mode (which is fine for personal use).

5 The Remote OAuth Dance

This is the clever part. Since we're on a server with no browser, we use gog's remote authentication flow:

Step 5.1: Upload OAuth Credentials

# Copy your downloaded client_secret.json to the server
scp client_secret.json user@your-vps:/tmp/

# Copy into container
docker cp /tmp/client_secret.json openclaw-container:/home/node/.openclaw/

# Load credentials
docker exec openclaw-container su node -c "gog auth credentials /home/node/.openclaw/client_secret.json"

Step 5.2: Generate Auth URL

docker exec openclaw-container su node -c "gog auth add you@gmail.com --services gmail,calendar,drive,contacts,sheets,docs --remote --step 1"

# Output:
# auth_url    https://accounts.google.com/o/oauth2/auth?access_type=offline&client_id=...
# Run again with --remote --step 2 --auth-url <redirect-url>

Step 5.3: Authorize in Your Browser

1. Copy the auth_url from the output
2. Open it in your browser (on your laptop/phone)
3. Sign in with your Google account
4. Grant all the permissions
5. Your browser will redirect to http://127.0.0.1:xxxxx/... which will fail to load
6. That's OK! Copy the entire URL from your browser's address bar

Step 5.4: Complete Authentication

docker exec openclaw-container su node -c "gog auth add you@gmail.com --services gmail,calendar,drive,contacts,sheets,docs --remote --step 2 --auth-url 'PASTE_THE_FULL_URL_HERE'"

# Verify it worked
docker exec openclaw-container su node -c "gog auth list"

# Output:
# you@gmail.com    default    calendar,contacts,docs,drive,gmail,sheets    oauth

Real Examples I Use Every Day

💰 Complete Cost Summary

VPS Hosting: $4.5/month (shared with other services)
Google APIs: $0/month (completely free)
gogcli binary: $0 (open source)
OAuth authentication: $0 (Google provides for free)

Total additional cost to add Google Workspace: $0/month

⚡ You Can Revoke Access Anytime: Go to myaccount.google.com/permissions and remove "OpenClaw Integration" to instantly revoke all access. No data remains on the server.

1. Docker Volumes Are Your Friend

Anything in /home/node/.openclaw/ persists across restarts. Anything in /usr/local/bin/ or /tmp/ does not. Put important stuff in persistent volumes!

2. Symlinks Need Automation

Creating a symlink manually works once. But after docker compose down/up, it's gone. Add it to your startup script or you'll be recreating it every time.

3. Remote OAuth Flow is Brilliant

The --remote --step 1/2 flow is designed exactly for this use case. Don't try to hack localhost redirects or use port forwarding. Just use the remote flow.

4. Test Mode OAuth is Fine

You don't need to get your app "verified" by Google unless you're building for public use. Test mode works perfectly for personal/internal use with up to 100 test users.

• 📊 Automated expense tracking - Parse receipts from Gmail, add to Google Sheets
• 📅 Smart calendar assistant - "Find a time next week when both John and Sarah are free"
• 📧 Email triage - Automatically categorize and prioritize emails
• 💾 Document search - "Find all contracts modified in the last month"
• 🎯 Meeting prep - "What's my next meeting and what were the action items from last time?"

The dream of having a personal AI assistant isn't reserved for tech giants with million-dollar budgets anymore.

It's here. It's affordable. And you can build it yourself.

Want to Follow Along?

I'm documenting my entire AI assistant journey—from cost optimization to advanced integrations. If you're interested in building your own self-hosted AI assistant, check out my other posts:

Published on prodatanalytics.com | February 16, 2026

Built with OpenClaw • Hosted on Hostinger VPS • Powered by curiosity