Qovery

Cloud API token

Deploy and manage Qovery environments, applications, databases and secrets from any Windmill script, flow or app.

Set up in 3 steps

Create an API token

In the Qovery console, open your organization settings then API tokens, and create one with the role the scripts need.

Add the resource in Windmill

Open Resources, add a resource of type qovery, and paste the token.

Run your first script

Fork any script below and read before writing anything. There are hundreds here, so search by the verb you need.

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

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

View raw schema →

Field	Type	Required	What it is
apiKey	string	Yes	API key for authentication

Questions

What can the token do?

Whatever its role allows, within the organization it was created in. Create it with the narrowest role the scripts need rather than reusing an owner token.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

Set up in 3 steps

Create an API token

Add the resource in Windmill

Run your first script

Scripts

Upgrade a cluster

Update karpenter private fargate subnet ids

Update enterprise connection

Update deployment rules priority order

Update alert rule

Update alert receiver

Unlock Cluster

Uninstall terraform

Uninstall services

Uninstall job

Uninstall helm

Uninstall environment

Uninstall database

Uninstall container

Uninstall application

Transfer organization ownership to another user

Stop services

Stop job

Stop helm

Stop environment

Stop database

Stop container

Stop cluster

Stop application

Specify cluster cloud provider info and credentials

Send Sign Up request

Retart database

Remove database backup

Remove an invited member

Remove an application from this database

Resource type

Questions