Connect Linear to incident.io
When something happens in Linear, Notis takes the next step in incident.io. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Linear to incident.io
Turn outage issues into incident records
Create an incident.io incident when a new Linear issue clearly reports a production outage or customer-impacting service disruption.
Keep incident status aligned with fix progress
When a Linear issue linked to an active incident changes status, update that incident's details to reflect the latest fix progress.
Refresh incident context from impact comments
When someone comments on a Linear issue with new customer-impact details, update the related incident summary in incident.io.
Escalate newly critical Linear issues
Create an incident.io incident when a public-team Linear issue is updated to a priority that your prompt defines as incident-worthy.
Carry private-team updates into incident records
Update an existing incident when a comment on a private-team Linear issue adds meaningful response context.
Open incidents for private-team production issues
Create an incident when a new private-team Linear issue describes an operational outage or production-impacting event.
Update incident response when private issue priority changes
When a private-team Linear issue's properties change, update the linked incident if the change materially affects response urgency.
Register new Linear projects in the incident catalog
Create an incident.io catalog entry for a new Linear project when it represents a service or operational resource worth tracking.
Refresh catalog ownership from project changes
When a Linear project lead or other ownership detail changes, update the related incident.io catalog entry to keep responder references current.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Linear and incident.io
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.