Connect Linear to Bart
When something happens in Linear, Notis takes the next step in Bart. 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 Bart
Auto-Post BART Service Advisories for Critical Issues
When a critical issue affecting commute times is created, automatically fetch and share current BART service alerts.
Verify BART Station Info When Meeting Location Changes
When a meeting location is added or updated in a Linear issue, automatically fetch station details and commute info.
Get Departure Schedules When Travel Issues Are Logged
When a travel or commute issue is created in your public Linear team, automatically fetch BART departure schedules.
Check BART Service When Project Dates Update
When a project milestone or deadline is updated in Linear, check BART service advisories to flag transit-related risks.
Enable Real-Time BART Monitoring for Urgent Comments
When an urgent comment is added to a commute-related issue, fetch real-time BART trip updates to stay ahead of delays.
Fetch Available BART Schedules for Office Days
When an office or in-person work issue is created, automatically pull available BART schedules for that day.
Fetch BART Route Info When Location-Based Projects Launch
When a new project with location or venue tags is created, automatically fetch relevant BART route information.
Get Daily Transit Briefing Every Weekday Morning
Every weekday morning, Notis pulls current BART service advisories to start your day with transit clarity.
Get Arrival-Time Schedules for Deadline-Driven Issues
When an issue with a deadline is updated, fetch BART schedules based on your required arrival time.
Supported Triggers and Actions
Notis builds workflows that link Linear to Bart. A trigger fires from one place; an action lands in another.
Linear triggers
Bart actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get BART API Version
Stub action for bart api version retrieval.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BART Available Schedules
Tool to retrieve a list of currently released bart schedules. use when you need schedule versioning info.
Comment Received Trigger
Triggered when a comment is received.
Get Route Info
Tool to fetch detailed information about a specific bart route. use when you know the route number (1–12) or need all routes configuration. call after confirming the route id.
Issue Created Trigger
Triggered when a new issue is created.
Get BART Stations
Stub action for bart stations retrieval.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get GTFS-RT Trip Updates
Tool to fetch real-time trip updates in gtfs-realtime format. use when you need the latest live trip information as raw protobuf.
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).
Download GTFS Static Schedule Feed
Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get BART Schedule Arrive
Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get BART Schedule Depart
Tool to get schedule information based on a specified depart time. use when planning trips from an origin to a destination with time constraints after confirming station codes.
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 Bart
Connect any two apps with Notis in the middle.
Linear and Bart, 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 Bart.