Turn an Adafruit IO device alert into a BART departure check
Get the next available BART departures when a connected-device update needs your attention. Include the station abbreviation in the webhook request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Estimated Departures
Retrieves live estimated train departures for a station.
Why this helps
A device alert can pull you away from your work and leave you checking transit details by hand when you need to head out.
- Check current departure predictions in response to a device update.
- Keep the station abbreviation with the webhook request so Notis knows where to look.
- See departure details such as minutes until departure, platform, train length, and delay information when returned.
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and Bart once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language; name it and choose a report channel.
- 3Describe that each webhook request should use its station abbreviation to fetch and summarize current BART estimated departures.
- 4Pick the Notis webhook trigger and have your connected-device system send its feed update and station abbreviation in an HTTP request.
- 5Choose where run reports go, then test with one real device update and a valid BART station abbreviation.
Questions about this workflow
Does Adafruit IO provide a trigger event for this workflow?
No Adafruit IO trigger event is listed here. This workflow starts when an external system sends an HTTP request to a Notis webhook, carrying the device update and station abbreviation.
What station detail does the request need?
Include the BART station identifier needed by the estimated departures action. Test with a valid station so Notis can request current predictions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Bart. A trigger fires from one place; an action lands in another.
Adafruit IO triggers
Bart actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get BART API Version
Retrieve the current API version information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BART Available Schedules
Retrieve available schedules; this deprecated endpoint returns an empty list.
Get Route Info
Retrieve details about a route.
Get Elevator Status
Retrieves current elevator status across all stations.
Get BART Stations
Retrieve information about all stations.
Get Estimated Departures
Retrieves live estimated train departures for a station.
Get GTFS-RT Trip Updates
Retrieve real-time trip updates.
Get BART Fare
Retrieves fare prices between two stations.
Connect any two apps with Notis in the middle.
Adafruit IO 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.