Connect GitHub to Bart
When something happens in GitHub, 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
Ways Notis can move work from GitHub to Bart
Check BART alerts after a pull request changes
When a pull request opens, closes, or syncs, check BART advisories so transit disruptions are easy to spot alongside release work.
Check BART advisories when a pull request review arrives
After a GitHub review is submitted, fetch current BART service advisories and include relevant alerts in the run report.
Get a BART departure plan after a pull request commit
When a commit is added to a monitored pull request, retrieve a BART schedule for a departure-time trip between known station codes.
Check BART service after a new review comment
A new inline review comment starts a check for current BART service advisories, helping keep transit disruptions alongside code feedback.
Check BART advisories when pull request reviewers change
When requested reviewers are added, removed, or re-requested, check BART advisories and surface active disruptions in the report.
Plan a BART departure when a pull request updates
On a pull request open, close, or sync event, get BART departure schedule options using station codes and a time you provide.
Plan a BART arrival after a pull request review
When a review is submitted, get BART schedule options for reaching a destination by the arrival time you specify.
Check BART service when a pull request gets a commit
A new pull request commit prompts Notis to fetch current BART advisories and summarize disruptions in your chosen report channel.
Get BART departure options when a new pull request opens
A newly created pull request can cue a departure schedule lookup for station codes and a departure time you provide.
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.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect GitHub and Bart
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.