make a separate google calendar for one project

give a project its own calendar before it crowds your personal one. a bot can create a secondary google calendar with a title, description, location and time zone.

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

your connected account owns it. name the time zone because the default is utc. creation won't ask first unless you put that instruction in the job.

pixel art: a green pixel bot and a blue pixel bot beside the Google Calendar mark on a white tile, an alarm clock and a calendar and a signpost, on a lilac hill in front of little green islands on a lake, one saying "a calendar for rehearsals"

what it does

give rehearsals a home of their own. this action creates a secondary calendar and its settings. choose the owning account and title, then add a description and location if useful. your primary calendar stays put.

say "paris time" for the time zone; a city in the description won't set it. the default is utc. events and sharing take separate steps, so the calendar starts empty.

when you would use it

separate touring dates. keep production planning away from personal appointments.
start a course intake. give the new cohort its own calendar and location description.
contain the office move. make one temporary home for appointments before people add them.

try it

paste this into a chat with your bot

on the first tuesday of each quarter at 11, read the harrow lane theatre season plans in our project folder. find newly confirmed seasons that name a calendar and don't yet list one.

show the proposed title, description, location and paris time zone here. ask me before you change anything. create only calendars i confirm in my work account. return each calendar's details here. never add events, change sharing or recreate a calendar already listed in a season plan.

when: first tuesday of each quarter at 11:00
needs: access to the season plans folder; google calendar read and write for calendar creation

what comes back looks like this (an example)

harrow lane winter rehearsals
owner: connected work account
location: west rehearsal room
time zone: paris time

ready for your review. no calendar created.

set it up

pick the owner first. connect the right google account and allow calendar creation with read and write.
name the calendar and zone. give its purpose too, so the title still makes sense next season.
put review in the request. tell the bot to wait before creating anything.
open the result. read the owner and time zone in settings. pause the quarterly routine when season intake ends.

what it needs from you

input	required	what it is
`summary`	yes	Title of the calendar.
`location`	no	Geographic location of the calendar as free-form text.
`timezone`	no	The time zone of the calendar, specified as an IANA Time Zone Database name (e.g., 'America/New_York', 'Europe/London', 'Asia/Tokyo').
`description`	no	Description of the calendar.

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

how dusk bot handles it

dusk bot counts Create a new calendar 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.calendars.

where it stops

no zone means utc. a place name in the location field won't change that default.
choose work or personal before creation. the connected account owns the new calendar.
events and sharing are separate. this action has no sharing setting and doesn't fill the schedule.

try it in 2 minutes

choose the google account that should own it
name one new calendar and its time zone
ask to review its settings before creation
open the new calendar settings before adding events

mistakes people make

putting the city only in the description

set the time zone too. otherwise the new calendar uses utc.

making a new calendar every quarter regardless

read the season plans first. create only for confirmed seasons that need one.

questions

does this replace my primary google calendar?

no, your primary calendar stays. the new one is a secondary calendar owned by the connected account.

can i name the calendar and set its city?

yes, give a title and optional location. add a description if useful. set the time zone separately from the city text.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: computer permissions
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].