List, upload, copy and share Google Drive files from any Windmill script, flow or app.
Set up in 2 steps
Connect from the Resources page
Open Resources, click Add a resource/API and pick gdrive from the OAuth APIs list. Click Connect and sign in with the Google account that owns the files, then name the resource and save it.
Run your first script
Fork any script below and list a folder 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.
Get new files
Delete Shared Drive
Update Shared Drive
Search Shared Drives
Move File to Trash
Get Shared Drive
Create Shared Drive
Create Folder
Copy File
Delete File
Download Files (Google Docs, Sheets, Slides)
Subscribe to Watch Changes
Get Changes
Download a file
Flows
Multi-step workflows that already wire Gdrive to something else.
Resource type
The shape of the credential every script on this page expects.
gdrive
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes |
Questions
What can Windmill do in my Drive?
Everything the connected account can. The connection asks for the full drive scope, so scripts can read, write and delete — grant it an account that only holds what 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.