Integration
Connect Transport for Denver, US to Open Government, Ireland
When something happens in Transport for Denver, US, your agent does the next thing in Open Government, Ireland. 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 Open Government, Ireland 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 Open Government, Ireland
Triggers and actions 1 trigger · 11 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.
Action
Find datasets by search criteriaSearch the Ireland open-data catalog for datasets matching a Solr query. Endpoint: GET /api/3/action/package_search with params q, fq, sort, rows, start. Returns count + list of matching dataset dicts (package_search).
- Find records in a resource
Query the structured data (DataStore) of a specific published resource (CSV/table), returning matching rows. Endpoint: GET /api/3/action/datastore_search?resource_id={resource_id}&q={query}&limit={limit}&offset={offset}.
- Get dataset
Fetch full metadata for one dataset (package) by id or name, including its resources. Endpoint: GET /api/3/action/package_show?id={id}.
- List datasets
List the names/ids of all datasets in the catalog, paginated. Endpoint: GET /api/3/action/package_list?limit={limit}&offset={offset}.
- List groups
List thematic groups/categories datasets can belong to. Endpoint: GET /api/3/action/group_list.
- List organizations
List all publishing organizations (government bodies) registered in the catalog. Endpoint: GET /api/3/action/organization_list.
- List tags
List all tags used across datasets in the catalog, for discovery/filtering. Endpoint: GET /api/3/action/tag_list.
- Run SQL against a resource
Run a read-only SQL query against one or more DataStore resources for advanced filtering/aggregation. Endpoint: GET /api/3/action/datastore_search_sql?sql={sql}.
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