---
title: "Linear, Trello, and Featurebase"
url: "/help/buuk/product-sources"
updated: "2026-10-25T16:58:19.085Z"
---
# Linear, Trello, and Featurebase

Product connectors answer a different question than support desks: what should the docs explain next, according to the people building and requesting it? Linear, Trello, and Featurebase all flow into the same background scan as the support sources, so their signals can become [suggested updates](./suggested-updates).

## Linear

Issues and their feedback become draft material. Connect with OAuth, or paste an API key from **Linear → Settings → API → Personal API keys** when your deployment has no Linear OAuth app.

### Step by step — OAuth

1. **Connect and sign in**
   Press Connect and Linear’s sign-in appears. Use the account whose workspace holds the issues you want Buuk to learn from. A single Linear user can authorize the app for themselves; nothing is required on the workspace-admin side.

2. **Approve the read permission**
   Linear lists
   
   access to issues, projects, comments, and labels on that workspace. Press
   
   .

3. **Back in Buuk**
   The card connects and the first sync pulls recent issues. Issues that read like bug reports get tagged Product bug rather than doc gap.

### Step by step — API key

1. **Create the key in Linear**
   Open
   
   (linear.app → your avatar → Workspace settings → API). Press
   
   , label it Buuk, and copy the
   
   value — shown once.

2. **Paste in Buuk**
   Paste the key into the token field on the Linear card and press Connect with token. The key carries your personal access level, so connect with an account that can read the teams whose issues matter.

Issues that read like bug reports are tagged Product bug rather than doc gap, so you can tell documentation problems from defects without opening the issue.

> [!TIP]
> The feedback loop is the reason to connect Linear: when a fix linked to an issue ships and an article update lands, Buuk measures reader demand before and after, and reports the outcome on the issue itself — automatically, once, about two weeks after the fix.

That outcome comment shows the thumbs-down counts before the fix, the counts after, and how much demand the change retired — so the team sees whether the doc work closed the loop.

## Trello

Cards move into the same draft pipeline. Connect by pasting a token authorized with your Power-Up API key, and card titles and descriptions become draft material the background scan can use.

### Step by step

1. **Approve on trello.com**
   Pressing Connect opens trello.com’s approval screen showing the
   
   power-up and the scopes
   
   , with expiration
   
   . Sign in with the Trello account (or team) whose boards carry product work, then press
   
   .

2. **Nothing to copy**
   Trello hands the token back to Buuk in the same redirect — you do not copy or paste anything. Back in Buuk the card shows connected.

3. **If connect skips the redirect**
   On deployments without the platform key the card shows a token field instead. Ask your Buuk admin for the Power-Up API key, open
   
   , press Allow, and paste the returned token into the field.

## Featurebase

Connect with an API key from **Featurebase → Settings → API keys**. Posts from your board — feature requests, bugs, upvotes — become draft material, and the key is verified at connect time so a wrong one fails immediately.

### Step by step

1. **Create the key in Featurebase**
   In your Featurebase dashboard open
   
   (under the advanced/API section) and press
   
   . Copy the
   
   value — shown once.

2. **Paste in Buuk**
   Paste the key on the Featurebase card and press Connect. Buuk verifies it against your board on the spot; a wrong key fails immediately rather than at the first sync.

Featurebase and Linear are searched separately from support tickets as product signals, which keeps feature asks from drowning in ticket noise when drafts research demand.

## Plan

Each connection uses an integration slot: Starter includes GitHub plus one support source, and Growth connects the full catalog — see [Plans and billing](./plans-and-billing).

## Troubleshooting

**Linear stops syncing after key rotation**

Paste the new key from the integration card. Re-authenticating an existing connection does not consume a new slot.

**No outcome comment ever appeared on an issue**

The comment posts about two weeks after an applied fix goes live, on suggestions whose draft actually came from that Linear issue. It never posts twice and does nothing for issues that were never linked to a suggestion.

## Related

- Where these signals are reviewed: [Suggested updates](./suggested-updates).
- Code-side sources: [GitHub](./github) and [Code mirrors](./mirror).
- Support-side sources: [More support desks](./support-desks).
- The full catalog: [Integrations overview](./connect-integrations).