Calendar

A calendar connection turns “what’s on my plate?” into a real question your AI can answer.

Once your calendar is connected (see Connect Google Workspace for Google; other providers may follow the same pattern), your AI can read upcoming events, infer who’s involved, prepare you for meetings, schedule across time zones, and use your calendar as context for everything else.

This chapter is what you can do once it’s set up.

The daily brief

Most customers set a daily morning brief as one of their first goals.

“Each morning at 8am, send me a brief on what’s coming today: events, who’s in them, anything I should prepare, anything that looks like a conflict.”

The brief arrives on your default channel and includes:

Events for the day with times and locations.
People you’ll be meeting with, what you last interacted about, recent context.
Files or threads that look relevant to upcoming meetings.
Anything that looks like a conflict (overlapping events, back-to-back without buffer, travel time issues).
Things you said you’d prepare ahead of time, surfaced as a reminder if you haven’t.

You can adjust the shape (“less detail on internal meetings, more on external ones”; “only flag the new stuff, not the recurring stuff”) with corrections, in the usual way.

Asking about specific days

In any channel:

“What’s on my calendar tomorrow?”
“When’s my next call with Mike?”
“Do I have anything Friday afternoon?”
“How does next week look?”

Your AI answers from the connected calendar, with the same context (people, files, prior threads) it’d include in a daily brief.

Meeting prep

Before a meeting, you can ask:

“I have a call with Anna at 3pm. What do I need to know?”

Your AI looks at:

Anna’s record in your knowledge graph (who is she, what role).
Recent email threads with Anna.
Documents you and Anna both have access to.
Any project Anna is involved in, and recent activity there.
Open follow-ups (you said you’d do something for Anna; is it done?).

It produces a meeting brief artifact, usually in 30 seconds or less, including a short bulleted summary, recent thread context, and any open items.

You can prompt this proactively as a goal: “An hour before any external meeting, send me a prep brief on the participants and the topic.”

Scheduling

The classic use case: finding a time that works for everyone.

“Find a 45-minute slot next week for me, Anna, and Mike. Mornings preferred. Anna’s in Mountain time.”

Your AI checks your calendar, asks for or pulls availability for the others, accounts for time zones, and proposes options. You pick one and your AI sends invites.

The where-time-zones-get-it-wrong cases are common with humans and usually right with your AI. It’ll tell you “3pm your time, 4pm Anna’s, 2pm Mike’s” so everyone can verify.

Creating events

“Block my calendar Thursday afternoon for focused work.”

“Add a recurring weekly 1:1 with Lily, Wednesdays at 6pm.”

“Schedule a contractor walkthrough at the house, an hour, sometime next week. Mike or Anna both work.”

These create events with approval (Approvals and gates). For internal blocks you set on yourself, you might loosen the gate after a few uses. For invitations to others, keep the gate; it’s worth a click.

Cancelling, moving, rescheduling

“Move the 3pm to 4pm.”

“Cancel tomorrow’s check-in with Mike; tell him we’ll do it next week instead.”

“I’m not going to make the team standup; let them know.”

Your AI handles the calendar action and any notifications. Cancellations that need messaging the other attendee usually surface as a “send this note?” approval gate.

Catch-ups, end-of-day, and weekly reviews

“End-of-day review the calendar: what happened today, what slipped, what’s still open.”

“Weekly review: how did this week’s calendar look in aggregate? Where am I spending time?”

These produce reflective artifacts that you can use to adjust your own habits. Customers sometimes ask them as one-offs; others schedule them as recurring goals.

What it doesn’t do (or doesn’t yet)

Doesn’t pull every calendar at once. You can connect multiple calendars (work and personal, separate accounts), but you specify which to read for which kinds of questions. Otherwise context gets crossed.
Doesn’t reschedule without permission. Even loose approval rules don’t apply to events involving other people; your AI will draft, you approve.
Doesn’t read others’ calendars without their explicit OAuth grant. This is the trust boundary; we don’t fish.
Limited free/busy scheduling assistants. Find-a-time across many external people who aren’t on shared calendars still requires the back-and-forth email dance. Your AI can drive that dance, but it can’t shortcut it.

A note on quiet calendars

Some people block their calendar heavily; others keep it bare. Both are fine. The brief and prep tooling work either way. If you don’t typically put internal work on the calendar, your AI doesn’t insist; it works from what’s there.

If you keep your calendar mostly empty and like it that way, you can still ask for a daily brief; it’ll just be short.

Connecting more than one calendar

You can connect multiple calendars (different Google accounts, an iCal feed, etc.). When you connect more than one, you’ll be asked which is the default for new events and which are read-only.

A common pattern: personal Google calendar as default, work Google calendar as read-only for context but not write-target.