FeaturedDev & IT Ops#Linear#Bug Intake#Support#Engineering#Triage

Linear Bug Intake Triage

Turn a support or QA bug report into a prioritized Linear issue with an AI-written title and description.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Linear#Bug Intake#Support#Engineering#Triage

Click a node to select it — same as the Heym editor; the panel shows its settings.

4 nodes · Free & source-available

Linear Bug Intake Triage

Route incoming bug reports into Linear with a consistent issue shape. The workflow accepts a short report, asks an LLM to draft a concise ticket, creates the Linear issue, and returns the created issue URL.

What this workflow does

  1. BugReport captures the report text and source
  2. DraftLinearTicket writes a Linear-ready title, description, and priority
  3. CreateLinearIssue creates the issue in your Linear team
  4. IssueReceipt returns the identifier and URL from Linear

Use cases

  • Support escalation to engineering
  • QA bug intake from forms or webhook payloads
  • Internal feedback that should become tracked product work

Setup

Create a Linear credential first. Set Linear Team ID on CreateLinearIssue to your team UUID, then connect an LLM credential on DraftLinearTicket. Replace the sample input with your support inbox, QA form, Slack trigger, or webhook source when you move it into production.

Notes

Linear priority values are 0 to 4: 0 means no priority, 1 urgent, 2 high, 3 normal, and 4 low. Keep the LLM schema strict so downstream Linear fields stay predictable.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym