dusk botintegrationsgoogle calendar
put a new event in google calendar by asking
get the appointment out of your messages and onto the calendar. give a bot the title, date, time zone and duration. it can create timed or all-day entries.
ask for availability separately. google emails all guests by default; dusk treats creation as a change. put review and notification choices in your request before the bot creates it.

create event, in plain words
book the slot you agreed, on the calendar you meant. choose your primary calendar, or ask the bot to list your calendars. look up availability separately before booking.
- timed entries need a start and an end or duration
- all-day entries end on the following date for a single day
- eligible events request a meet link by default; turn it off for a simple reminder
a routine to copy
paste this into a chat with your bot
each saturday at 10, read new emails from larch quay gallery in gmail from the past week. find confirmed exhibition dates, not tentative ones. compare them with my personal google calendar and skip entries already there. propose each missing all-day event with its venue. ask me before creating anything. add only approved events, with no guests, no meeting link and guest notifications off. list the saved entries here. never change existing events.- when
- saturdays at 10:00
- needs
- gmail connected as read only; google calendar connected with read and write for calendar lookup and event creation
what comes back looks like this (an example)
proposed exhibition
mina's glasswork at larch quay gallery
all day: 21 november. calendar: personal.
no guests, guest emails or meeting link.
add this event?good jobs for it
- keep confirmed exhibition dates visible. add an all-day entry.
- reserve the workshop slot. include the street address and duration.
- stop losing repair appointments. give the bot the date and time you agreed.
- keep practice at the right hour. give repeating sessions an explicit time zone.
before it runs
dusk bot counts Create 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.
how to start
- connect google calendar with read and write access for this bot.
- name the calendar and time zone. ask it to list calendars if the name is unclear.
- try one event. choose guest emails and meeting-link options, then ask to review before creation.
- open the saved event in google calendar. pause the routine if it proposes unconfirmed dates.
limits worth knowing
- find a free slot first. event creation won't look for clashes; request an availability lookup.
- defaults can surprise guests. updates default to all attendees; eligible events request a meet link.
- no time zone means utc. spell yours out, especially for repeating events.
- your laptop must stay awake. missed runs under 12 hours old run once on return. older runs skip. dusk cloud runs on time.
the details it works from
| input | required | what it is |
|---|---|---|
summary | no | Summary (title) of the event. |
end_date | no | Exclusive end date for an all-day event in YYYY-MM-DD format. |
location | no | Geographic location of the event as free-form text. |
timezone | no | IANA timezone name from the timezone database (e.g., 'America/New_York', 'Europe/London', 'Asia/Jerusalem', 'UTC'). |
attendees | no | List of attendees. |
eventType | no | Type of the event, immutable post-creation. |
from composio's catalog for Google Calendar (action GOOGLECALENDAR_CREATE_EVENT, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- name a calendar and your time zone
- ask for a ten-minute test event with no guests
- request no meet link and no guest emails
- review the proposal before it creates anything
before it hits the calendar
- the calendar and time zone match
- availability got a separate check
- all-day dates cover the intended days
- guest emails and meeting links match your choice
mistakes people make
saying 'three tomorrow'
give the date, time zone and duration. ambiguity costs calendar space.
expecting sending approval to catch guest emails
event creation is a change. ask to review before creation.
questions
can i ask for a whole-day event instead of choosing hours?
yes. give dates rather than hours. the end date falls outside the event. for one day, the bot uses the next date as the end.
will it warn me if i already have a meeting?
ask for an availability lookup before creating it. event creation alone won't warn you about a clash.
does adding a guest send an invitation email?
by default, yes. google emails all attendees. dusk counts event creation as a change. put review and notification choices directly in your request.
sources
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].
change a calendar detail without replacing the event
a calendar bot that finds you room to think
make a separate google calendar for one project
see events from your google calendars together
an ai chief of staff for the loose ends
an ai executive assistant for inbox and calendar work