Connect Bart to Linear

When something happens in Bart, 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 Bart to Linear

View example

Turn rail disruption alerts into Linear issues

Check Bart for service alerts on a supplied route and create a Linear issue for each disruption that could affect a team commitment.

View example

Post a route change summary to Linear

Check Bart for an updated route and comment on a specified Linear issue with the proposed alternative and key journey details.

View example

Refresh an issue with station information

Look up a specified station in Bart and update a related Linear issue with the station details relevant to the task.

View example

Create a Linear follow-up for a complex rail journey

Plan a supplied multi-leg journey with Bart and create a Linear issue when the itinerary needs coordination or follow-up.

View example

Prepare a Linear task for a station visit

Check Bart station information for a supplied visit and create a Linear issue capturing preparation tasks relevant to the visit.

View example

Review upcoming rail risks before the workday

On a recurring schedule, check supplied upcoming routes in Bart and list relevant open Linear issues to help spot work at risk.

View example

Add a weekly travel blocker check-in

On a recurring schedule, check Bart alerts for supplied routes and comment on a specified Linear issue when a disruption needs follow-up.

View example

Refresh travel context on an upcoming work issue

On a recurring schedule, look up a supplied journey in Bart and update a Linear issue with relevant current schedule or alert context.

View example

Find open work that depends on upcoming rail trips

On a recurring schedule, review supplied journeys in Bart and list open Linear issues that may need attention before travel.

Supported Triggers and Actions

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

Bart triggers

Linear actions

Recurring trigger

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

TriggerScheduled

Create linear attachment

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

ActionInstant

Webhook trigger

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

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

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

Get create issue default params

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

ActionInstant

Create a label

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

ActionInstant

Delete issue

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

ActionInstant

Get all teams

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

ActionInstant

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.