Connecting Google Calendar

Connect Google Calendar and Monad can manage your schedule for you — without ever handling your password. You connect once with your own Google sign-in, and agents use that access when they act on your behalf. While the connection is active, Library also maintains a read-only mirror of supported events so related clusters stay current.

Google Calendar connects directly to Google, so Monad can read your calendars and events, check your availability, schedule and update events, and RSVP to invitations.

What Google will ask for. When you connect, Google's consent screen lists the access you're granting — reading your calendars and events, and creating or changing events. That access is what lets an agent put a meeting on your calendar or accept an invite; if you only want agents to read, you can turn off the event-changing tools per connector after connecting (see Choosing what agents can do).

Connecting#

There's nothing to set up — Monad handles the Google connection for you, so you never create an OAuth app or paste any keys.

1. Open Settings → Connection Preferences (or the Connectors section on the Connections page) and find Google Calendar.
2. Click Add, then on the connector's page click Connect.
3. Sign in with Google and approve the requested access. You'll be returned to Monad with a green Connected badge.

Once Google Calendar is connected, its card turns into a dimmed Added tile and it shows up in your Connections list above — open it from there any time to manage or disconnect it.

From then on you can ask an agent things like "what's on my calendar tomorrow?" or "find a free hour this afternoon" without thinking about credentials.

What Monad can do#

Monad acts as your account. It can:

• List your calendars and read events and their details.
• Suggest open meeting times by checking free/busy availability.
• Create, update, and delete events, and RSVP to invitations.

They only ever touch Google Calendar — never your wider Google account.

Choosing what agents can do#

Every Calendar tool can be turned off independently from the connector's page, so you can keep the connection but narrow what agents may do — for example, allow reading and time-suggestions but block creating, changing, or deleting events. Turning a tool off here disables it for agents; it doesn't change the access you granted Google (that only changes when you reconnect or disconnect). Read-only tools appear first, followed by tools that can change your calendar; each group is alphabetical. A writes badge beside a tool's name marks the second group. These switches control agent tools. They do not pause Library's read-only mirror; disconnect Calendar to stop both uses of the connection.

How Calendar appears in Library#

A personal Calendar connection creates Only you Library objects. A shared workspace connection creates workspace-visible objects. Library keeps those objects current incrementally and may use them in eligible clusters.

You can promote an eligible object from a personal connection without sharing your whole calendar: open the object's Monad detail page and choose Share to workspace. The action is recorded, and that object can then contribute to workspace clusters. Choose Revoke share to return it to Only you; Library removes its workspace memberships and grounded claims as it rebuilds the affected clusters. Sharing never gives another member control of your Google account.

Reconnecting#

If you see an amber Reconnect needed badge, your access expired or the permissions changed. Click Reconnect and approve again, or choose Disconnect to remove your connection without reconnecting first.

Disconnecting#

Click Disconnect at any time and Monad immediately stops using your Google Calendar account. Disconnecting also revokes Monad's access at Google, so it's removed from your Google Apps with access to your account list — you don't need to do that step yourself. Library removes the connection's mirrored objects and refreshes affected clusters. For a personal connection, other members and admins see only objects you explicitly shared—not the rest of your calendar or your tokens.