Classify new bugs in Linear with OpenAI's GPT-4 and move them to the right team
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 10 nodes and runs on Linear events. Along the way it connects Linear, Slack and OpenAI. It also calls api.linear.app over HTTP.
How it runs
Trigger: On Linear events.
- Set me up (Edit Fields (Set)): sets 2 fields: teams, slackChannel
- Only tickets that need to be classified (Filter): keeps only the items that match a condition
- OpenAI: uses OpenAI
- Get all linear teams (HTTP Request): calls api.linear.app (POST)
- Merge: merges the data from its input branches
- Check if AI was able to find a team (If): checks a condition and branches into true / false
- Set team ID (Edit Fields (Set)): sets 1 field: teamId
- Notify in Slack (Slack): uses Slack
- Update team (Linear): update
Services it uses
HTTP calls to: api.linear.app
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Linear Trigger
n8n-nodes-base.linearTrigger - Filter
n8n-nodes-base.filter - Linear
n8n-nodes-base.linear - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Merge
n8n-nodes-base.merge - OpenAI
@n8n/n8n-nodes-langchain.openAi
From the author
Use case When working with multiple teams, bugs must get in front of the right team as quickly as possible to be resolved. Normally this includes a manual grooming of new bugs that have arrived in your ticketing system (in our case Linear). We found this way…