Google Cloud

Cloud Service account key

Call Google Cloud APIs — Cloud Storage, Compute, BigQuery — from any Windmill script, flow or app with a service account.

Set up in 3 steps

1

Create a service account and a key

In the Google Cloud console, open IAM & Admin, then Service Accounts. Create one, grant it the roles your scripts need, then add a key and download the JSON.

2

Add the resource in Windmill

Open Resources, add a resource of type gcloud, and paste the JSON — its fields map one to one.

3

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.

Resource type

gcloud — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
auth_provider_x509_cert_urlstringYes
auth_uristringYes
client_emailstringYes
client_idstringYes
client_x509_cert_urlstringYes
private_keystringYes
private_key_idstringYes
project_idstringYes
token_uristringYes
typestringYes

All resource types

Questions

What is gcloud_storage for?

It pairs a bucket name with the same service account key, so a script that only ever works in one bucket does not repeat it. The credential inside is identical.

Which roles should I grant?

Only what the scripts call. A service account key does not expire, so its blast radius is whatever you granted it, indefinitely.

Are my credentials stored on the hub?

Never. They live only in your own Windmill workspace, encrypted at rest.