Pipelines

Today, Linear.
Tomorrow, you tell us.

A pipeline is the destination for classified signal. The point is you never log into NVSBL to 'check for new signal' — it shows up where your work already happens. We launched with Linear because that's where most of the product teams using NVSBL already triage tickets. Every destination after Linear is shipped by user vote, with the option to ask us for a custom build at any time.

Live now

Linear

Each classified signal becomes a Linear issue, in the team and project of your choice.

Title
Generated from the signal, kept human-readable.
Description
The original quote, the HN source URL, the classification label, the confidence score, and a short rationale ('classified as feature request because…').
Labels
Configurable defaults per classification.
Assignee and priority
Configurable defaults; can be overridden per classification.
Filtering
Send all classifications, or only the ones your team triages. Most teams start with feature requests and competitor mentions and tune from there.

You can connect more than one Linear workspace on the Team plan and above.

On the roadmap

Voted by customers.

The next destinations are user-voted. Current roadmap, in order of votes at the time of writing:

  1. 01Slack (real-time channel, daily digest, or mention routing)
  2. 02Notion (database append)
  3. 03Webhook (POST to any endpoint)
  4. 04Asana
  5. 05Jira
  6. 06GitHub Issues / Discussions
  7. 07ClickUp
  8. 08Height
  9. 09Email digest
  10. 10Discord webhook
See the live roadmap and vote →
Custom destinations

Need a destination not on the roadmap?

Tell us:

  • The destination tool
  • The shape you need (issue, message, row, event, file)
  • The auth model (API key, OAuth, webhook)

Most custom pipelines ship within two weeks at a flat $1,500 per build. Scale customers get one per quarter at no charge.

Request a custom pipeline →