Integration
Connect Open Government, Canada to Transport for The Netherlands
When something happens in Open Government, Canada, your agent does the next thing in Transport for The Netherlands. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Open Government, Canada and Transport for The Netherlands 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 Open Government, Canada and Transport for The Netherlands
Triggers and actions 1 trigger · 12 actions
Trigger
New datasetFires when a new dataset is published to the Open Government portal.
Action
Find datasetsSearch the Open Government portal's catalog of published datasets by keyword, tag, or organization.
Action
Find records in a data resourceQuery the tabular records stored in a dataset's DataStore-backed resource, with filtering and search.
Action
Get datasetRetrieve the full record for one published dataset, including its resources and metadata.
Action
Get organizationRetrieve details for one publishing organization, including its datasets.
Action
List organizationsList the government organizations that publish datasets on the portal.
Action
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
Action
Find passtimes by stop areaGet the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
Action
Find passtimes by timing pointGet the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.
Action
List journeysList the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
Action
List linesList all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.
Action
List stop areasList all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.
Action
List timing pointsList all timing point codes (bus stops, tram/train stops, and virtual points) known to the OVAPI within its current uptime.
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