Skip to content
Notis

Log incidents as Linear issues automatically

Alerts fire, the fire gets put out, and the follow-up work evaporates in the alert channel. Notis catches the incident webhook and opens a Linear issue, so the fix and the retro become real, tracked work.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Create linear issue

Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.

Why this helps

The follow-up after an incident is the easiest thing to lose, because the alert scrolls away and no one turns it into tracked work.

  • Every incident leaves behind a Linear issue for the real follow-up work.
  • Fixes and retros stop evaporating in a noisy alert channel.
  • Your monitoring stack feeds Linear without a human in the loop.

Setup

Build it in a few focused steps.

  • 1Connect Linear to Notis once through the portal.
  • 2Ask Notis for your portal link and create a New Automation, or describe it to Notis in plain language.
  • 3State the outcome, for example: When my incident webhook fires, create a Linear issue to track the follow-up.
  • 4Choose the incoming webhook as the trigger and point your monitoring tool at the Notis address.
  • 5Pick a report channel and test by sending one real alert through the webhook.

Questions about this workflow

Can I set the issue priority high?

Yes. Say so in your instruction, for example ask Notis to create the issue with high priority, and it will.

Which alerting tools work?

Any tool that can send an HTTP webhook can trigger this automation.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Linear. A trigger fires from one place; an action lands in another.

Jira triggers

Linear actions

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Create linear issue

Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.

ActionInstant

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Jira and Linear. Any combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.