Linode

Cloud Personal access token

Create and manage Linode instances, volumes, DNS and networking from any Windmill script, flow or app.

Set up in 3 steps

1

Create a personal access token

In the Linode Cloud Manager, open your profile then API Tokens. Create one, granting only the scopes your scripts need, and copy it.

2

Add the resource in Windmill

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

3

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

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

View raw schema →
FieldTypeRequiredWhat it is
tokenstringYesPersonal access token for Linode API.

Questions

Creating things costs money

Instances, volumes and load balancers are billed from the moment they exist. Scripts that create them should have a matching path that deletes them.

A call returns 403 on one endpoint

Linode tokens are scoped per area — Linodes, Domains, Volumes and so on — and read-only by default. Widen the token in the Cloud Manager.

Is my token stored on the hub?

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