Integration
Connect Open Government, South Australian Government to Xitoring
When something happens in Open Government, South Australian Government, your agent does the next thing in Xitoring. 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 Xitoring 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 Xitoring
Triggers and actions 1 trigger · 24 actions
Trigger
New or updated datasetFires when a dataset on the Data.SA portal is published or its metadata is updated.
Action
Find datasetsSearch South Australian Government open datasets by keyword, tag, organisation, or format.
Action
Find records in a resourceQuery rows from a tabular data resource (the datastore) with filters, full-text search, or SQL.
Action
Get datasetRetrieve full metadata and resource list for one dataset by its ID or name.
Action
Get organisationRetrieve details and dataset list for one publishing organisation.
Action
Get resourceRetrieve metadata for one data resource (file/table) belonging to a dataset.
Action
List datasetsList all dataset names published on the Data.SA open data portal.
Action
List groupsList the topical groups datasets are categorized under (e.g. Health, Transport, Environment).
Action
List organisationsList the government organisations that publish datasets on the portal.
Action
Add checkCreate a new uptime/website/server check. POST /api/v2/check
Action
Add groupStore a new check/server group. POST /api/v2/groups
Action
Add heartbeatCreate a new heartbeat check. POST /api/v2/heartbeat/add
Action
Add maintenance scheduleCreate a new maintenance window. POST /api/v2/maintenance-schedules/add
Action
Add ticketCreate a new support ticket. POST /api/v2/tickets
Action
Delete checkDelete a check. DELETE /api/v2/checks/{id}
Action
Delete serverRemove a server from monitoring. DELETE /api/v2/servers/{id}
Action
Get checkRetrieve a single check by id. GET /api/v2/check/{id}
Action
Get incidentGet a single incident's data. GET /api/v2/incidents/{id}
Action
Get serverRetrieve a single server by id. GET /api/v2/servers/{id}
Action
List checksList all checks. GET /api/v2/check/
Action
List groupsList all groups. GET /api/v2/groups
Action
List maintenance schedulesList maintenance schedules. GET /api/v2/maintenance-schedules
Action
List serversList all monitored servers. GET /api/v2/servers
Action
Resolve incidentResolve an open incident. POST /api/v2/incidents/{id}/resolve
Action
Update checkUpdate an existing check. PUT /api/v2/check/{id}
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