Integration
Connect Transport for Denver, US to iDigBio
When something happens in Transport for Denver, US, your agent does the next thing in iDigBio. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Transport for Denver, US and iDigBio to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Transport for Denver, US and iDigBio
Triggers and actions 2 triggers · 9 actions
Trigger
New service alertFires when RTD publishes a new service alert, polling Denver RTD's GTFS-Realtime alerts feed.
- Get service alerts
Fetch the service alerts RTD is currently publishing (delays, detours, closures), from Denver RTD's GTFS-Realtime alerts feed.
- Get trip updates
Fetch real-time trip progress and arrival/departure predictions for RTD scheduled trips, from Denver RTD's GTFS-Realtime trip-updates feed.
- Get vehicle positions
Fetch the live position of every RTD vehicle currently in service, from Denver RTD's GTFS-Realtime vehicle-positions feed.
Trigger
New recordPolls for specimen records newly indexed into iDigBio matching a saved search query, sorted by modified/index date. GET /v2/search/records/ sorted on datemodified.
- Find media records
Search iDigBio media records (images/media associated with specimens) matching a query. GET/POST /v2/search/media/ using the iDigBio Query Format (mq/rq parameters).
- Find records
Search iDigBio specimen records matching a query. GET/POST /v2/search/records/ using the iDigBio Query Format (rq parameter).
- Find recordsets
Search iDigBio recordsets (collections/datasets contributed by publishers) matching a query. GET/POST /v2/search/recordsets/ using the iDigBio Query Format (rsq parameter).
- Get media record
Retrieve a single iDigBio media record by its UUID. GET /v2/view/mediarecords/{uuid}.
- Get record
Retrieve a single iDigBio specimen record by its UUID. GET /v2/view/records/{uuid}.
- Get recordset
Retrieve a single iDigBio recordset (dataset) by its UUID. GET /v2/view/recordsets/{uuid}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews