a calendar bot that shows your options before changes

what a bot can do in Google Calendar

calendar planning starts with the right calendar and time zone. a bot can inspect events and find free slots, then explain its choices in chat. these actions also include event changes, which you can leave disabled.

composio, the connection service dusk bot uses for apps, lists 50 Google Calendar actions (catalog version 20261103_00, read 12 november 2026⁵). dusk bot treats 12 of them as reads, 0 as sends and the other 38 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Google Calendar

1. open Connected apps in the sidebar.
2. pick Google Calendar and sign in on Google Calendar's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Google Calendar.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

sign in to google calendar from Connected apps and enable it for your planning bot. tell the bot which calendar counts as work and what time zone to use. connect other accounts separately if your commitments are split across them, with a distinct label for each.

routines to copy

copy a message and make the working hours yours. each routine has a different purpose, and none requires the bot to move meetings on its own.

every sunday at 6 in the evening, find two uninterrupted 90-minute slots on my work calendar for the coming week, between 9 and 5. avoid lunchtime. explain the options here. do not create or change events.

every weekday at 4:30, inspect tomorrow's work calendar. show stretches of back-to-back meetings and any gap shorter than 15 minutes. suggest where i could request breathing room, but leave the calendar unchanged.

on the last friday of each month at 11, find next month's occurrences of the recurring meetings i named here. list their dates and how much calendar space they occupy. ask which i want to keep reviewing. do not cancel any.

what it asks you first

calendar edits need their own boundary. adding an event, changing its time or deleting it is not documented as asking first under the sending rule. the reliable start for a planning assistant is to keep change actions disabled.

if you later allow event writes, give an explicit rule such as "ask me before you change anything". name the exact calendar and event. the bot can be limited to an action list, so a bot allowed to create a focus block need not receive every calendar management action.

what it cannot do

• move or create events when its app grant only permits reading. a suggested slot in chat does not itself reserve that time.
• include commitments from accounts you never connected. a free-slot search only helps when the bot has the calendars that matter to your request.
• deliver a pre-work check from an asleep computer. missed desktop schedules less than 12 hours old run once when you return; older runs are skipped. dusk cloud runs routines on time.

say what free means to you

an empty hour may be lunch, travel or time you do not want to offer. put working hours and breaks into the request. ask the bot what time zone its routine uses if dates look wrong. the weekly calendar preview gives a broader view of the same week.

planning and preparation are different jobs

once you choose which meetings matter, a meeting prep routine can focus on the background you need. if your appointments live in microsoft instead, start with the outlook integration rather than assuming a google connection reaches them.