---
title: "Integrations overview"
url: "/help/buuk/connect-integrations"
updated: "2026-11-13T16:22:22.026Z"
---
# Integrations overview

Open **Integrations** in the dashboard to connect the tools your team already uses. Every connector reads the team-level signals a source holds — support conversations, releases and code changes, shared inboxes, project boards — and turns them into suggestions or source material for drafts.

![Integrations: connected tools with their last sync, and the available integrations filtered by Support, Product, and Codebase.](/api/media/assets/3e16ea64-7671-43f7-a22a-0e71d329dbf5)

You can start with one source and add more later. Each card lists what Buuk needs — usually OAuth sign-in, sometimes an API or bot token — and you can disconnect anytime from the same page.

> [!NOTE]
> Nothing auto-publishes. A connection feeds [Suggestions](./suggested-updates) with material for you to accept, edit, or dismiss. Publishing stays with your team.

## Codebase sources

| Provider | What Buuk reads |
| --- | --- |
| [GitHub](./github) | Releases become changelog entries, help articles stay in sync with the repo, and code changes surface as doc suggestions. |
| [Mirror](./mirror) | Clones any Git repo — GitHub, GitLab, Gitea, or self-hosted — and scans it into draft docs. |
| [Confluence](./confluence-and-google-drive) | Pages serve as source material for help article drafts. |
| [Google Drive](./confluence-and-google-drive) | Google Docs serve as source material for help article drafts. |
| Databricks | Notebooks serve as source material for help article drafts. |

## Support sources

| Provider | What Buuk reads |
| --- | --- |
| [Intercom](./intercom) | Support conversations become help article drafts. |
| [Zendesk](./zendesk) | Tickets become help article drafts. |
| [Freshdesk](./support-desks) | Tickets become help article drafts. |
| [Help Scout](./support-desks) | Conversations become help article drafts. |
| [Zoho Desk](./support-desks) | Tickets become help article drafts. |
| [BoldDesk](./support-desks) | Tickets become help article drafts. |
| [HubSpot](./support-desks) | Tickets become help article drafts. |
| [Chatwoot](./support-desks) | Conversations become help article drafts. |
| [Missive](./support-desks) | Shared-inbox conversations become help article drafts. |
| [Fernand](./support-desks) | Conversations become help article drafts. |
| [Crisp Chat](./support-desks) | Live chats become help article drafts. |
| [tawk.to](./support-desks) | Chats become help article drafts. |
| [Chatbase](./support-desks) | Chats become help article drafts. |
| [Drift](./support-desks) | Chats become help article drafts. |
| [Slack](./slack) | Mention Buuk in a channel to file a suggestion as it happens, or import threads for drafts. |
| [Discord](./community-channels) | Server messages become drafts — you choose the guild. |
| [Microsoft Teams](./community-channels) | Team messages become help article drafts. |
| [Gmail](./email-inboxes) | Support emails become help article drafts. |
| [Outlook](./email-inboxes) | Support emails become help article drafts. |
| [WhatsApp Business](./community-channels) | Customer messages become help article drafts. |
| [X (Twitter)](./community-channels) | Mentions of your handle become help article drafts. |
| [Facebook](./community-channels) | Posts and Messenger chats become help article drafts. |
| [Instagram](./community-channels) | Comments become help article drafts. |

Repeated support themes rise to the surface either way: drafting an article that answers them, and clustering them into product insights in Reporting. The connection itself just watches — review happens in Suggestions.

## Product sources

| Provider | What Buuk reads |
| --- | --- |
| [Linear](./product-sources) | Issues and feedback become drafts, and outcomes are reported back to the issue. |
| [Trello](./product-sources) | Cards become help article drafts. |
| [Featurebase](./product-sources) | Posts become help article drafts. |

## Plans

Starter includes two integration slots: GitHub plus one support source. Growth connects the full catalog in the tables above. See [Plans and billing](./plans-and-billing) for the numbers.

> [!TIP]
> Start with GitHub and the desk your team answers in most. Those two sources usually produce the first week of useful suggestions.

## Related

- Where connections land their material: [Suggested updates](./suggested-updates).
- Put the review pipeline on a schedule: [Automations](./automations).
- React to changes from your own systems instead: [Webhooks](./webhooks).
- How many sources each plan allows: [Plans and billing](./plans-and-billing).