Google Calendar

Your assistant can read across every calendar you subscribe to, not just the primary one, and pull back a single list for a date range you name. It expands recurring series into the real instances, so a weekly standup shows up as the four dates it actually falls on. Nothing is created, moved, or canceled by asking.

What you end up with. A plain list of next week's commitments in one place, including the events sitting on secondary and shared calendars you forget to look at.

Start with it bringing you the information and you deciding.

Never without. Give it an explicit date range and time zone. A range read in the wrong zone silently returns the wrong days rather than an error.

Built on: List Events from All Calendars / Find event / Get Event Instances / Get current date and time

It can query free and busy blocks for a set of calendars and return the windows where nobody is booked. This is a read: it hands you candidate times and you pick one. What it sees depends on how much detail each person shares with you, so a colleague who only exposes busy blocks still works, but someone who shares nothing at all will look permanently free.

What you end up with. Two or three specific windows you can propose, instead of the round of emails that usually finds them.

Start with it bringing you the information and you deciding.

Never without. Check whether each person's calendar is actually shared with you before treating an empty block as availability.

Built on: Find free slots / List Events from All Calendars / Get Google Calendar

It can create the event, set the time and duration, add attendees, and attach a Meet link. Creating the event sends the invitation to every attendee at once, so this is the point where something leaves your account. Start by having it draft the details back to you and confirming before it writes.

What you end up with. A booked event with the right people and a conferencing link on it, without you retyping any of it.

Start with it doing the work and checking with you.

Never without. Confirm the attendee list and the time zone before it writes. Creating the event notifies everyone on it immediately, and a correction is a second email to the same people.

Built on: Create Event / Find free slots / Get Google Calendar

The distinction between the two ways of doing it matters. A patch changes only the fields you name and leaves everything else alone. A full update replaces the event, which clears anything you did not restate, including attendees, reminders, recurrence, and the conferencing link. Ask for a patch unless you genuinely mean to rebuild the event.

What you end up with. The meeting on its new time with the guest list, reminders, and video link still intact.

Start with it doing the work and checking with you.

Never without. Never let it use the full update path on an event with attendees. Omitted fields are cleared, so a rescheduled meeting can quietly lose its guest list and its Meet link.

Built on: Patch Event / Find event / Get Event / Update Google event

It can delete an event, and it can drop a single person from one without canceling the whole thing. Both are one-way. The safe pattern is to have it search first, read back the exact event it found with the date and the attendees, and only then act on that specific event.

What you end up with. The event gone from everyone's calendar, or one person removed from it, with the cancellation notice already sent.

Start with it doing the work and checking with you.

Never without. Never let it delete from a text search alone. A deleted event cannot be restored, every attendee is told it is canceled, and two meetings with similar titles is the normal case rather than the edge case.

Built on: Delete event / Remove attendee from event / Find event / Get Event

This is a bounded routine rather than a one-off. It reads the coming week, finds the calls that match a rule you set, and blocks the half hour before each one on your own calendar. Because the blocks carry no attendees, a mistake costs you a deletion rather than an apology to a client. Nothing in Google Calendar makes this repeat: whatever schedules your assistant is what makes it happen every week, and the connector supplies the read and the blocks. Run it by hand for two or three weeks and read what it produced before it runs unattended.

What you end up with. Prep blocks already sitting in front of the calls that need them, on a calendar that reflects how the week will actually go.

Start with it doing the work and checking with you.

Never without. Keep the rule narrow and keep the blocks free of attendees, so nothing it creates unattended can send mail to another person.

Built on: Find event / List Events from All Calendars / Create Event / Get Event Instances

Sharing on a Google Calendar is a list of access rules, one per person, group, or domain. Your assistant can read that list back to you, which is often the first time anyone has looked at it in years. It can also add and remove rules, and removing one takes effect straight away with no notice to the person losing access.

What you end up with. A written answer to who can see this calendar, and a sharing list that matches who is still supposed to be on it.

Start with it doing the work and checking with you.

Never without. Have it list who loses access before it removes anything. Deleting an access rule is immediate and silent, and the person only discovers it when a calendar they rely on stops loading.

Built on: List ACL Rules / Get ACL Rule / Create ACL Rule / Delete ACL Rule

It can create a new secondary calendar, add it to your visible list, and set the time zone and description. New calendars default to UTC and do not appear in your interface until they are inserted into your calendar list, which is the step people miss and then assume it failed.

What you end up with. A project calendar you can toggle on and off, sharable on its own, sitting alongside your main one.

Start with it doing the work and checking with you.

Never without. Set the time zone explicitly after creating it. A calendar left on the UTC default puts every event you add on it at the wrong hour.

Built on: Create a new calendar / Insert Calendar into List / Patch Calendar / Get Single Calendar by ID