Google Calendar

Google Calendar: calendars, events, invites and free/busy times

Connects by
Signing in with Google
Category
Calendars and meetings
Part of
Google
Tools
40
ServiceKey
Google Calendarcalendar

Connecting

Your client presses Connect on their link and approves on Google's own screen. Operate As never sees their password.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "calendar"    ]  }]

Permissions

What the client readsPermission it asks for
See, add and change events on your calendarshttps://www.googleapis.com/auth/calendar.events
See the names of your calendarshttps://www.googleapis.com/auth/calendar.calendarlist.readonly

Tools

Install Google Calendar's typed package for your language:

pip install operate-as-calendar
Run calendar.create_event
curl -X POST https://api.operate.as/v1/actions/calendar.create_event \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "summary": "<summary>",      "start": "<start>",      "end": "<end>"    }  }'
InputTypeWhat it is
summaryrequiredstringThe event's title
startrequiredstringWhen it starts (RFC 3339, e.g. 2026-11-02T10:00:00-05:00)
endrequiredstringWhen it ends (RFC 3339)
calendar_idstringLeave empty for the main calendar
descriptionstringNotes on the event
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://www.googleapis.com/calendar/v3. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../calendar/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Google refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer
HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Google access ended. Send them their link to reconnect."}
Your webhook receives
{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "google",    "services": [      "calendar"    ],    "reconnectUrl": "https://…"  }}