How to connect Google Calendar to OpenClaw

The ClawHub skill teaches OpenClaw about Google Calendar, but the calls run through the ClawLink plugin and your connected account. Make sure Google Calendar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Reconnect Google Calendar from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Calendar tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Calendar call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

This is the single most common Google Calendar failure we see, and the cause is almost always the same: the agent sent Google Calendar API's own nested shape, \{"summary": "…", "start": \{"dateTime": "2026-01-16T13:00:00Z"\}, "end": \{"dateTime": "…"\}\}. That is exactly what Google's API reference documents, so a model reaching for its training data writes it — but this tool takes flat arguments, so start is ignored and the required start_datetime is genuinely absent. Retrying the same payload cannot fix it; we have seen a single agent replay it more than fifty times. The working form is start_datetime: "2026-01-16T13:00:00" with timezone set separately, and the duration expressed as event_duration_hour / event_duration_minutes rather than an end time.

Ask the agent to diagnose it:

Retry the event creation, but first show me the exact arguments you are going to send. start_datetime must look like 2026-01-16T13:00:00 with no Z and no offset, and put the zone in the timezone argument instead.

The tool exists, but not under the name the agent guessed. The real names read verb-last: it is googlecalendar_events_list, not list_events; googlecalendar_patch_event, not events_patch; and googlecalendar_calendar_list_get, not calendar_list_list. ClawLink returns a "Did you mean" suggestion with the closest matches on every miss, so tell the agent to read that line and retry with the suggested name rather than inventing another variant. Asking it to call clawlink_list_tools first is the reliable fix.

Ask the agent to diagnose it:

Run clawlink_list_tools for google-calendar and show me the exact tool names that came back. Then retry using the real name, not a guess.

Almost always the calendar id, not the connection. Calendar tools default to primary, which is the connected account's own calendar — so if your events live on a shared calendar, a work calendar, or a second account you shared into this one, the agent is reading an empty or unrelated calendar and reporting exactly what it found. Ask it to run googlecalendar_list_calendars first and show you the ids, then repeat the request naming the calendar you meant; the id is the calendar's email address, not its display name. This is also why sharing a calendar with a bot account is not enough on its own — the agent still has to be told to read it.

Ask the agent to diagnose it:

Run googlecalendar_list_calendars and show me every calendar id and its summary. Do not filter the list. Then re-run my request against the calendar id I pick.

The duration is split across two arguments and the minutes field only accepts 0-59. Anything an hour or longer goes in event_duration_hour, which accepts 0-24. A 90-minute meeting is event_duration_hour: 1 with event_duration_minutes: 30; a two-hour block is event_duration_hour: 2. If you omit both, the event is created 30 minutes long.

Ask the agent to diagnose it:

Create the event again using event_duration_hour for the whole hours and event_duration_minutes for the remainder only. Show me both values before you send it.

You asked for 2pm to 4pm and got 2pm to 2:30pm, with no error anywhere. googlecalendar_create_event has no end_datetime argument — duration is expressed only through event_duration_hour and event_duration_minutes, and an unrecognised end time is discarded rather than rejected. The event is created, the call reports success, and only the calendar shows the mistake. This is common enough that it is worth checking first whenever a created event has the right title and start time but the wrong length. Ask the agent to convert the end time into a duration and patch the event.

Ask the agent to diagnose it:

That event is the wrong length. googlecalendar_create_event has no end_datetime argument — convert my time range into event_duration_hour and event_duration_minutes, then patch the existing event and show me the arguments you send.

The Google grant behind this connection was withdrawn — either from myaccount.google.com/permissions, by an admin on a Workspace account, or by deleting the connection's access. Nothing on the ClawLink side can revive it and retrying the call will keep returning the same status. Reconnect Google Calendar from the dashboard, complete Google's consent screen in the same browser session, then start a fresh chat so OpenClaw picks up the working connection. A status of INITIALIZING instead means the consent flow was started but never finished.

Ask the agent to diagnose it:

Reconnect Google Calendar from the dashboard first, then run clawlink_list_integrations and show me the status you get back before retrying anything.

Try reconnecting Google Calendar and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect OpenClaw to Google Calendar: link your Google Calendar account once in the browser and OpenClaw can call the Google Calendar API through 44 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Calendar skill from ClawHub, then you click Connect in the dashboard to authorize Google Calendar. OpenClaw calls the tools from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Google Calendar in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Calendar working from chat.

Not with ClawLink. The guides that tell you to create a Cloud project, enable the Calendar API, configure a consent screen and download a credentials.json are describing the gog CLI route, where the OAuth client is yours. ClawLink uses a hosted connection instead: you click Connect, approve on Google's own consent screen, and the tools work from the next message. You still see and control the grant under Third-party apps and services in your Google account.

Because the calendar tools default to primary, the connected account's own calendar. If your events live on a shared, work, or secondary calendar, the agent is reading a different calendar and truthfully reporting that it found nothing — or returning events you did not ask about. Ask it to run googlecalendar_list_calendars, then repeat the request naming the calendar id you want; ids are email addresses, not display names. Sharing a calendar with the connected account makes it reachable but does not make it the default.

Use event_duration_hour for the hours and event_duration_minutes only for the remainder, because the minutes argument accepts 0-59 and rejects 60. A 90-minute event is event_duration_hour: 1 with event_duration_minutes: 30. Left unset, a new event is 30 minutes long.

The honest version: ClawLink asks Google for calendar and calendar.events access, which is enough to read, create, edit and delete events on the calendars that account can reach. That is real access and we would rather say so than call it narrower than it is. What it avoids is a standing credential — there is no client secret or token file sitting on your machine or server, the grant is listed under Third-party apps and services in your Google account, and one click at myaccount.google.com/permissions ends it. The agent also acts only when you ask, rather than polling. If that reach is more than you want on a personal calendar, connect a secondary Google account and share into it just the calendars the agent should see.

The ClawHub skill teaches OpenClaw about Google Calendar, but the calls run through the ClawLink plugin and your connected account. Make sure Google Calendar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.