OpenClaw + Gmail & Google Calendar

📧 What can OpenClaw do with Gmail?

Once connected, you talk to your agent the same way you'd ask a human assistant — no commands to memorize.

📅 What can OpenClaw do with Google Calendar?

OpenClaw can see your schedule, create events, find open slots, and send invites — like having a personal scheduler on call.

🔐 How to connect your Google account

OpenClaw uses OAuth 2.0 to connect to Google — the same secure login flow used by apps like Zoom and Slack. You authorize it once; OpenClaw never sees your password.

1. Go to Google Cloud Console

   Open console.cloud.google.com and sign in with your Google account. This is Google's developer portal — it's free to use.

2. Create a new project

   Click the project dropdown at the top → New Project → name it something like openclaw-integration → click Create.

3. Enable the Gmail and Calendar APIs

   In the left menu go to APIs & Services → Library. Search for and enable both:

   • Gmail API — for email access
   • Google Calendar API — for calendar access

   Click each one → Enable. Takes about 30 seconds each.

4. Create OAuth credentials

   Go to APIs & Services → Credentials → Create Credentials → OAuth client ID.

   • Application type: Desktop app
   • Name: anything you like (e.g. OpenClaw Desktop)
   • Click Create

   Google will show you a Client ID and Client Secret. Copy both — you'll need them in the next step.

5. Configure the OAuth consent screen

   Go to APIs & Services → OAuth consent screen. Set:

   • User type: External (even if it's just you)
   • App name: anything (e.g. My OpenClaw)
   • Support email: your email
   • Add your email as a Test user

   You don't need to publish the app — keeping it in test mode is fine for personal use.

6. Add credentials to openclaw.json

   Open your openclaw.json file and add the Google section:

   openclaw.json Copy

   {
     "integrations": {
       "google": {
         "enabled": true,
         "client_id": "YOUR_CLIENT_ID.apps.googleusercontent.com",
         "client_secret": "YOUR_CLIENT_SECRET",
         "scopes": [
           "https://www.googleapis.com/auth/gmail.modify",
           "https://www.googleapis.com/auth/calendar"
         ]
       }
     }
   }

   Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with the values from Step 4.

7. Authorize OpenClaw

   Restart OpenClaw. The first time it tries to access Gmail or Calendar, it will open a browser window asking you to sign in with Google and grant permission. Click Allow.

   OpenClaw saves a token locally so you only need to do this once. The token is stored on your machine — it never leaves your computer.

🔒 What permissions does OpenClaw request?

Google requires apps to declare exactly what they can access. Here's what each scope means in plain English.

💬 Example prompts to try

Once connected, just talk to OpenClaw naturally. Here are some prompts to get you started.

🔧 Common problems & fixes

• "Access blocked: This app hasn't been verified by Google" ▾

  This is normal for personal OAuth apps in test mode. Google shows this warning to protect users from unknown apps. Since this is your own app connecting to your own account, it's safe to continue.

  • Click Advanced on the warning screen
  • Click "Go to [your app name] (unsafe)"
  • This only appears the first time you authorize
• OpenClaw can read emails but can't send ▾

  The gmail.send scope is separate from gmail.modify. Add it to your scopes array in openclaw.json, then re-authorize:

  • Add "https://mail.google.com/" to the scopes array
  • Delete the saved token file (usually ~/.openclaw/google_token.json)
  • Restart OpenClaw and go through the auth flow again
• "Token has been expired or revoked" ▾

  Google OAuth tokens expire after 7 days if the app is in test mode (or if you revoke access from your Google account). To fix it:

  • Delete the token file at ~/.openclaw/google_token.json
  • Restart OpenClaw — it will prompt you to re-authorize
  • To avoid this, publish your OAuth app in Google Cloud Console (you don't need to submit it for review for personal use)
• Calendar events are showing in the wrong timezone ▾

  OpenClaw uses the timezone set in your openclaw.json config. Make sure it matches your Google Calendar timezone.

  • Add "timezone": "America/New_York" (or your timezone) to the google section of openclaw.json
  • Use IANA timezone names (e.g. Europe/London, Asia/Tokyo)
• "API has not been used in project" error ▾

  You created credentials but forgot to enable the API. Go back to Google Cloud Console → APIs & Services → Library and enable the Gmail API and/or Google Calendar API for your project. It can take a minute to propagate.

🔗 Related guides