Fly integration | Windmill Hub

Set up in 3 steps

1

Create an access token

Run flyctl tokens create org, or create one from the Fly dashboard under Tokens. Prefer a token scoped to one app over a personal one.

2

Add the resource in Windmill

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

3

Run your first script

Fork any script below and read before writing anything. There are dozens 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

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

View raw schema →

Field	Type	Required	What it is
token	string	Yes

Questions

Machines bill while they exist

A started machine bills for its compute. Scripts that create machines should have a matching path that destroys them, not just stops them.

Is this the same as the GraphQL API?

No. These scripts use the Machines API, which is the REST one. Some older Fly operations only exist on the GraphQL endpoint.

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 access token

Add the resource in Windmill

Run your first script

Scripts

Wait for State

Verify with a secret key

Update Volume

Update Metadata

Update Machine

Uncordon Machine

Suspend Machine

Stop Machine

Start Machine

Signal Machine

Sign with a secret key

Restart Machine

Request an OIDC token

Request a Petsem token for accessing KMS

Release Lease

List secret keys belonging to an app

List app secrets belonging to an app

List Volumes

List Versions

List Snapshots

List Processes

List Machines

List Events

List Apps

Get an app secret

Get an app's secret key

Get Volume

Get Regions

Get Placements

Get Metadata

Resource type

Questions