Integration
Connect Wachete to Open Government, Austria
When something happens in Wachete, your agent does the next thing in Open Government, Austria. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Wachete and Open Government, Austria 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 Wachete and Open Government, Austria
Triggers and actions 2 triggers · 16 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
Action
Find datasetsReturns up to 100 datasets from the Austrian open data catalogue that match the given search words, optionally narrowed by facet, date, quality score or geographic bounding box.
- Find resources
Returns the published files and services (distributions) of up to 100 Austrian open data catalogue datasets that match the given search words, optionally narrowed to a single file format.
- Get dataset
Returns the full record of one Austrian open data catalogue dataset by its id, including all of its published files and services.
- Get group
Returns one data category (thematic group) of the Austrian open data catalogue by its short code, with its name in every published language.
- Get organization
Returns one publishing organisation of the Austrian open data catalogue by its catalogue id, including its name, homepage and how many datasets it publishes.
- Get resource
Returns one published file or service of an Austrian open data catalogue dataset, selected by its file id, including its download links, format and licence.
- List datasets
Returns the ids of every dataset in one publishing organisation's catalogue on the Austrian open data portal.
- List groups
Returns every data category (thematic group) datasets can belong to on the Austrian open data portal, with each name in every published language.
- List organizations
Returns the catalogue id of every publishing organisation (government body) on the Austrian open data portal.
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