How to Connect Google Calendar Maton API to OpenClaw

Go to console.cloud.google.com and sign in with your Google account. If you do not have a Google Cloud project, click 'Create Project' — name it 'OpenClaw Integrations' or similar. The project is free to create and you will use it only for API access. Once in your project, navigate to APIs & Services > Library. Search for 'Google Calendar API' and click Enable. This authorizes the project to make Calendar API requests. Next, go to APIs & Services > Credentials. Click 'Create Credentials' > 'Service Account'. Fill in a service account name like 'openclaw-calendar-bot'. Click 'Create and Continue'. For the role, select 'Project > Editor' or leave it blank — the relevant permissions come from calendar sharing, not project roles. Click 'Done'. You now have a service account with an email like `openclaw-calendar-bot@your-project-id.iam.gserviceaccount.com`. Note this email — you will use it in Step 3. Click on the service account, go to the 'Keys' tab, click 'Add Key' > 'Create new key' > JSON. Download the JSON file. This is your GOOGLE_SERVICE_ACCOUNT_KEY.

1# The downloaded JSON key file has this structure:
2{
3  "type": "service_account",
4  "project_id": "your-project-id",
5  "private_key_id": "key-id-here",
6  "private_key": "-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----\n",
7  "client_email": "openclaw-calendar-bot@your-project-id.iam.gserviceaccount.com",
8  "client_id": "...",
9  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
10  "token_uri": "https://oauth2.googleapis.com/token"
11}
12
13# Store this file at a secure path, e.g.:
14# ~/.openclaw/credentials/google-service-account.json

Google Calendar does not grant service accounts access to calendars automatically — you must explicitly share each calendar you want the integration to manage. This is a security feature: the service account can only see and modify calendars you deliberately share with it. Open Google Calendar at calendar.google.com. In the left sidebar, hover over the calendar you want OpenClaw to manage and click the three-dot menu. Select 'Settings and sharing'. Scroll to the 'Share with specific people or groups' section. Click 'Add people and groups'. Enter the service account email address from Step 1 (it ends in `.iam.gserviceaccount.com`). Set the permission level: 'Make changes to events' gives full read/write access to events on that calendar. Click 'Send'. The service account does not receive the calendar sharing invitation the way a human does — the sharing takes effect immediately. You can also find the Calendar ID in this settings page under 'Integrate calendar'. The Calendar ID typically looks like `calendar-name@group.calendar.google.com` or your Gmail address for the primary calendar.

1# Note your Calendar ID from the calendar settings page
2# It appears under 'Integrate calendar' > 'Calendar ID'
3# Examples:
4# Primary calendar: your-email@gmail.com
5# Team calendar: abc123xyz@group.calendar.google.com
6
7# Test that the service account can see the calendar via Maton:
8curl -X POST https://api.maton.app/v1/google-calendar/events/list \
9  -H "Content-Type: application/json" \
10  -d '{
11    "service_account_key": "PATH_OR_CONTENT_OF_YOUR_JSON_KEY",
12    "calendar_id": "YOUR_CALENDAR_ID",
13    "time_min": "2026-03-30T00:00:00Z",
14    "time_max": "2026-04-06T00:00:00Z"
15  }'

Open `~/.openclaw/config.yaml` and add the Google Calendar integration block. The service account key can be provided either as a file path to the downloaded JSON file or as the full JSON content inline in the config. Using a file path is recommended for security — it keeps the private key out of the main config file, which may be more broadly readable. The file path approach references the JSON file you saved in Step 1. The `calendar_id` field specifies the default Google Calendar for operations. You can override this per-workflow in the actions block if you manage multiple calendars. The `timezone` field ensures events are created in your local timezone rather than UTC by default. After saving the config and running `openclaw reload`, the integration will verify that the service account credentials are valid and can authenticate with Google's API through the Maton layer.

