Plan meetings across your Google Workspace calendars

The agent calls the Google Calendar API v3 on your request: it reads the account calendar list, events with attendees, location, description and reminders, instances of recurring meetings and busy time across several calendars at once. Out of that it assembles the plan for today and tomorrow, finds the clashes, picks a free slot of the length everyone involved needs and sends a scheduled summary of the day with the free hours left.

Google Calendar is built around the calendar list of one specific account: the agent sees exactly what that list holds and queries each calendar separately by its identifier. The access level decides a lot too: at the free/busy level only busy intervals are visible, without titles or attendees, so the agent will name a clash but not its reason. A recurring meeting arrives as a rule, so the agent expands the concrete dates of the series itself.

For writing, the agent creates events with attendees, location, description and a reminder, moves them and deletes them. It is careful here: a move or a cancellation mails everyone invited, so a change to someone else meeting is confirmed before it goes out, and on a recurring series the agent asks separately whether to edit a single instance or the whole chain. Batched edits go one meeting at a time, with the list shown before a single mail leaves.

Connecting is a sign-in to a Google account in a separate window, with no keys to copy: access lives as a token that refreshes itself and dies the moment you revoke the grant on the account access page. The agent holds the request rate itself so as not to run into the Google quota, and fetches long periods in date windows. If a calendar is unavailable, the grant was revoked or the day really is empty, it says so directly instead of showing an empty table.