Critical issues should not wait in a queue. This setup pushes urgent bug reports from your issue tracker into Slack right away so the team can respond fast. It fits product and engineering groups that manage work in Linear and coordinate in Slack.

An event in Linear starts the flow when a new issue appears in a chosen team. A filter checks two things before alerting anyone: the item must be labeled bug and the priority must be 3 or higher. A Set step cleans the title into title case and keeps only the fields needed, including the link to the issue. The Slack step posts a channel mention with a clickable link to the issue. For safe testing, a manual path with mock data lets you validate the message and formatting without touching live records.

Setup is simple. You need a Linear account with access to the right team and a Slack workspace where the bot can post to the target channel. Expect faster triage, fewer missed issues, and clearer handoffs between QA and engineers. It works well for incident triage, on call updates, and high priority bug alerts. You can also swap the trigger or the final message step if your tools change later.

• Linear event trigger listens for new issues in a specific team.
• Filter keeps only items labeled bug with priority 3 or higher.
• Set step formats the title in title case and keeps only title and URL.
• Slack message mentions the channel and links directly to the issue.
• Manual trigger with mock data lets you test end to end safely.
• Simple path layout makes it easy to swap the trigger or the alert app.

• Reduce manual checking of issue queues from hours to instant alerts
• Cut triage time from about 30 minutes to roughly 2 minutes per bug
• Lower missed urgent issues by up to 90% with clear channel mention
• Connect Linear and Slack so teams act without switching tabs
• Handle dozens of new issues per hour with the same team size

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Linear and Slack. See the Tools Required section above for links to create accounts with these services.
3. Open the Linear Trigger node. In the 'Credential to connect with' field, click 'Create new credential' and follow the on screen steps to connect your Linear account. Select the team that should trigger alerts and make sure the resource is set to Issue events.
4. Confirm the trigger scope: choose the correct team or workspace in Linear so only the right issues start the flow. Save the node.
5. Open the Slack node. In the 'Credential to connect with' field, click 'Create new credential' and authorize Slack. Pick the channel where alerts should post, or enter a channel name. Make sure the bot is invited to that channel.
6. Adjust the Filter node if needed. By default it passes only items with label 'bug' and priority 3 or higher. If your team uses a different label or scale, update those values.
7. Click Execute Workflow to test with the Manual Trigger path. The Code node sends mock data to the Filter. If no message appears, loosen the filter for testing, then restore it.
8. Review the Slack message formatting. Edit the text field in the Slack node to change the wording, mentions, or add more fields if needed.
9. Create a real test issue in Linear with label bug and priority 3 or higher to confirm the live trigger. Check that the Slack message includes the correct title and link.
10. Turn off or remove the Manual Trigger and Code nodes once live. Keep the workflow active and monitor the executions for any errors. If alerts fail, verify channel permissions, confirm your Linear team selection, and make sure the credentials are still valid.