Skip to main content

Automatic issue routing in Linear with GPT-4-mini classification

Workflow preview

Workflow preview
100%
Automatic issue routing in Linear with GPT-4-mini classification preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

How it works This workflow automatically classifies and routes new or updated Linear issues using AI. When an issue is created or updated, its title and description are analyzed by an OpenAI powere...

Best for

  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.if, n8n-nodes-base.lineartrigger, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.switch, n8n-nodes-base.linear, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.

Original n8n.io source

1.1 Workflow description

Title
Automatic issue routing in Linear with GPT-4-mini classification
Workflow name
Automatic issue routing in Linear with GPT-4-mini classification

How it works

This workflow automatically classifies and routes new or updated Linear issues using AI. When an issue is created or updated, its title and description are analyzed by an OpenAI-powered classifier. The workflow then determines the correct team, routes the issue through the right path, and updates it in Linear. This ensures accurate, consistent triaging and removes the need for manual assignment.

Step-by-step

1. Trigger and validation

  • Linear Trigger – Detects new or updated issues in Linear.
  • Filter New Issues Only – Ensures the issue has a valid title.
  • If (Create or Update) – Confirms the action is either create or update.

2. AI classification

  • OpenAI Chat Model – Provides language model capabilities for classification.
  • AI Agent (Bug Classifier) – Uses issue title and description to assign a team ID.

3. Routing logic

  • Engineering Router – Checks if classification output is Engineering.
  • Product Router – Checks if classification output is Product.
  • Design Router – Checks if classification output is Design.
  • Default Router – Fallback if no match is found.

4. Update Linear issue

  • Assign to Engineering – Updates team assignment in Linear.
  • Assign to Product – Updates team assignment in Linear.
  • Assign to Design – Updates team assignment in Linear.
  • Assign to Default – Assigns to fallback team if no match.

Why use this?

  • Automates issue triage, eliminating manual team assignment.
  • Speeds up bug resolution by instantly routing to the right team.
  • Ensures consistency in bug categorization using AI-driven analysis.
  • Scales effortlessly with growing issue volume.
  • Reduces human error in issue management.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - 📋 Filter New Issues Only

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 2 - 🔔 Linear Trigger

Type / Role
n8n-nodes-base.linearTrigger - linearTrigger
Config choices
Version 1

Block 3 - ⚖️ If (Create or Update)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 4 - 🤖 AI Agent (Bug Classifier)

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.2

Block 5 - 🔀 Engineering Router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 6 - 🔀 Product Router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 7 - 🔀 Design Router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 8 - 🔀 Default Router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 9 - 🛠️ Assign to Engineering

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 10 - 📦 Assign to Product

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 11 - 🎨 Assign to Design

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 12 - 📂 Assign to Default

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 13 - 🧠 OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 14 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automatic issue routing in Linear with GPT-4-mini classification
Complexity advanced
Nodes 17
Categories AI Summarization
Author Avkash Kakdiya
Published 23 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8845/8845.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automatic issue routing in Linear with GPT-4-mini classification do?

How it works This workflow automatically classifies and routes new or updated Linear issues using AI. When an issue is created or updated, its title and description are analyzed by an OpenAI powere...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your AI Summarization use case.