Ticket destination
File AI-drafted issues into Linear in one click
Turn a ranked feedback topic into a Linear issue, with the title, summary, and acceptance criteria drafted by AI from the notes behind it.
Why connect Linear
- Built for fast teams. Go from feedback topic to a Linear issue without the busywork.
- AI-drafted detail. Title, summary, and acceptance criteria written from the real feedback.
- Grounded in the notes. Each issue traces back to the feedback that drove it.
Fix CSV export timeouts on large projects
Multiple customers report exports failing on projects above ~10k rows. Summarized from 12 related notes.
Acceptance criteria
- Exports over 10k rows complete without timing out
- Progress is shown while the file builds
- Failures surface a retry, not a silent error
How it works
- 1
Connect Linear
Add a personal API key and your team ID.
- 2
Pick a topic
Choose a ranked feedback topic to ship.
- 3
Create the issue
FeedbackFlow drafts and files it into Linear instantly.
Prefer the full walkthrough? Read the Linear setup guide.
Before you start
- A Linear account with access to the team you want issues created in. Issues are created as you, so the account you use is the one that will show as the creator on everything filed.
- Permission to create a personal API key, which every Linear user has for their own account under Settings, Security and access, API.
- The team ID for the team that should receive the issues, found in that team's general settings. One connection targets one team.
How to connect Linear to FeedbackFlow
- 1
Create a personal API key
In Linear, open Settings, then Security and access, then API, and create a personal API key. Paste it into the Linear card in your FeedbackFlow project settings. The key inherits your own permissions, so FeedbackFlow can only reach teams you can already reach, and it is stored encrypted rather than kept in plain text.
- 2
Find and enter your team ID
Open Settings, then Team, then General for the team you want issues filed into, and copy the team ID. Paste it into FeedbackFlow. This is what decides where every issue from this connection lands, so if you run several Linear teams, pick the one whose backlog product actually plans from.
- 3
File your first issue to check the wiring
Open a ranked topic and choose to create a Linear issue. FeedbackFlow drafts a title, a description synthesizing the feedback behind that topic, and acceptance criteria, then shows you the draft before anything is created. Confirm it and the issue appears in your team, which is also how you verify the key and team ID are correct.
- 4
Decide who files, and when
Filing is a manual action on a topic, so agree as a team who does it and at what point. Most teams let whoever runs prioritization file the top topics during planning, rather than filing continuously, which keeps the Linear backlog reflecting decisions rather than raw inbound feedback.
The exact Request URL and any values you need to paste are shown on the Linear card inside your project settings, because they are specific to your project. Full Linear setup guide.
What FeedbackFlow writes to Linear
One issue per topic you choose to file, containing the fields below. Nothing is created without you asking for it, existing Linear issues are never modified, and no other part of your workspace is touched.
| Field | What it contains |
|---|---|
| Issue title | Drafted from the topic as a problem statement, not a copy of one customer message |
| Description | A synthesis of the feedback items behind the topic, so the pattern is visible |
| Acceptance criteria | Written from the specific failures customers described |
| Team | The team matching the ID you configured; issues are never filed elsewhere |
What this looks like in practice
A topic rises to the top of the ranked list
You open it and see every piece of feedback behind it, with the count and the requesters attached, rather than the single loudest anecdote. The ranking reflects how many people hit the problem across every source you have connected.
You file it to Linear
FeedbackFlow drafts the issue from all of that feedback at once and creates it in your team, with acceptance criteria grounded in the specific failures customers reported rather than a paraphrase of the topic name.
It enters the cycle
The issue lands in the team your engineers already plan from, carrying enough context that it does not need a follow-up conversation to become actionable. The topic stays in FeedbackFlow with its requesters, so you know who to tell when it ships.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- Issues are created, not synced. Status changes in Linear do not flow back to the topic in FeedbackFlow.
- One team per connection. Issues cannot be routed to different Linear teams based on the content of the feedback.
- Filing is manual by design. There is no automation that creates issues when a topic passes a threshold.
- The connector sets title, description, and acceptance criteria. It does not set project, cycle, estimate, labels, or assignee.
Frequently asked questions
- Does this create Linear issues automatically?
- No. AI ranks the topics and drafts the issue content; you decide which topics become issues. Filing is always an explicit action, which keeps your Linear backlog from filling up with untriaged customer reports.
- What access does the API key give FeedbackFlow?
- A personal API key inherits your own permissions in Linear, so FeedbackFlow can reach exactly what you can reach and nothing more. In practice it is used only to create issues in the team ID you configured. The key is encrypted at rest with AES-256-GCM and never returned to the browser after you save it.
- Can I file into different Linear teams?
- Not from one connection. Each connection targets a single team ID and every issue goes there. If you need feedback split across teams, the practical route is to file into one team and move issues from there, since Linear handles that better than a feedback tool routing on its own guesses.
- Does it set labels, projects, or estimates?
- No. The connector writes the title, description, and acceptance criteria, and leaves everything else to your team's own conventions. Labels, projects, cycles, and estimates are decisions your process owns, and guessing at them would create cleanup rather than save it.
- What happens to the topic in FeedbackFlow after I file it?
- It stays in FeedbackFlow with the feedback items behind it intact, so the record of who asked survives. The link is one-way: closing the Linear issue does not close the topic, and the requesters attached to it remain available for when you want to tell people the work shipped.
Connect Linear today
Free plan. No credit card. Live in 2 minutes.