Integration · Updated
Linear integration for usedocs
Product decisions and feature details live in Linear issues long before anyone writes them up for customers. The Linear integration catches them there: tag @usedocs or label the issue docs, and the help article draft is waiting when the work ships.
TL;DR
Short answer
The usedocs Linear integration turns issues into help article drafts. Mention @usedocs in a comment on an issue, or complete an issue that has the docs label, and usedocs drafts the article from the issue's description and comments. It replies on the issue with a link, and the draft waits in your review queue. Nothing publishes without approval.
Overview
usedocs keeps a SaaS help center accurate from your code and your customers, and Linear adds the place where your team plans the work. After you connect Linear, two things start a draft. Mention @usedocs in a comment on any issue, and usedocs reads the issue's title, description, and comments and drafts the help article it needs. Or add the docs label to an issue, and when the issue is completed, usedocs drafts the article then, so the docs are ready around the time the feature ships. Either way, usedocs replies on the issue from its Linear app with a link to the draft, so the whole team can see the docs are in hand. Drafts arrive with a reader facing title, a description, and a suggested collection, and wait in the same review queue as edits from merged pull requests and drafts from customer questions. One draft per issue: a second mention while a draft is open doesn't create another.
What this integration does
Drafts on @usedocs mentions
Mention @usedocs in a comment and get a draft written from the issue and its discussion.
Drafts when docs issues finish
Completing an issue labeled docs starts a draft, so documentation lands with the feature.
A reply on the issue
usedocs comments on the issue with a link to the draft, so nobody wonders whether the docs are done.
One review queue
Linear drafts wait next to edits from merged pull requests and drafts from customer questions.
Setup
Open Integrations In the usedocs dashboard, open Integrations and find Linear under Docs and code.
Connect your Linear workspace Approve the usedocs app in Linear. It can read issues and post comments, so it can reply with draft links.
Add a docs label Create a label named docs in Linear, if you don't have one, for issues whose completion should produce a help article.
Mention or label an issue Comment @usedocs on an issue, or complete an issue labeled docs, then review the draft from the link usedocs posts.
Limits and plan notes
- Drafts are proposed, never published without approval.
- One open draft per issue; mention again after the draft is approved or dismissed for a new one.
- Drafts count toward the AI drafts allowance on Growth under fair use; if drafts are paused, usedocs says so on the issue.
- The issue's title, description, and comments are the source, so a thin issue produces a thin draft.
Not for you if
Skip this if your team doesn't plan work in Linear, or if issues rarely describe what changes for customers. The GitHub integration covers most teams on its own, proposing edits from the merged pull requests themselves.
FAQ
What does the usedocs Linear integration do?
It drafts a help article from a Linear issue when you mention @usedocs in a comment or complete an issue labeled docs, then replies on the issue with a link to the draft.
Does usedocs publish anything automatically from Linear?
No. Every draft waits in the review queue for approval.
What does usedocs read from the issue?
The issue's title, description, and comments, not other issues or projects.
Do I need the GitHub integration too?
No, but they work well together: Linear catches docs at planning time, GitHub proposes edits when code merges.
Can I control which issues create drafts?
Yes. Only issues where someone mentions @usedocs, or completed issues labeled docs, start a draft.