Novalink

Use case

GitHub issue triage with Linear and Slack

Updated September 19, 2026

New GitHub issues need the same three questions answered: is it a duplicate, is it a real bug, and who should know. This workflow answers them with an agent and three connected apps, and you can draft it from one sentence.

Nodes used:manual_triggeragentconnector_actionifoutput

Draft it from a sentence

With GitHub, Linear and Slack connected, open Generate with AI on the Workflows page and describe it:

Description
When a GitHub issue comes in, check it against open issues for duplicates.
If it is a real bug, create a Linear issue in the Platform team.
Otherwise post a short summary to #support in Slack.

Claude picks the connector actions by their real ids, and the preview shows the graph below before you create it. See generating workflows.

How the workflow runs

  1. The trigger carries the issue: title, body, and repository.
  2. A triage agent has GitHub · List issues as a tool, reads the open issues, and returns duplicate, is_bug and a one-line summary as structured output.
  3. An If node sends bugs to Linear · Create issue and everything else to Slack · Post message.
  4. The Output node records which path fired and what was created.

Fill the actions with templates

Linear · Create issue
Team key: PLAT
Title: {{ trigger.title }}
Description: {{ nodes.triage.output.structured.summary }}
Is bug · If condition
nodes.triage.output.structured.is_bug

What the workflow never sees

Build it on the canvas

Create a free account, describe the workflow or wire it yourself, and run it in the browser.