Check BART conditions while planning an event
When an event plan appears in Notion, check relevant BART advisories before travel details slip off the list.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Service Advisories
Tool to fetch current bart service advisories. use when you need up-to-date system-wide or station-level alerts before presenting or planning transit routes.
Why this helps
Event logistics compete with many small details, and service checks are easy to forget until departure.
- Add a timely service check to event planning.
- Keep transit conditions connected to the event page.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bart to Notis once through the portal.
- 2Create an automation with one instruction to check relevant BART advisories for a new event plan.
- 3Pick the Notion Page Created trigger for your event planning page or database.
- 4Choose a channel for run reports, then test with an event plan that names its station.
Questions about this workflow
Can the check be limited to BART events?
Tell Notis in the instruction to act only when the event plan includes a BART journey or station.
Are advisories current?
The action retrieves current BART service advisories when the automation runs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bart. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get BART Stations
Stub action for bart stations retrieval.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Download GTFS Static Schedule Feed
Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Get BART Schedule Arrive
Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Connect any two apps with Notis in the middle.
Notion 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.