Create, move and read Google Calendar events from any Windmill script, flow or app.
What you can do with Gcal
Complete, deployable projects built around Gcal — 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 Attendees of an Event
Create Quick Event
Update Event
Delete Event
List Events
Create Event
Get Calendar Metadata
Get Calendar List
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?
Everything the connected account can do in Calendar. Grant it an account that only holds the calendars you intend to automate.
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.