;}%20.st6{fill:url(%23SVGID_00000021089067129159788970000008246765442136188072_);}%20.st7{fill:url(%23SVGID_00000117639240116366130650000015074833605515028638_);}%20.st8{opacity:0.4;fill:url(%23SVGID_00000101781798616409025840000016567063639337360777_);}%20.st9{opacity:0.4;fill:url(%23SVGID_00000052086836598721292040000002033117744178971046_);}%20.st10{opacity:0.4;fill:url(%23SVGID_00000159460939004760751800000002448009281983951536_);}%20.st11{opacity:0.4;fill:url(%23SVGID_00000013177830667419993080000017721442101626521532_);}%20.st12{opacity:0.4;fill:url(%23SVGID_00000152235521444854938490000006526001119318383285_);}%20.st13{opacity:0.4;fill:url(%23SVGID_00000119823135212293698520000012774889010992664993_);}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st2'%20points='134.78,14.22%20114.31,48.21%20101.33,69.75%20158.22,69.75%20177.97,36.95%20191.67,14.22%20'/%3e%3cpolygon%20class='st3'%20points='227.55,69.75%20186.61,69.75%20101.33,69.75%20129.78,119.02%20158.16,119.02%20228.61,119.02%20256,119.02%20'/%3e%3cpolygon%20class='st3'%20points='136.93,132.47%20116.46,167.93%2073.82,241.78%20130.71,241.78%20144.9,217.2%20180.13,156.18%20193.82,132.46%20'/%3e%3cpolygon%20class='st3'%20points='121.7,131.95%20101.23,96.49%2058.59,22.63%2030.15,71.91%2044.34,96.49%2079.57,157.5%2093.26,181.22%20'/%3e%3cpolygon%20class='st2'%20points='64.81,131.95%2025.15,131.21%200,130.74%2028.44,180.01%2066.73,180.72%2093.26,181.21%20'/%3e%3cpolygon%20class='st2'%20points='165.38,181.74%20184.58,216.46%20196.75,238.47%20225.19,189.2%20206.66,155.69%20193.83,132.46%20'/%3e%3c/g%3e%3c/svg%3e)
Windmill HubZendesk
Support Subdomain and OAuth (authorization code or client credentials); legacy email and API token until April 2027Create, update and search tickets, manage users and organizations, run side conversations, and read macros, views and Help Center articles, from any Windmill script, flow or app.
Set up in 4 steps
Zendesk admin: create an OAuth client
In Admin Center, open Apps and integrations, then APIs, then OAuth clients, and add a client of kind Confidential with https://<your Windmill instance>/oauth/callback/zendesk as a redirect URL. Copy the identifier and the secret (shown once). Client-credentials tokens act as the admin who creates the client, so create it from a dedicated bot or admin agent for shared and scheduled flows.
Windmill instance admin: configure the client (authorization code)
In Instance settings, then OAuth, add Zendesk and enter the subdomain (yourcompany in yourcompany.zendesk.com), client id and secret. This is done once per instance, and connects one Zendesk account. Skip it if you only use client credentials.
Workspace user: connect the resource
Add a zendesk resource. With the instance client configured, click Connect and approve; the token acts as you. Otherwise pick Zendesk under Others and enter the subdomain, client id and secret for client credentials; Windmill renews the token either way, with read and write scopes by default.
Run your first script
Start with List Tickets or Search Tickets to check the connection, then Create Ticket or Update Ticket.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Update Side Conversation
Set Custom Ticket Fields
Search Help Center
Search Community Posts
Search Articles
Reply to Side Conversation
List Side Conversations
List Articles
Get Side Conversation
Get Article
Create Side Conversation
List View Tickets
List Ticket Comments
Add Ticket Tags
Get Dynamic Content Items by Name
Remove Ticket Tags
Create or Update User
Get Dynamic Content Item
Update Organization
List Macros
List Tickets
Get Macro
List Organizations
List Locales
Create Ticket
List Ticket Fields
Create Organization
Delete Ticket
Search Tickets
Upload Ticket Attachments
Trigger flows from Zendesk
Zendesk is not only a destination. These inbound paths are supported today.
Zendesk webhooks on an HTTP route
Create a Windmill HTTP route with Raw body enabled, then in Admin Center add a webhook (Apps and integrations, then Webhooks) pointing at it: subscribe it to Zendesk events (user, organization, ticket events), or leave it on trigger or automation events and add a Zendesk trigger whose action is Notify webhook. Copy the webhook's signing secret, and verify each delivery in a preprocessor: X-Zendesk-Webhook-Signature must equal base64(HMAC-SHA256(secret, X-Zendesk-Webhook-Signature-Timestamp + raw body)).
Resource type
The shape of the credential every script on this page expects.
zendesk
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| password | string | No | Legacy API-token auth: the API token that goes with username. |
| subdomain | string | Yes | Your account subdomain: `yourcompany` in yourcompany.zendesk.com. |
| token | string | No | OAuth access token. Filled in when you connect with OAuth, using an OAuth client from Admin Center > Apps and integrations > APIs > OAuth clients. When set, username and password are ignored. |
| username | string | No | Legacy API-token auth: agent email followed by `/token` (e.g. `[email protected]/token`). Zendesk deactivates API tokens on April 30, 2027; accounts created after July 28, 2026 can't use them. |
Questions
What happens to API tokens?
Zendesk is retiring them: accounts created after July 28, 2026 can't use them, no account can create new ones after October 27, 2026, and all of them stop working on April 30, 2027. Resources holding username (email/token) and password still work until then; move them to OAuth by connecting the resource again.
There is no Connect button on my instance
On a self-hosted instance, an instance admin has to configure the Zendesk OAuth client in Instance settings first. Until then, connect with client credentials from the Others row of the resource dialog.
What can the token do?
What the scopes allow, within the permissions of the user it acts as: the approving user for an authorization-code connection, the client's creator for client credentials. The default read and write scopes cover every script here; admin-only calls such as dynamic content need an admin user.
Are my credentials stored on the hub?
Never. They live only in your own Windmill workspace, encrypted at rest.