Render
Cloud API keyManage Render services, deploys, environment variables, domains and disks from any Windmill script, flow or app.
Set up in 3 steps
Create an API key
In the Render dashboard, open Account Settings then API Keys, and create one. Copy it — it is shown only once.
Add the resource in Windmill
Open Resources, add a resource of type render, and paste the key.
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.
Verify DNS configuration
Update service
Update secret files
Update registry credential
Update redirect/rewrite rules
Update redirect/rewrite rule priority
Update project
Update notification settings
Update notification override
Update maintenance run
Update log stream override
Update log stream
Update environment variables
Update environment group
Update environment
Update disk
Update blueprint
Update autoscaling config
Update a webhook
Update Redis instance
Update Postgres instance
Update Key Value instance
Unlink service
Trigger point-in-time recovery
Trigger maintenance run
Trigger deploy
Trigger cron job run
Suspend service
Suspend Postgres instance
Subscribe to new logs
Resource type
render — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| apiKey | string | Yes | API key retrieved from the dashboard. |
Questions
What can the key do?
Everything your own account can, across every workspace you belong to. Render has no per-key scopes, so a key that can deploy can also delete.
Is my key stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.