Google Calendar

01

Setup

1. 01Connect Google. In the superagnt app open Integrations, pick Google Calendar and click Connect with Google.
2. 02Approve calendar access. Google asks only for calendar access (the https://www.googleapis.com/auth/calendar scope) plus your Google identity. Approve it in the Google window.

Google Calendar, Google Docs, Google Sheets and Google Search Console share one Google sign-in, but each is its own connection with its own consent: connecting one never grants the others. If the workspace already has a Google account connected for another Google app, the dialog offers Connect Google Calendar instead, which asks that account for Google Calendar's permissions only. Access tokens are refreshed for you.

02

Things to know

• For a date-range agenda, pass timeMin and timeMax with singleEvents=true and orderBy=startTime, so recurring events expand into instances. q searches event text (summary, description, location and attendees).
• Free/busy returns busy intervals only. Compute the free gaps by subtracting them from your query window.
• Quick add parses times in the calendar's time zone on a best-effort basis. Check the returned start and end, and create the event in full when the time must be exact.
• An event update changes only the fields you pass.
• Deleting a calendar removes a secondary calendar with all its events (the primary calendar cannot be deleted). Clearing removes every event from the primary calendar, and works only there. Neither can be undone.
• When more than one Google account in the workspace has granted Google Calendar, calls use the account most recently connected to it.

03

Permissions

These defaults decide whether a superagnt_ agent runs a call or waits for a person (Permissions). Reads run without asking, and so does the free/busy query. Creating, quick-adding, updating and moving events, creating and updating calendars, and sharing a calendar or changing a share ask by default. Deleting an event, deleting or clearing a calendar and unsharing one always ask a person first, because they cannot be undone.

04

Examples

A day's agenda

curl "https://api.superagnt.com/v1/connections/google-calendar/calendars/primary/events?timeMin=2026-11-10T00:00:00Z&timeMax=2026-11-11T00:00:00Z&singleEvents=true&orderBy=startTime" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Create an event with attendees

curl -X POST "https://api.superagnt.com/v1/connections/google-calendar/calendars/primary/events?sendUpdates=all" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "summary": "Roadmap review",
    "start": {"dateTime": "2026-11-10T10:00:00-08:00", "timeZone": "America/Los_Angeles"},
    "end":   {"dateTime": "2026-11-10T10:45:00-08:00", "timeZone": "America/Los_Angeles"},
    "attendees": [{"email": "sam@example.com"}]
  }'

When is the team free?

curl -X POST "https://api.superagnt.com/v1/connections/google-calendar/freeBusy" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "timeMin": "2026-11-10T00:00:00Z",
    "timeMax": "2026-11-11T00:00:00Z",
    "items": [{"id": "primary"}, {"id": "sam@example.com"}]
  }'

10 tools, one per resource and risk

MCP servers and agents on the grouped surface list Google Calendar as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.

All 21 operations

Each operation is a REST path under https://api.superagnt.com/v1/connections/google-calendar and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.

Related