Integration
Connect Open Government, South Australian Government to openSenseMap
When something happens in Open Government, South Australian Government, your agent does the next thing in openSenseMap. 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, South Australian Government and openSenseMap 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, South Australian Government and openSenseMap
Triggers and actions 1 trigger · 16 actions
Trigger
New or updated datasetFires when a dataset on the Data.SA portal is published or its metadata is updated.
- Find datasets
Search South Australian Government open datasets by keyword, tag, organisation, or format.
- Find records in a resource
Query rows from a tabular data resource (the datastore) with filters, full-text search, or SQL.
- Get dataset
Retrieve full metadata and resource list for one dataset by its ID or name.
- Get organisation
Retrieve details and dataset list for one publishing organisation.
- Get resource
Retrieve metadata for one data resource (file/table) belonging to a dataset.
- List datasets
List all dataset names published on the Data.SA open data portal.
- List groups
List the topical groups datasets are categorized under (e.g. Health, Transport, Environment).
- List organisations
List the government organisations that publish datasets on the portal.
Action
Find measurements by phenomenonFetch the latest measurements for all sensors measuring a given phenomenon/grouptag, as JSON or CSV. GET /statistics/idw or /boxes/data (phenomenon-scoped query)
- Find senseBoxes near location
Search senseBoxes near a given coordinate/bounding box and phenomenon. GET /boxes with near/bbox query params
- Get 10000 latest measurements for sensor
Fetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters. GET /boxes/:senseBoxId/data/:sensorId
- Get database statistics
Fetch overview statistics about the openSenseMap database (box count, sensor count, measurement count). GET /stats
- Get latest measurements of senseBox
Fetch the latest measurements of all sensors for a given senseBox. GET /boxes/:senseBoxId/sensors
- Get latest measurements of sensor
Fetch the latest measurement value for one specific sensor of a senseBox. GET /boxes/:senseBoxId/sensors/:sensorId
- Get senseBox
Fetch details for one senseBox station by its ID. GET /boxes/:senseBoxId
- List senseBoxes
List all senseBox stations, optionally filtered by bounding box/phenomenon/exposure. GET /boxes
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