Vercel
Cloud Access tokenManage deployments, projects, domains and aliases on Vercel from any Windmill script, flow or app.
Set up in 3 steps
Create an access token
In the Vercel dashboard, open Settings then Tokens. Choose the scope — your account, or a team — and copy the token; it is shown only once.
Add the resource in Windmill
Open Resources, add a resource of type vercel, 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.
Create Deployment
List Deployments
Cancel Deployment
Verify project domain
Upload a cert
Upload Deployment Files
Update the data cache feature
Update or move apex domain
Update deployment integration action
Update an existing project
Update an existing DNS record
Update an access group project
Update an access group
Update an Edge Config
Update a project domain
Update a custom environment
Update a check
Update a Team Member
Update a Team
Update Resource Secrets
Update Protection Bypass for Automation
Update Firewall Configuration
Update Edge Config schema
Update Edge Config items in batch
Update Attack Challenge mode
Unpause a project
Submit Prepayment Balances
Submit Invoice
Submit Billing Data
SSO Token Exchange
Resource type
vercel — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes |
Questions
A project is not found
Almost always the token's scope. A token scoped to your personal account cannot see a team's projects — create one scoped to the team instead.
Is my token stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.