Connect Chatfai to Linear

When something happens in Chatfai, 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

Archives a Linear issue while preserving its data for future reference.

Build an automation Browse examples

Examples

Ways Notis can move work from Chatfai to Linear

Turn a Chatfai roleplay bug into a Linear issue

Send a reproducible Chatfai character or roleplay failure to Linear with the scenario and observed result in the issue description.

Add Chatfai story feedback to a Linear issue

Append a submitted Chatfai story or character feedback note to the relevant existing Linear issue as a comment.

Create Linear follow-ups from a Chatfai session review

On a recurring schedule, review Chatfai session material made available to Notis and create Linear issues for concrete unresolved work.

Turn Chatfai character requests into Linear issues

Capture a submitted character or scenario request as a Linear issue, retaining the requester's stated goals and constraints.

Post Chatfai review reminders to Linear issues

On a chosen schedule, comment on supplied open Linear issues that need a Chatfai character or scenario review.

Supported Triggers and Actions

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

Chatfai triggers

Linear actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Archive issue

Archives a Linear issue while preserving its data for future reference.

ActionInstant

Webhook trigger

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

TriggerInstant

Create a comment

Add a comment to an issue; this shared workspace change cannot be undone.

ActionInstant

Archive Project

Confirm the project name before archiving, especially in bulk; it leaves active views but can be unarchived later.

ActionInstant

Create linear issue

Creates an issue in a specified Linear team with the supplied details.

ActionInstant

Archive Project Update

Hides a project update from active views while keeping its data; it is irreversible only until it is unarchived.

Conditions and details

The update is archived, not permanently deleted: it is hidden from the default and active views and its data is preserved. It can be unarchived later; the action is irreversible only in the sense that the update stays hidden until it is explicitly unarchived.

ActionInstant

Get create issue default params

Retrieve a team's default issue estimate and workflow state for new issue forms.

ActionInstant

Create attachment

Creates an attachment and associates it with an existing issue.

ActionInstant

Create a label

Creates a label for a Linear team or returns an existing label with the exact same name.

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

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.