Automate Slack Alerts for Urgent Bugs with n8n Linear Trigger

What This Workflow Does

This workflow listens for new issues in Linear. It checks if the issue is a bug with priority 3 or higher. It sends alerts to a Slack channel only for those urgent bugs. This helps the team respond faster and not miss important problems.

The workflow starts with Linear sending issue data, then a filter keeps just urgent bugs. Next, it formats the bug title to title case. Finally, Slack alerts are sent with links and channel alerts.

Who Should Use This Workflow

This is good for any team using Linear for tracking bugs. If urgent bugs get missed or delayed, this workflow helps by automating notifications. It is also useful for teams wanting to save manual work copying issue details.

Users with basic JavaScript can customize the mock data node or message text. The workflow works well for teams using Slack but can be adapted to others.

Tools and Services Used

• n8n: Automation platform running the workflow.
• Linear API: Provides issue event data.
• Slack API: Receives alert messages.
• JavaScript Code Node: Used to create mock issue data for testing.

Beginner Step-by-Step: How to Use This Workflow in n8n

Importing the Workflow

1. Download the workflow file from this page.
2. Open the n8n editor.
3. Click “Import from File” and select the downloaded workflow.

Configuring Credentials and IDs

1. Open the imported workflow in n8n.
2. Provide your Linear API Key in the Linear Trigger node credentials area.
3. Enter your Linear Team ID in the Linear Trigger node settings.
4. Set your Slack API token in the Slack node credentials.
5. Update the Slack channel name if different from “#important-bugs”.

Testing the Workflow

1. Use the manual trigger to run the workflow and test sending a sample alert.
2. Check Slack to see if the alert shows with the formatted title and clickable link.

Activating for Production

1. Disable the manual trigger and code nodes used for testing.
2. Enable the Linear Trigger node.
3. Activate the workflow to listen for real Linear events.

If you run on your own server, consider using self-host n8n for greater control.

Workflow Inputs, Processing Steps, and Outputs

Inputs

• New or updated issue events from Linear via the Linear Trigger node.
• In testing, mock issue data generated by the Code node.

Processing Steps

• The Filter node checks if the issue priority is 3 or higher and the first label is “bug”.
• The Set node transforms the issue title to title case and sets the issue URL.
• Slack node formats and sends the alert message to the #important-bugs Slack channel.

Outputs

• Slack message mentioning the channel and linking to the urgent bug with a clean title.
• No alerts for non-urgent or non-bug issues.

Customization Ideas

• Replace the Linear Trigger with a Jira Trigger node to watch Jira issues.
• Swap the Slack node with Microsoft Teams for alerts in Teams.
• Change the priority filter to catch lower priority bugs by adjusting priority >= 3 to a lower number.
• Add more details like issue creator or labels in the Slack message text.
• Insert a Code node before the Set node for complex message formatting or extra metadata handling.

Common Issues and Fixes

No nodes triggering on Linear events

Check if the Linear Trigger node is enabled.

Verify API Key is correct under credentials.

Slack message fails to send

Confirm Slack API token is valid.

Check channel name is correct and includes “#” if using name mode.

Filter node passes no data

Look at incoming data structure.

Adjust filter conditions especially on the label path.

Pre-Production Checklist

• Test the Linear webhook connection with credentials.
• Verify Slack API token permissions.
• Run the manual trigger and check for expected Slack messages.
• Confirm filter logic matches your actual issue data.
• Check Slack message formatting for accuracy.
• Backup previous workflows before enabling live triggers.

Deployment Guide

Enable the Linear Trigger node to start live listening.

Disable test nodes to avoid duplicate runs.

Activate the workflow.

Monitor real-time logs for errors.

Use alert steps or emails to get notified on workflow failures.

Summary and Results

✓ Saves time by automating urgent bug detection.

✓ Sends clear Slack alerts with formatted titles and links.

✓ Helps teams respond faster and avoid missed critical bugs.

✓ Easy to test using mock data before going live.

✓ Flexible for other platforms like Jira or Teams.

Code for Mock Issue Data (Example)

This JavaScript code is used in the Code node to simulate a new urgent bug event for testing:

return [{
  json: {
    data: {
      title: "critical bug found in payment gateway",
      priority: 4,
      labels: [{ name: "bug" }],
      url: "https://linear.app/issue/BUG-1234"
    }
  }
}];

Simply copy and paste this code in the Code node to mock urgent bug data.