Turn a Jira travel request into a BART departure plan
When a Jira task calls for a trip, send a request to Notis and get schedule information for the specified BART stations and departure time.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Planning a work trip requires carrying station names and timing between project tasks and transit tools.
- Start trip planning from an HTTP request tied to a Jira task process.
- Retrieve departure schedule information for the supplied constraints.
- Keep the returned schedule in the workflow report.
Setup
Build it in a few focused steps.
- 1Connect Bart once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe in one instruction that a webhook request should return BART departures for the supplied stations and time.
- 4Pick a Notis webhook as the trigger and choose where run reports go.
- 5Test with one real example using confirmed BART station codes.
Questions about this workflow
What details are needed for the departure lookup?
Provide origin and destination station codes and a departure time. Confirm station codes before requesting schedule information.
Does this trigger automatically from Jira?
No. This workflow starts from an HTTP request. Jira task context can be included in the request process.
Does it provide live train positions?
No. This action retrieves schedule information based on a specified departure time.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bart. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
Get BART Stations
Stub action for bart stations retrieval.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Download GTFS Static Schedule Feed
Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.
Get BART Schedule Arrive
Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.
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.
Jira 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.