change a calendar detail without replacing the event

send visitors to the right entrance without rebuilding the meeting. the bot can fix a google calendar location, title or time while leaving other details alone.

by the dusk bot team · checked 12 november 2026 · how we made this

name the calendar and event date. guest lists and repeat rules replace their whole existing lists, so keep those outside a simple room correction. ask for a preview and a pause before the edit.

pixel art: a yellow pixel bot, a purple cat bot and a blue pixel bot beside the Google Calendar mark on a white tile, a folded map and an alarm clock and a calendar, on a grassy meadow in front of chalk cliffs by the sea, one saying "use the new room"

what it does

the appointment can stay while the address changes. have the bot find it, confirm the date and calendar, then change only the detail you name.

guest and repeat schedules replace the whole existing list
adding one guest means reading the current guest list first
update emails follow your account default unless you choose yes or no

say what should stay, and whether guests should hear about the edit.

when you would use it

save visitors a wrong turn. correct the room without touching guests.
make the title useful. replace a vague name with the agreed workshop title.
move the right appointment. confirm the date before changing its start time.
fix stale directions. replace the old entrance in the description.

try it

paste this into a chat with your bot

every monday at 12:30, read emails received in my work gmail during the last seven days from our studio bookings team. find explicit room corrections for studio visits this week. match each to an event on my work google calendar. show the event date, current location and proposed location here. ask me before you change anything. change only locations i approve and turn guest update emails off. leave attendees, repeat schedules, meeting links and times alone. ask about unclear matches.

when: mondays at 12:30
needs: gmail read only; google calendar read and write for finding and correcting events

what comes back looks like this (an example)

location correction awaiting review

studio visit, wednesday 14:00
current: north entrance
proposed: courtyard entrance, wren house
source: studio bookings email
only the location would change.

set it up

connect the calendar. give the bot read and write, limited to the actions it needs.
name the meeting precisely. include calendar, title and date. the bot finds the event.
require a preview. ask for old and new values, then a wait for your agreement.
open the changed event. confirm its location after the first edit and narrow unclear matching rules.

what it needs from you

input	required	what it is
`event_id`	yes	The unique technical identifier of the event to update.
`calendar_id`	yes	Identifier of the calendar.
`source`	no	Input model for event source.
`status`	no	Status of the event.
`summary`	no	New title for the event.
`color_id`	no	Color ID for the event (1-11).

from composio's catalog for Google Calendar (action GOOGLECALENDAR_PATCH_EVENT, read 12 november 2026⁴). your bot fills these in from what you tell it.

how dusk bot handles it

dusk bot counts Patch Event as a change: it alters something in Google Calendar, and the sending setting does not cover it. a bot you allow only to read can never call it.

the permissions Google Calendar asks for to run it: calendar, calendar.app.created, calendar.events, calendar.events.owned.

where it stops

repeating meetings need a date. say which occurrence you want changed.
a guest list replaces everyone. the bot must include current guests when adding someone.
guest emails follow the edit’s own choice. sending settings do not decide this. say yes or no in the request.
times need a zone. without one, the bot may interpret the time as utc.

what it looks like

an invented room correction

before

rosa’s wednesday visit still says north entrance. the bookings email now says courtyard entrance, wren house.

after the bot

the bot previews a location-only change for wednesday at 14:00. rosa’s guest list and meeting time stay out of the edit.

an illustration with made-up names and numbers.

try it in 2 minutes

name the calendar and event date
ask for its current location
propose a new location with guest emails off
review before allowing the edit

quick checklist

correct calendar and occurrence
only intended details will change
guest update choice says yes or no
new time includes its time zone

mistakes people make

adding one guest as a list of one

read the current guests first or the edit can remove everyone else.

moving “the friday meeting”

give the exact date and time zone before anything changes.

questions

can it change just the address and keep the rest?

yes. ask for a location-only change and a preview of the meeting first. details left out of the edit stay as they are.

what happens if i ask it to add one attendee?

the new list replaces the old one. the bot needs to read everyone already invited and include them too.

will my guests get an email about the change?

say whether guests should hear about it. tell the bot to notify guests or keep update emails off. leaving it out uses your google default.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: a bot's computer
composio, Google Calendar toolkit (catalog version 20261103_00), checked 12 november 2026

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].