Connect Addressfinder to Bart

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

Build an automation Browse examples

Examples

Ways Notis can move work from Addressfinder to Bart

View example

Check BART fare from a verified address

Use a verified address and destination to look up BART fare options, including Clipper and cash prices.

View example

Get live BART departures for a verified location

Use a webhook with a verified address and station context to retrieve current BART departure predictions.

View example

Check BART elevators for an access-aware trip

Use a verified trip request to retrieve current elevator status across BART stations for accessibility planning.

View example

Retrieve BART station details from a verified trip request

Use a webhook with a verified address and known station abbreviation to retrieve BART station information.

View example

Review BART station access for a verified trip

Retrieve station access information, including parking, transit, bike facilities, and lockers, for a supplied BART station.

View example

Plan a BART trip around a departure time

Use a verified trip request with station codes and a departure time to retrieve BART schedule information.

View example

Plan a BART trip around an arrival deadline

Use verified trip context, station codes, and an arrival time to retrieve BART schedule options for arriving by a given time.

View example

Review BART service advisories on a schedule

Run a recurring check of current BART service advisories and receive a concise report in your chosen channel.

View example

Schedule a BART elevator status review

Run a recurring check of BART elevator availability and receive a status report for accessibility planning.

Supported Triggers and Actions

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

Addressfinder 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

Retrieve information about all stations.

ActionInstant

Get Estimated Departures

Retrieves live estimated train departures for a station.

ActionInstant

Get GTFS-RT Trip Updates

Retrieve real-time trip updates.

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 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.