Integration
Connect Transport for Denver, US to Clay
When something happens in Transport for Denver, US, your agent does the next thing in Clay. 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 Clay 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 Clay
Triggers and actions 1 trigger · 7 actions
Trigger
New service alertFires when RTD publishes a new service alert, polling Denver RTD's GTFS-Realtime alerts feed.
Action
Get service alertsFetch the service alerts RTD is currently publishing (delays, detours, closures), from Denver RTD's GTFS-Realtime alerts feed.
Action
Get trip updatesFetch real-time trip progress and arrival/departure predictions for RTD scheduled trips, from Denver RTD's GTFS-Realtime trip-updates feed.
Action
Get vehicle positionsFetch the live position of every RTD vehicle currently in service, from Denver RTD's GTFS-Realtime vehicle-positions feed.
Action
Create Record in TableAdds a record (row) to a Clay table by posting it to that table's webhook URL. Each key in the record becomes a column in the table.
Action
Get my userReturns the Clay user the connection authenticates as. Takes no search criterion.
Action
Get Search Results PageReturns the next page of people or company records for a Clay search you already created. Call it repeatedly while it reports that more results are available.
Action
Search People or CompaniesStarts a search of Clay's people or company database using structured filters, and returns a search ID. Use Get Search Results Page to read the matching records.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.