1# ~/.openclaw/config.yaml
2integrations:
3  google-calendar-maton:
4    service_account_key_path: "~/.openclaw/credentials/google-service-account.json"
5    # OR provide the JSON inline (less recommended):
6    # service_account_key: |
7    #   { "type": "service_account", "project_id": "...", ... }
8    calendar_id: "your-email@gmail.com"    # Default calendar to use
9    maton_endpoint: "https://api.maton.app/v1/google-calendar"
10    timezone: "America/New_York"           # Your local timezone
11    default_event_duration_minutes: 60    # Default event length when not specified

With authentication working, test the core calendar operations: listing upcoming events, creating a new event, and deleting an event. These form the building blocks for all calendar automation workflows. The Maton API layer accepts simplified JSON payloads compared to the raw Google Calendar API — you do not need to manage etags, sequence numbers, or the full event resource schema that Google's direct API requires. Maton handles those details, accepting straightforward create/read/update/delete requests. Test creating a calendar event first — this confirms write permissions are working. Then query events to verify the event appears. Finally, test deletion to confirm the full CRUD cycle is functional before building workflows on top of it.

1# Create a calendar event via Maton
2curl -X POST https://api.maton.app/v1/google-calendar/events/create \
3  -H "Content-Type: application/json" \
4  -d '{
5    "service_account_key_path": "~/.openclaw/credentials/google-service-account.json",
6    "calendar_id": "your-email@gmail.com",
7    "summary": "OpenClaw Test Event",
8    "description": "Testing OpenClaw Google Calendar integration via Maton",
9    "start": "2026-04-01T10:00:00",
10    "end": "2026-04-01T11:00:00",
11    "timezone": "America/New_York"
12  }'
13
14# List events in a date range
15curl -X POST https://api.maton.app/v1/google-calendar/events/list \
16  -H "Content-Type: application/json" \
17  -d '{
18    "service_account_key_path": "~/.openclaw/credentials/google-service-account.json",
19    "calendar_id": "your-email@gmail.com",
20    "time_min": "2026-04-01T00:00:00Z",
21    "time_max": "2026-04-07T00:00:00Z"
22  }'
23
24# Delete an event by ID
25curl -X POST https://api.maton.app/v1/google-calendar/events/delete \
26  -H "Content-Type: application/json" \
27  -d '{
28    "service_account_key_path": "~/.openclaw/credentials/google-service-account.json",
29    "calendar_id": "your-email@gmail.com",
30    "event_id": "EVENT_ID_FROM_LIST_RESPONSE"
31  }'

With the integration verified, configure OpenClaw workflows that use Google Calendar as a trigger source or action target. The most common patterns are: creating events in response to external triggers, querying the calendar to check availability before scheduling, and updating events in batch operations. The workflow config uses the `google-calendar-maton` integration key to reference this integration. You can chain it with other integrations — for example, trigger on a Calendly booking (from the Calendly integration), then create a corresponding preparation block in Google Calendar, then post a notification to a Slack channel. For availability checking workflows, the `query-events` action type returns a list of events in a time window. Your workflow conditions can then evaluate whether the result is empty (slot is free) or non-empty (slot is busy) before proceeding.

1# ~/.openclaw/config.yaml — calendar automation workflow
2workflows:
3  create-prep-block:
4    trigger:
5      type: manual             # Or chain from another integration trigger
6    actions:
7      - type: integration-call
8        integration: google-calendar-maton
9        action: create-event
10        params:
11          summary: "Meeting Prep"
12          description: "Auto-created prep block"
13          start: "{{date.today}}T09:00:00"
14          end: "{{date.today}}T09:30:00"
15          timezone: "America/New_York"
16
17  check-availability:
18    trigger:
19      type: manual
20    actions:
21      - type: integration-call
22        integration: google-calendar-maton
23        action: list-events
24        params:
25          time_min: "{{input.start_time}}"
26          time_max: "{{input.end_time}}"
27      - type: condition
28        if: "{{result.count == 0}}"
29        then:
30          - type: log
31            message: "Slot is available"
32        else:
33          - type: log
34            message: "Slot is busy: {{result.events | map('summary') | join(', ')}}"