dusk bot
integrationsget event instances

dusk botintegrationsgoogle calendar

find the actual dates in a recurring calendar series

hand the trainer real dates instead of saying every tuesday. the bot finds your recurring google calendar event and lists its occurrences within a chosen window.

by the dusk bot team · checked · how we made this

include cancellations so nobody travels for a skipped session. this only lists dates, but dusk classes the action as a write. give it read and write access limited to this job.

pixel art: a lime pixel bot, a purple pixel bot and a pink pixel bot beside the Google Calendar mark on a white tile, an alarm clock and a calendar and a notebook, on a lilac hill in front of a calm sea with one small island, one saying "each date in order"

get event instances, in plain words

get the next four weeks laid out in order. name the repeating event and its calendar; your main calendar works too. the bot finds the series first.

name the time zone and ask for cancellations beside the scheduled dates. a long series can fill several batches, so tell it to keep going until it has the whole window.

a routine to copy

paste this into a chat with your bot

on the second tuesday of each month at 12:30, find the recurring kiln safety course on my training calendar. list the next four weeks in india time here for nikhil. keep going until all dates in that window are listed. mark cancellations and never count them as sessions to attend. never edit the series.
when
second tuesday of each month at 12:30
needs
google calendar with read and write; allow calendar and series lookups plus this action only

what comes back looks like this (an example)

kiln safety course, next four weeks
india time
- 17 november, 10:00: scheduled
- 24 november: cancelled
- 1 december, 10:00: scheduled
- 8 december, 10:00: scheduled
24 november is a week off.

good jobs for it

  • give a visiting trainer the dated sessions in a recurring course
  • spot a cancelled holiday-week session before anyone travels
  • list upcoming dates in your own recurring treatment series

before it runs

dusk bot counts Get Event Instances 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.events.public.readonly, calendar.events.owned.readonly, calendar.events.readonly, calendar.readonly.

how to start

  1. connect google calendar. give the course name and the calendar it belongs to.
  2. allow read and write for this action and its lookups. leave event edits outside the action list.
  3. compare the short list with your calendar. look for the right time zone and marked cancellations.
  4. schedule that same four-week search. look at the next runs and Pause when the course ends.

limits worth knowing

  • start with a repeating event. a standalone appointment has no series to expand.
  • a date window keeps the job manageable. a request for every occurrence can run slowly or fail.
  • use the dates for planning sessions. an attendee limit can leave people out, so get attendance separately.

the details it works from

inputrequiredwhat it is
eventIdyesREQUIRED.
calendarIdyesCalendar identifier.
timeMaxnoUpper bound (exclusive) for an event's start time to filter by.
timeMinnoLower bound (inclusive) for an event's end time to filter by.
timeZonenoTime zone used in the response.
pageTokennoToken specifying which result page to return.

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

try it in 2 minutes

  1. name the calendar and repeating meeting
  2. ask for the next four weeks in your time zone, including cancellations
  3. compare one scheduled date and one skipped date with your calendar

mistakes people make

treating every returned date as a meeting to attend

show cancellation status beside each date.

using it as a complete guest list

get attendance separately. the returned details can omit people.

questions

will this change the repeating meeting?

no meetings change. it only lists occurrences. dusk counts this action as a change, so read and write is still required.

can it include the skipped dates?

yes, ask for cancelled occurrences too. show their status beside each date and compare the short list with your calendar.

sources

  1. dusk bot docs: files and apps
  2. dusk bot docs: routines
  3. dusk bot docs: a bot's computer
  4. 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].