---
title: "Zendesk"
url: "/help/buuk/zendesk"
updated: "2026-10-25T16:58:19.085Z"
---
# Zendesk

Connect Zendesk and recent tickets become material for help articles. Each sync reads up to `50` of the newest tickets, with subject, description, and status.

## Step by step — OAuth

Open **Integrations** and pick **Zendesk**. A short form appears before the redirect asking for your **Zendesk subdomain** — save it once and it is reused for every sync.

1. **Find your subdomain**
   Look at the URL you use for your help desk: `https://your-company.zendesk.com`. The part before `.zendesk.com` — **your-company** — is the subdomain.

2. **Paste the subdomain and sign in on the redirect**
   Buuk opens an authorization page under `your-company.zendesk.com`. If you are not signed in yet, sign in with the Zendesk account that can see your support tickets.

3. **Review and approve the prompt**
   Zendesk asks whether to allow access and shows the permission being granted — read access. Press **Allow**.

4. **Back in Buuk**
   The card flips to connected. The first sync reads the newest tickets, and the theme scan runs over the last 30 days in the background.

## Connecting with an API token instead

**The card shows an email and token field**

That happens when this deployment has no Zendesk OAuth client configured. Instead of the redirect, generate an API token:

1. In Zendesk open **Admin Center** (the four-square icon, top right of your help desk).
2. Go to **Apps and integrations → APIs → Zendesk API**.
3. In the **API tokens** tab press Add API token. Copy the token — Zendesk shows it exactly once.
4. Back in Buuk enter your Zendesk account email (the one that signed in) and paste the token, then press Connect with token.

The email and token must belong to the same Zendesk account — Buuk uses them as a pair for basic auth.

## What it creates

Tickets land in the same pipeline as Intercom: drafts for one-off documentation gaps, and a recurring-subject scan over the last `30` days that turns themes into [suggested updates](./suggested-updates). A ticket wave about one feature usually means the article needs a section, and the suggestion says so.

> [!NOTE]
> Zendesk also carries widget escalations on deployments that use them — a chat that ends with the reader insisting on a human can open a ticket in your connected subdomain.

## Troubleshooting

**Sync fails with not configured**

The stored subdomain is missing or invalid. Reopen the Zendesk card, re-enter the subdomain your help desk really uses, and reconnect.

**Authorization errors after a password or token change**

Token rotation cuts stored credentials off. Reconnect from the same card — re-authenticating an existing connection does not consume a new integration slot.

## Related

- The other enterprise desk: [Intercom](./intercom).
- Freshdesk, Help Scout, and friends: [More support desks](./support-desks).
- The queue everything lands in: [Suggested updates](./suggested-updates).
- The full catalog: [Integrations overview](./connect-integrations).