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

Connect Intercom and support conversations become help article material. Each sync reads recent conversations — the most recently updated first, up to `50` per page — including the admin and bot replies that sit between the customer messages, not just the first ask.

## Step by step — OAuth

Open **Integrations** and pick **Intercom**, then press **Connect**. OAuth is the normal path.

1. **Confirm you are an admin of the Intercom workspace**
   Intercom only shows the authorization screen to workspace administrators — agents cannot install apps. If connecting is not possible ask a workspace admin to do it.

2. **Sign in to the right workspace**
   Buuk redirects you to `app.intercom.io`. If you are signed in to more than one Intercom workspace, check the workspace name shown on the consent screen — the one you are signed into at that moment is the one that gets connected. Switch workspaces in Intercom first if needed.

3. **Approve the access prompt**
   The consent screen lists what Buuk will read: conversations, and the users and companies behind them. Deployments with widget escalations also ask for conversation-write permission so a chat can be handed to a human. Press **Authorize access**.

4. **Back in Buuk**
   The card flips to connected and the first sync pulls recent conversations immediately. Imported threads become draft material in [Suggestions](./suggested-updates).

## Connecting with an access token instead

**The card shows an access-token field**

That happens when this deployment has no Intercom OAuth app configured. Instead of the redirect, generate a long-lived access token yourself:

1. In Intercom, open your workspace avatar menu and choose **Developer Hub (or Buddy menu → Show Developer Hub)**.
2. Press **Create App**, name it Buuk, and create it.
3. Open the app's **Authentication** page and create an access token with at least **Read conversations** and **Read users and companies** scopes.
4. Copy the token and paste it into the token field on the Buuk card, then press Connect with token.

For self-hosted deployments that use their own Intercom OAuth app: tick **Use OAuth** on the app's Authentication page and add your Buuk host's redirect URL — `/api/integrations/intercom/callback` appended to your app domain.

Only editors can connect, and the card disconnects from the same page.

## What it creates

Imported conversations feed article drafts. A background pass then reviews conversations from the last `30` days and clusters them into themes. A theme that stands on its own becomes a suggested update you accept, edit, or dismiss in [**Suggestions**](./suggested-updates).

Deeper demand shows up on individual pages: a run of not-helpful feedback on an article can match one of these themes, so the suggestion points at the page that needs rewriting.

> [!NOTE]
> Nothing auto-publishes. Drafts and suggestions wait for an owner or editor, always.

## Troubleshooting

**Nothing synced**

Check that the credential can read conversations — a token created without conversation access imports nothing. Reconnect from the card if the token was rotated.

**I never see the authorization screen**

Intercom only lets workspace administrators authorize apps. If you are an agent, ask an admin to connect once from the card — the connection then serves the entire workspace.

**A sync failed but the connection still shows connected**

Rate-limited and transient API errors are treated as temporary on purpose; the next sync retries rather than breaking the connection.

## Related

- The sibling desk page: [Zendesk](./zendesk).
- Every other support desk: [More support desks](./support-desks).
- Reviewing what arrives: [Suggested updates](./suggested-updates).
- Plan slots: [Plans and billing](./plans-and-billing).