Connect Aivoov to Bart

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

Retrieve the current API version information.

Build an automation Browse examples

Examples

Ways Notis can move work from Aivoov to Bart

Plan a BART trip around a departure time

Send a trip request with origin, destination, and departure time to get a BART schedule with relevant service context.

Find a BART trip that arrives by a deadline

Provide an arrival deadline and stations to retrieve a BART schedule suited to reaching your destination on time.

Check live BART departures for a station

Request current departure predictions for a BART station, including platform and delay details when available.

Check BART advisories before a trip

Retrieve current BART service advisories for a trip request and summarize alerts relevant to the stations provided.

Check BART elevator availability

Retrieve current elevator status across BART stations and summarize availability for the stations in a trip request.

Look up a BART trip fare

Request fare information between two BART stations and receive the available fare types and prices.

Get BART station access details

Request station access information covering parking, transit connections, bike facilities, and lockers where available.

Get a scheduled BART service alert briefing

On a recurring schedule, retrieve current BART service advisories and send a concise briefing to your report channel.

Receive a scheduled BART train count

On a recurring schedule, retrieve the current number of trains operating in the BART system and report the result.

Supported Triggers and Actions

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

Aivoov triggers

Bart actions

Recurring trigger

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

TriggerScheduled

Get BART API Version

Retrieve the current API version information.

ActionInstant

Webhook trigger

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

TriggerInstant

Get BART Available Schedules

Retrieve available schedules; this deprecated endpoint returns an empty list.

ActionInstant

Get Route Info

Retrieve details about a route.

ActionInstant

Get Elevator Status

Retrieves current elevator status across all stations.

ActionInstant

Get BART Stations

Lists BART stations with their names, codes, locations, and addresses.

ActionInstant

Get Estimated Departures

Retrieves live estimated train departures for a station.

ActionInstant

Get GTFS-RT Trip Updates

Fetches trip updates as protobuf data; responses over 10 KiB may be incomplete.

ActionInstant

Get BART Fare

Retrieves fare prices between two stations.

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.