Google Docs

Productivity OAuth

Fill templates, read, edit and export Google Docs from any Windmill script, flow or app: text, tables, images and tabs, with PDF or Word exports saved to object storage.

Set up in 2 steps

1

Connect from the Resources page

Open Resources, click Add a resource/API and pick gdocs from the OAuth APIs list. Click Connect and sign in with the Google account that owns the documents, then name the resource and save it.

2

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.

Submit a script →

Resource type

The shape of the credential every script on this page expects.

FieldTypeRequiredWhat it is
tokenstringYesThe OAuth token, refreshed if necessary

Questions

What can Windmill do with my account?

The default connection asks for the documents scope: read, edit and create any doc the account can open. Creating a document from a template also needs the drive scope (to copy a template the connection didn't create), and exporting, finding documents and listing comments need drive.readonly or drive, since those go through the Drive API. Tick them in the connect dialog's scope options.

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.