Connect Linear to Linear

When something happens in Linear, Notis takes the next step in Linear. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Linear to Linear

View example

Triage every new Linear issue automatically

Review each new issue, infer urgency and ownership from its context, then update it with a useful priority, assignee, and status.

View example

Convert actionable Linear comments into tracked issues

Detect concrete requests, promises, or follow-ups in new comments and create focused Linear issues only when separate tracking is warranted.

View example

Explain major issue changes in a concise comment

When ownership, priority, scope, or status changes materially, add a short comment explaining what changed and what should happen next.

View example

Refresh stale issues with a concrete next step

On a daily schedule, find active issues with no recent movement and update their due date, status, or ownership according to your follow-up rules.

View example

Consolidate likely duplicate Linear issues

Compare each new issue with open work, link strong matches, preserve useful context, and close the duplicate through one controlled Linear mutation.

View example

Add acceptance criteria to new private-team issues

Read a newly created private-team issue and add a concise comment with testable acceptance criteria, open questions, and a practical definition of done.

View example

Route new public-team issues by intent

Interpret each new public-team issue as a bug, request, question, or operational task, then update its owner, priority, and labels accordingly.

View example

Create a focused kickoff issue for every new project

When a Linear project is created, open one kickoff issue that captures the desired outcome, first decision, success signal, and immediate checkpoint.

View example

Realign active issues after a project change

When a project's lead, target date, priority, or status changes, update affected active issues in one controlled GraphQL operation.

Supported Triggers and Actions

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

Linear triggers

Linear actions

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Create linear attachment

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

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

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

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

TriggerPolling

Get create issue default params

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

ActionInstant

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Create a label

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

ActionInstant

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

Delete issue

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

ActionInstant

Project Created

Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.

TriggerPolling

Get all teams

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

ActionInstant

Project Properties Updated

Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.

TriggerPolling

Download issue attachments

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

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.