Connect Box to Bart

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

View example

Check BART alerts when a travel brief arrives

When a new travel brief is added to a Box folder, check current BART advisories and summarize relevant service disruptions.

View example

Plan a BART departure from a new itinerary

Read a newly added Box itinerary for a BART origin, destination, and departure time, then retrieve schedule information.

View example

Look up a BART station mentioned in a Box comment

When someone comments on a Box trip file, identify a clearly stated BART station abbreviation and retrieve its station information.

View example

Recheck BART advisories after an itinerary update

When a Box itinerary gets a new version, check current BART service advisories and summarize anything that may affect the plan.

View example

Get a morning BART advisory check for active trips

On a recurring schedule, review trip documents in a designated Box folder and check current BART advisories for relevant plans.

View example

Plan a BART arrival from a trip request

Start from an HTTP request containing confirmed BART station codes and an arrival time, then retrieve schedule information for the trip.

Supported Triggers and Actions

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

Box 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

Stub action for bart api version retrieval.

ActionInstant

Webhook trigger

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

TriggerInstant

Get BART Available Schedules

Tool to retrieve a list of currently released bart schedules. use when you need schedule versioning info.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

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.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Get BART Stations

Stub action for bart stations retrieval.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

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.

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

Download GTFS Static Schedule Feed

Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

Get BART Schedule Arrive

Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.

ActionInstant

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

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.

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.