Integration
Automate with Linear
Linear keeps your engineering team moving. NVS automates the issue lifecycle — creating bugs from errors, syncing with GitHub, and posting updates to Slack without any manual work.
Use Cases
When a GitHub PR is merged into main, NVS finds the linked Linear issue by branch name, marks it Done, and posts a completion message to the team Slack channel.
Trigger
PR Merged
github.trigger
Fires when a pull request is merged into the main branch.
Extract Issue ID
nvs.set
Linear issue ID parsed from the branch name or PR description.
Close Linear Issue
linear.issue
Issue status set to Done. Completion timestamp recorded.
Output
Notify #engineering
slack.message
Slack post: issue title, PR author, and link to the merged PR.
When Sentry logs a new unhandled error above the alert threshold, a Linear bug ticket is created with full context, and the on-call engineer is pinged in Slack.
Trigger
New Sentry Error
sentryio.trigger
Fires when a new unhandled exception crosses the alert threshold.
Format Issue Data
nvs.set
Error title, stack trace snippet, affected users, and Sentry link prepared.
Create Linear Bug
linear.issue
Bug ticket created in the appropriate project with P1 priority.
Output
Ping On-Call
slack.message
On-call engineer notified: error summary, affected count, and Linear link.
Every Monday morning, all issues in the current Linear cycle are pulled, grouped by status, and posted as a structured digest to the engineering team's Slack channel.
Trigger
Monday 9am
schedule.cron
Weekly digest runs every Monday morning before standup.
Fetch Cycle Issues
linear.cycle
All issues in the current active cycle fetched with status and assignee.
Format Digest
openai.gpt-4o
GPT-4o organizes issues by status and writes a concise summary.
Output
Post to #engineering
slack.message
Structured digest posted: In Progress, Todo, Done counts with issue links.