Zendesk

Support Subdomain, email and API token

Create and update tickets, users and organizations, and read macros and views, from any Windmill script, flow or app.

Set up in 3 steps

1

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.

2

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.

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

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

View raw schema →
FieldTypeRequiredWhat it is
passwordstringYespassword or api token
subdomainstringYes
usernamestringYesemail 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.