Intercom to Linear — Linear's integration links, Jetson decides
Jetson reads your Intercom conversations, classifies each as bug or feature (including Fin-handled threads), and files Linear issues with customer quotes, reproduction context, and suggested code files. Deduplicated against open issues, routed to the right team.
How it works
Connect Intercom
Connect with Intercom OAuth, scoped to the inboxes you pick. Read-only — Jetson never replies or modifies conversations.
Jetson classifies every conversation
Bugs, feature requests, and noise separated automatically. Deduplicated against open issues, priority inferred from signals like affected-customer count and plan tier.
Linear issues land in Triage
Issues land in Triage (or Backlog) by default — never directly into your active cycle. Your sprint stays yours; engineering reviews what came in on their own schedule.
What an auto-created Linear issue looks like
Title
Export button fails with 500 on large dashboards
Verbatim customer quote
"I clicked Export as CSV and got a 500 error. Tried twice — same result. We need this for our investor meeting tomorrow."
Affected customers
4 reporters · combined MRR $8.4k
Suggested files
src/routes/api/export/+server.ts src/lib/exporters/csv.tsBack-link to Intercom
Original inbox conversation with full customer context
It reads like an issue your best support lead would have filed — except they never had to.
Why not just use Zapier?
Zapier is plumbing. Jetson is triage. They solve different problems.
Zapier Zap
- Fires on every new conversation — your issue tracker fills with noise
- No classification — password resets and how-to questions become issues
- No deduplication — five reports of the same bug become five issues
- Raw message body pasted into issue — engineers decode on their own
- Breaks quietly when schemas change; you debug in Zap history
Jetson
- Classifies first — only real bugs and feature requests reach Linear
- Deduplicates against open issues — one issue, N linked customers
- Structured body: quotes, affected-customer count, suggested files, back-links
- Linear-native integration — OAuth workspace install, not brittle tokens
- Priority inferred from conversation signals, not pushed into your cycle
Built for Intercom + Linear specifically
Fin-handled threads still become issues
Intercom Fin resolves tier-1 support without a human. Jetson reads those threads too — so bugs surfaced via Fin conversations don't silently disappear. The classifier runs on every conversation, regardless of who (or what) replied.
Lands in Triage, never in your active cycle
Auto-created Linear issues default to Triage or Backlog — engineering reviews them on their own cadence. Your current cycle stays yours.
Customer context from Intercom travels with the issue
Plan tier, MRR, account ID, and custom attributes from Intercom land in the Linear issue body — so PMs can prioritize by revenue impact, not just ticket count.
Intercom note: Jetson classifies conversations end-to-end — including threads Intercom Fin resolved without a human touch. Bugs surfaced in Fin-handled conversations still become work items.
Frequently asked questions
Other integrations
Help Scout to GitHub
Turn Help Scout conversations into GitHub issues automatically. Customer quotes, reproduction context, and suggested code files — no Zapier rules to maintain.
Help Scout to Linear
Turn Help Scout conversations into Linear issues automatically. Classified, deduplicated, and engineering-ready — with customer quotes and reproduction context. Not Zapier, not Linear's manual Customer Requests.
Intercom to GitHub
Turn Intercom conversations into GitHub issues automatically — including Fin-handled threads. Customer quotes, reproduction context, and suggested code files. No Zapier rules to maintain.
Stop copy-pasting support tickets into Linear
Connect Intercom and Linear in under two minutes. Jetson handles the triage.