How to connect Linear and Slack

Step 1: Create a new workflow
Step 2: Add and configure nodes
Step 3: Connect
Step 4: Customize and extend your integration
Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Linear and Slack integration: Create a new workflow and add the first step

Step 2: Add and configure Linear and Slack nodes

You can find Linear and Slack in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure Linear and Slack nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Linear and Slack integration: Add and configure Linear and Slack nodes

Step 3: Connect Linear and Slack

A connection establishes a link between Linear and Slack (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

Linear and Slack integration: Connect Linear and Slack

Step 4: Customize and extend your Linear and Slack integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Linear and Slack with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Linear and Slack integration: Customize and extend your Linear and Slack integration

Step 5: Test and activate your Linear and Slack workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Linear to Slack or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

Linear and Slack integration: Test and activate your Linear and Slack workflow

Customer Support Channel and Ticketing System with Slack and Linear

This n8n workflow demonstrates how to create a really simple yet effective customer support channel and pipeline by combining Slack, Linear and AI tools.

Built on n8n's ability to integrate anything, this workflow is intended for small support teams who want to maximise re-use of the tools they already have with an interface which is doesn't require any onboarding.

Read the blog post here: https://blog.n8n.io/automated-customer-support-tickets-with-n8n-slack-linear-and-ai/

How it works

The workflow is connected to a slack channel setup with the customer to capture support issues.
Only messages which are tagged with a "✅" reaction are captured by the workflow. Messages are tagged by the support team in the channel.
Each captured support issue is sent to the AI model to classify, prioritise and rewrite into a support ticket.
The generated support ticket is uploaded to Linear for the support team to investigate and track.
Support team is able to report back to the user via the channel when issue is fixed.

Requirements

Slack channel to be monitored
Linear account and project

Customising this workflow

Don't have Linear? This workflow can work just as well with traditional ticketing systems like JIRA.

Nodes used in this workflow

Popular Linear and Slack workflows

Customer Support Channel and Ticketing System with Slack and Linear

This n8n workflow demonstrates how to create a really simple yet effective customer support channel and pipeline by combining Slack, Linear and AI tools. Built on n8n's ability to integrate anything, this workflow is intended for small support teams who want to maximise re-use of the tools they already have with an interface which is doesn't require any onboarding. Read the blog post here: https://blog.n8n.io/automated-customer-support-tickets-with-n8n-slack-linear-and-ai/ How it works The workflow is connected to a slack channel setup with the customer to capture support issues. Only messages which are tagged with a "✅" reaction are captured by the workflow. Messages are tagged by the support team in the channel. Each captured support issue is sent to the AI model to classify, prioritise and rewrite into a support ticket. The generated support ticket is uploaded to Linear for the support team to investigate and track. Support team is able to report back to the user via the channel when issue is fixed. Requirements Slack channel to be monitored Linear account and project Customising this workflow Don't have Linear? This workflow can work just as well with traditional ticketing systems like JIRA.

Send alert when data is created in app/database

This template shows how you can take any event from any service, transform its data and send an alert to your desired app. Specifically, this example monitors a Linear project for new bug submissions. Then it only sends a Slack notification to a channel if a new bug is urgent. You can swap the Linear trigger for another Task Management app such as Jira or Asana; or an entirely different usecase. Setup instructions are located inside the workflow template.

Classify new bugs in Linear with OpenAI's GPT-4 and move them to the right team

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 too time-consuming. That's why we built this workflow. What this workflow does This workflow triggers every time a Linear issue is created or updated within a certain team. For us at n8n, we created one general team called Engineering where all bugs get added in the beginning. The workflow then checks if the issue meets the criteria to be auto-moved to a certain team. In our case, that means that the description is filled, that it has the bug label, and that it's in the Triage state. The workflow then classifies the bug using OpenAI's GPT-4 model before updating the team property of the Linear issue. If the AI fails to classify a team, the workflow sends an alert to Slack. Setup Add your Linear and OpenAi credentials Change the team in the Linear Trigger to match your needs Customize your teams and their areas of responsibility in the Set me up node. Please use the format Teamname. Also, make sure that the team names match the names in Linear exactly. Change the Slack channel in the Set me up node to your Slack channel of choice. How to adjust it to your needs Play around with the context that you're giving to OpenAI, to make sure the model has enough knowledge about your teams and their areas of responsibility Adjust the handling of AI failures to your needs How to enhance this workflow At n8n we use this workflow in combination with some others. E.g. we have the following things on top: We're using an automation that enables everyone to add new bugs easily with the right data via a /bug command in Slack (check out this template if that's interesting to you) This workflow was built using n8n version 1.30.0

Build your own Linear and Slack integration

Create custom Linear and Slack workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.