Zendesk
Support Subdomain, email and API tokenCreate and update tickets, users and organizations, and read macros and views, from any Windmill script, flow or app.
Set up in 3 steps
Enable and create an API token
In Zendesk, open Admin Center, then Apps and integrations, then Zendesk API. Enable token access and add a token — it is shown only once.
Add the resource in Windmill
Open Resources, add a resource of type zendesk. subdomain is the yourcompany in yourcompany.zendesk.com; username is your agent email suffixed with /token; password is the API 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 Ticket Field
Export Suspended Tickets
Update Many Triggers
Update Many Automations
Bulk Create Memberships
Get sources by target
Delete Automation
Create Target
Create Membership
Delete Custom Object Field
Show Audit Log
Reorder Custom Fields of an Object
List Routing Attribute Definitions
Update Workspace
List Tickets From a View
Create Custom Object
List Supported Actions for Macros
Ticket Import
Show Support Address
List Group SLA Policies
Create View
List Ticket Metric Events
Delete Membership
List Comments
Show User Field
List Email CCs for a Ticket
Count Ticket Fields
Create Ticket Form
Show Custom Role
Set a User's Password
Resource type
zendesk — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| password | string | Yes | password or api token |
| subdomain | string | Yes | |
| username | string | Yes | email or "{email}/token" if using an api token |
Questions
Why does username end in /token?
Zendesk authenticates over HTTP Basic, and the /token suffix is what tells it the password field holds an API token rather than your account password.
What can the token do?
Everything the agent it belongs to can. Zendesk has no per-token scopes, so create it on an agent with the role you intend.
Are my credentials stored on the hub?
Never. They live only in your own Windmill workspace, encrypted at rest.