;}%20.st6{fill:url(%23SVGID_00000021089067129159788970000008246765442136188072_);}%20.st7{fill:url(%23SVGID_00000117639240116366130650000015074833605515028638_);}%20.st8{opacity:0.4;fill:url(%23SVGID_00000101781798616409025840000016567063639337360777_);}%20.st9{opacity:0.4;fill:url(%23SVGID_00000052086836598721292040000002033117744178971046_);}%20.st10{opacity:0.4;fill:url(%23SVGID_00000159460939004760751800000002448009281983951536_);}%20.st11{opacity:0.4;fill:url(%23SVGID_00000013177830667419993080000017721442101626521532_);}%20.st12{opacity:0.4;fill:url(%23SVGID_00000152235521444854938490000006526001119318383285_);}%20.st13{opacity:0.4;fill:url(%23SVGID_00000119823135212293698520000012774889010992664993_);}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st2'%20points='134.78,14.22%20114.31,48.21%20101.33,69.75%20158.22,69.75%20177.97,36.95%20191.67,14.22%20'/%3e%3cpolygon%20class='st3'%20points='227.55,69.75%20186.61,69.75%20101.33,69.75%20129.78,119.02%20158.16,119.02%20228.61,119.02%20256,119.02%20'/%3e%3cpolygon%20class='st3'%20points='136.93,132.47%20116.46,167.93%2073.82,241.78%20130.71,241.78%20144.9,217.2%20180.13,156.18%20193.82,132.46%20'/%3e%3cpolygon%20class='st3'%20points='121.7,131.95%20101.23,96.49%2058.59,22.63%2030.15,71.91%2044.34,96.49%2079.57,157.5%2093.26,181.22%20'/%3e%3cpolygon%20class='st2'%20points='64.81,131.95%2025.15,131.21%200,130.74%2028.44,180.01%2066.73,180.72%2093.26,181.21%20'/%3e%3cpolygon%20class='st2'%20points='165.38,181.74%20184.58,216.46%20196.75,238.47%20225.19,189.2%20206.66,155.69%20193.83,132.46%20'/%3e%3c/g%3e%3c/svg%3e)
Windmill HubCreate, move, RSVP to and read Google Calendar events — recurring series included — from any Windmill script, flow or app.
What you can do with Google Calendar
Complete, deployable projects built around Google Calendar — the fastest way to get something real running.
Set up in 2 steps
Connect from the Resources page
Open Resources, click Add a resource/API and pick gcal from the OAuth APIs list. Click Connect and sign in with the Google account that owns the calendars, then name the resource and save it.
Run your first script
Fork any script below and read before writing anything.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Update Following Instances
Update Event Instance
Respond to Event
List Event Instances
Get Event
Query Free/Busy
Update Attendees of an Event
Create Quick Event
Update Event
Delete Event
List Events
Create Event
Get Calendar Metadata
Get Calendar List
Trigger flows from Google Calendar
Google Calendar is not only a destination. These inbound paths are supported today.
Calendar changes (native Google trigger)
Add a Google trigger of type Calendar on a script or flow and pick a calendar: Windmill subscribes to Google's push notifications and starts a run whenever an event on it is created, updated or deleted. The notification says that the calendar changed, not what changed, so start from the Google native trigger template script in the gworkspace integration: it keeps a sync token in state and returns the changed events, deletions included. Set its resource path to your gcal resource. The first notification only stores the sync token and returns no events.
Resource type
The shape of the credential every script on this page expects.
gcal
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes | The OAuth token, refreshed if necessary |
Questions
What can Windmill do with my account?
By default, read and write events on every calendar the connected account can access — the connection asks for calendar.events, not full calendar access. Listing calendars, reading calendar metadata and querying free/busy need extra read-only scopes: tick calendar.calendarlist.readonly, calendar.calendars.readonly and calendar.freebusy (or calendar.readonly) when you connect.
Can I create the resource by hand instead of connecting?
Nothing stops you — the resource is a single token field. But Google's access tokens last about an hour and only the OAuth flow returns the refresh token that renews them, which is why this page has no CLI lane.
There is no Connect button on my instance
Self-hosted instances need a Google OAuth client configured once by an admin before the tile appears.