Keep route details close to a development milestone
A new commit can prompt a quick route lookup. Notis can retrieve BART route details for a route number you specify and add them to its report.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
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.
Why this helps
Remembering route numbers and searching for configuration details adds friction when planning around work.
- Look up route details at a clear work milestone.
- Use a known route number in a plain language instruction.
- Keep route information in a Notis run report.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bart once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Describe the outcome: fetch detailed BART route information for the route number I provide and summarize it in the run report.
- 4Pick the New Commit Added to Pull Request trigger, then choose where run reports go.
- 5Test it with one real commit on the monitored pull request.
Questions about this workflow
What route input does this action require?
Provide a BART route number from 1 to 12, or ask for all routes configuration.
Does the commit identify which BART route I mean?
No. The route number must be provided in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bart. A trigger fires from one place; an action lands in another.
GitHub 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.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get BART Stations
Stub action for bart stations retrieval.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Download GTFS Static Schedule Feed
Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get BART Schedule Arrive
Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
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.
GitHub 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.