Google Calendar

What it is

The owner's diary and often the business's booking book: site visits, shoots, tours, catering dates and staff shifts. Small businesses without a booking system run on it.

How an agent connects

1. The AHL gateway. The default. When the owner connects Google, consent also asks for calendar events. The gateway offers calendar.list and calendar.draft_event. A Google connection made before calendar support was added must be connected again.
2. Google's official MCP server (calendarmcp.googleapis.com), in Developer Preview. It lists, searches, creates, updates and deletes events, answers invitations and suggests times. It signs in with OAuth and needs a Cloud project in the preview program.
3. Calendar API for code an intern builds, with a read-only scope unless the job truly writes.
4. Zapier and n8n have calendar triggers and actions for an owner's simple automations.

What agents may do

agent_access: draft. An agent reads the calendar to check dates and proposes events. A proposed event becomes real only when the owner approves it, because Google then sends invitations to customers.

Through the gateway

calendar.list reads at most 31 days at a time, runs straight away and is logged. calendar.draft_event is held for the owner unless a standing permission covers it once the agent is live. Once approved, Google sends the invitations. For a business with no Google connection, manual.draft_event shows the event on the owner's page to add by hand. Deleting or moving a customer's booking is never automated.

Watch out for

• An event invitation is a message to a customer. Treat it like a send.
• Time zones: always pass the offset. A date check that ignores it double-books.
• Private events can hold health or family details. Read only the fields the job needs.
• The official MCP server can delete events. Do not connect it to a client calendar while it is in preview.
• Community servers with write tools should run read-only, on test calendars, if at all.