receive linear events and only tickets that need to be classified and update linear
Configured with Filter, HTTP Request, Linear, Linear Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- Integration
- Web / API
- Transform
- Messaging
- AI & models
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Linear Trigger | Trigger | Linear Trigger | See node parameters |
| Only tickets that need to be classified | Routing | Filter | See node parameters |
| Update team | Integration | Linear | update |
| Get all linear teams | Web / API | HTTP Request | POST |
| Set team ID | Transform | Edit Fields | See node parameters |
| Set me up | Transform | Edit Fields | See node parameters |
| Check if AI was able to find a team | Routing | If | See node parameters |
| Notify in Slack | Messaging | Slack | See node parameters |
| Merge data | Transform | Merge | See node parameters |
| OpenAI | AI & models | Open Ai | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
linearApilinearOAuth2ApiopenAiApislackApi
Workflow notes
When does this fire?
When does this fire?
In our setup we have a general team in Linear where we post new tickets to. Additionally, the bug needs to have a certain label and the description needs to be filled. You're of course free to adjust this to your needs 👇
Setup
Setup
- Add your Linear and OpenAi credentials
- Change the team in the
Linear Triggerto match your needs - Customize your teams and their areas of responsibility in the
Set me upnode. Please use the format[Teamname][Description/Areas of responsibility]. Also make sure that the teamnames match the names in Linear exactly. - Change the Slack channel in the
Set me upnode to your Slack channel of choice.
receive linear events and only tickets that need to be classified and update linear
receive linear events and only tickets that need to be classified and update linear
Purpose and structure
This folder contains the receive linear events and only tickets that need to be classified and update linear workflow. Its executable nodes use filter, httpRequest, if, linear, linearTrigger, merge, openAi, set, slack. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Linear Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Filter/0451_Filter_Slack_Update_Webhook.json MIT; preserve source notices.