Skip to content
Notis

Alerts Escalate Your Linear Issues

An external alert fires (critical error, customer escalation, system outage). Notis finds the related Linear issue and boosts its priority so your team sees it immediately.

Trigger

Webhook received

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

Action

Update issue

Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

Why this helps

A production issue flares up in your monitoring system, but the related Linear issue stays in medium priority. Your team doesn't know it's critical until someone notices. By then, time is lost.

  • Critical issues auto-escalate in Linear the moment they're detected elsewhere.
  • Your team responds faster because they see priority without hunting.
  • You reduce incident response latency.

Setup

Build it in a few focused steps.

  • 1Connect Linear to Notis.
  • 2Create an automation: 'When a webhook arrives with alert data, find the related Linear issue and update its priority to Urgent.'
  • 3Notis will provide a webhook URL.
  • 4Configure your alerting system (monitoring, error tracking, customer escalation) to send webhooks to that URL when critical issues occur.
  • 5Test by triggering an alert and verifying the priority changes in Linear.

Questions about this workflow

How does Notis match an alert to a Linear issue?

Your prompt defines it—by error keywords, service name, or custom fields. Notis learns from your examples.

Can I set different priorities based on alert severity?

Yes. You can map alert levels (critical, high, medium) to Linear priorities automatically.

Should this create a new issue or update an existing one?

Best practice: update an existing issue if one already exists for that alert type, or create a new one if it's a new incident.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Fireflies triggers

Linear actions

Transcription Complete Trigger

Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.

TriggerPolling

Create linear attachment

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

ActionInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

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 Fireflies 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.