Connect Linear to Cursor

When something happens in Linear, Notis takes the next step in Cursor. 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 Cursor

View example

See every running Cursor cloud agent the moment a Linear issue lands

A new Linear issue arrives and Notis pulls the current list of Cursor cloud agents so you know what is already in flight before you start.

View example

Pull the Cursor agent conversation whenever a Linear issue changes status

An issue moves to In Progress or gets updated and Notis fetches the matching Cursor cloud agent conversation so you can read the latest progress in one place.

View example

Get a daily roster of your Cursor cloud agents alongside your Linear work

Every morning Notis lists your active Cursor cloud agents so you open the day knowing exactly what is running before you touch Linear.

View example

Check which Cursor agents are active when a Linear comment comes in

A teammate comments on a Linear issue and Notis lists your active Cursor cloud agents so you can respond knowing what is already in progress.

View example

List the GitHub repos Cursor can reach when a Linear issue is created

A new Linear issue appears and Notis pulls the GitHub repositories available through your Cursor account so you know exactly where the work can land.

View example

Surface available GitHub repos when a new Linear project kicks off

A new Linear project is created and Notis lists the GitHub repositories your Cursor account can access so you can align the project to the right codebases from day one.

View example

Get a weekly digest of the AI models available in Cursor

On a schedule you choose, Notis lists the AI models available in Cursor so you always know what you can pick from without checking manually.

View example

List Cursor agents when a public-team Linear issue is created

A new issue lands in a public Linear team and Notis lists your Cursor cloud agents so shared work never overlaps with something already running.

View example

List Cursor agents when a private-team Linear issue appears

A new issue shows up in a private Linear team and Notis lists your Cursor cloud agents so sensitive work stays coordinated without extra clicks.

Supported Triggers and Actions

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

Linear triggers

Cursor actions

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Get Agent Conversation

Tool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Get API Key Info

Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.

ActionInstant

Issue Updated Trigger

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

TriggerInstant

List Agents

Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.

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

List Available Models

Tool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.

ActionInstant

Private Team Issue Created

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

TriggerPolling

List GitHub Repositories

Tool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.

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

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

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

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.