Escalate blockers that threaten incident recovery
When a blocker puts recovery at risk, get the right responders engaged without another manual escalation decision.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Create Escalation V2
Tool to create an escalation in incident.io. Use when you need to page users to respond to alerts. You must specify either an escalation_path_id or direct targets (users/schedules).
Why this helps
A recovery blocker is documented in Linear, but the people needed to unblock response are not engaged promptly.
- Triggers the configured responder path for serious blockers.
- Reduces manual follow-up during recovery.
- Keeps the source issue available for context.
Setup
Build it in a few focused steps.
- 1Connect Linear and incident.io to Notis once in the portal.
- 2Ask Notis to create an escalation using the intended path when an issue update confirms a blocker to a live incident recovery.
- 3Select the Linear Issue Updated trigger and choose a channel for run reports.
- 4Test with one real blocker linked to an active incident and confirm the correct escalation path.
Questions about this workflow
Does this escalate every blocked issue?
No. The prompt should require a confirmed blocker to recovery from a live customer-impacting problem.
What is required to create the escalation?
Specify a configured escalation path or direct responder targets in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to incident.io. A trigger fires from one place; an action lands in another.
Linear triggers
incident.io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Attribute V2
Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract and organize information from incoming alerts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Route V2
Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and templates.
Comment Received Trigger
Triggered when a comment is received.
Create Alert Source V2
Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
Issue Created Trigger
Triggered when a new issue is created.
Create Catalog Entry V2
Tool to create a catalog entry in incident.io. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Catalog Entry V3
Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Create Catalog Type V3
Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create Custom Field Option
Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Custom Field V2
Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
Connect any two apps with Notis in the middle.
Linear and incident.io, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business incident.io.