---
title: "More support desks"
url: "/help/buuk/support-desks"
updated: "2026-10-25T16:58:19.085Z"
---
# More support desks

Beyond Intercom and Zendesk, Buuk connects the rest of the support desk market with one pattern: connect with OAuth or an API credential, read conversations and tickets, cluster repeated asks, and file suggestions — never publish.

Crisp Chat joins the same group, connecting with a Website ID plus API details to turn live chats into drafts.

## Connections, provider by provider

| Provider | Connects with | What Buuk reads |
| --- | --- | --- |
| Freshdesk | Your subdomain plus an API key | Tickets |
| Help Scout | OAuth app token, or a Mailbox API token | Conversations |
| Zoho Desk | OAuth, with your data center (com, eu, in, au, or jp) | Tickets |
| BoldDesk | Your portal URL plus an API key | Tickets |
| HubSpot | OAuth, or a private app token with tickets read access | Tickets |
| Fernand | An API key | Conversations |
| Missive | An API token | Shared-inbox conversations |
| Drift | OAuth, or an access token | Chats |
| Chatwoot | Instance URL (cloud or self-hosted), account ID, and a user access token | Conversations |
| Chatbase | An agent ID plus an API key | Chatbot conversations |
| tawk.to | Property ID plus a webhook secret — webhook push or the REST API | Chats and tickets |

Credentials are verified at connect time where the provider allows it, so a wrong key fails on the spot instead of surprising you at the first sync.

## Where each credential lives

| Provider | Exact location in their admin |
| --- | --- |
| Freshdesk | Avatar menu (top right) → Profile settings → API Key — revealed after a reCAPTCHA. The domain is the your-company part of yourcompany.freshdesk.com. |
| Help Scout | For the one-click OAuth just approve the consent at secure.helpscout.net. For a token: Manage → Profile icon → My Apps → create or copy the Mailbox API 2.0 token. |
| Zoho Desk | Connect with OAuth — first pick the data center from your Zoho login domain (zoho.com, .eu, .in, .au, .jp), then approve Desk read access. Desks.tickets read is the only permission requested. |
| BoldDesk | Portal URL from your browser bar; API key from Agent profile → Personal Settings → API Keys → Create. |
| HubSpot | OAuth approves in one click. For a private-app token: Settings (gear) → Integrations → Private Apps → Create private app → name it Buuk → Tickets scope with read → copy the token. |
| Fernand | Settings → Integrations → API key → copy. |
| Missive | Settings → API → Create token — choose read scopes for the shared inbox. |
| Drift | OAuth approves through dev.drift.com. For a token: Aria → Settings → App Settings → OAuth & API tokens → generate authorized OAuth token. |
| Chatwoot | Profile settings → Access token (copy). Account ID shows under profile/workspace switcher; instance URL is where you sign in (app.chatwoot.com or your self-hosted host). |
| Chatbase | Agent picker → your agent → Agent settings → Agent ID; Workspace → Settings → API Keys → create. |
| Crisp Chat | Settings → Workspace settings → Website ID and API Keys — create a token pair; the key half is shown once. |
| tawk.to | Administration → Overview → Property ID (not the widget ID); Administration → Webhooks → Create webhook → copy the secret. |

## The shared flow

1. Connect from the **Integrations** card. OAuth providers redirect through their site; token providers open a form with a hint about where each key lives.
2. Conversations import on a schedule and become draft material whenever a conversation is really a doc gap.
3. A background pass reviews the last `30` days of conversations and clusters themes. Recurring matters: one ticket is a draft candidate, ten tickets are an article.
4. Themes become suggested updates in [**Suggestions**](./suggested-updates), each with an evidence drawer showing the actual threads behind the signal.

> [!NOTE]
> Starter holds two integration slots — GitHub plus one support source. Growth connects the full catalog.

## Troubleshooting

**The provider screen asks for admin approval**

Several connectors (HubSpot private apps, Zoho OAuth, Drift, Chatwoot policies) require an administrator to approve the app on the provider side. The screen names the requirement — forward it to whoever administers that tool. Connecting from Buuk itself only needs dashboard editor access.

**Syncs stop after a credential change**

API keys and tokens expire or get revoked on the provider side. Reconnect from the integration card; re-authenticating an existing connection never consumes a new slot.

**A ticket that obviously needs docs did not appear**

The theme scan looks back 30 days and clusters conversations, so a single one-off ticket may not rate a suggestion on its own. Draft the article directly from Ask Buuk instead.

## Related

- The two dedicated pages: [Intercom](./intercom) and [Zendesk](./zendesk).
- Email instead of tickets: [Email inboxes](./email-inboxes).
- Social and chat channels: [Community and social channels](./community-channels).
- The full catalog: [Integrations overview](./connect-integrations).