Communication

Google Calendar

Calendar and scheduling

Overview

Personal calendar access so an agent can reason about your week: what a meeting is for, who is in it, and where the time actually goes.

You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.

1context types mined

1agent tool groups

1connection method

3security controls

Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.

Event context
Events, attendees, and scheduling read live from the connected calendar.

Example context item

google_calendar_event_context

PrimaryWeekly Revenue Review

Tools are granted per skill, never globally. Anything that changes state in Google Calendar is marked as a write and stops for human approval.

Calendar actions
Permission mirroringJust-in-time
Read and manage events on the connected calendar through the Google Calendar API, with writes gated behind approval.

Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.

Each user connects their own calendar. It is a personal connection: nothing is shared with the workspace.

Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.

Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.

Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.

Tool calls execute as the person asking, not as a shared workspace credential, so an agent can never reach a channel or file the user cannot.

Connect it in minutes and give every agent a governed understanding of what is inside, without moving a single row of data.