Integration
Connect Open Government, Finland to Xitoring
When something happens in Open Government, Finland, 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, Finland 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, Finland and Xitoring
Triggers and actions 1 trigger · 24 actions
Trigger
New datasetFires when a new dataset is published to the Finnish open-data catalog (polls CKAN package_search sorted by creation date).
Action
Find datasetsSearch the Finnish open-data catalog for datasets matching a keyword, tag, organization, or other criteria (CKAN package_search).
Action
Get datasetRetrieve the full metadata and resource list for one published dataset by its id or name (CKAN package_show).
Action
Get organizationRetrieve details and datasets for one publishing organization by id or name (CKAN organization_show).
Action
Get resourceRetrieve one data resource (file/link/format) belonging to a dataset by its resource id (CKAN resource_show).
Action
List datasetsList the names of all published datasets in the catalog (CKAN package_list).
Action
List groupsList the topical groups/categories used to organize datasets in the catalog (CKAN group_list).
Action
List organizationsList the government organizations and agencies that publish datasets in the catalog (CKAN organization_list).
Action
List tagsList the tags used across datasets in the catalog, optionally filtered by a query string (CKAN tag_list).
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.