Integration
Connect Open Government, Queensland Government to Wachete
When something happens in Open Government, Queensland Government, your agent does the next thing in Wachete. 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, Queensland Government and Wachete 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, Queensland Government and Wachete
Triggers and actions 3 triggers ยท 17 actions
Trigger
New datasetFires when a new dataset is published on the Queensland Government open data portal.
Action
Find datasets by criteriaSearch datasets on the portal by keyword, tag, organization, or other facets.
Action
Find resources by criteriaSearch across all data resources by field/value criteria.
Action
Get datasetRetrieve the full metadata and resource list for a single dataset by its id or name.
Action
Get groupReturns one thematic group of the Queensland open data catalogue by its short name, with its title, description and dataset count. The portal blocks its own group endpoint, so the group is read from a dataset search instead; a group with no datasets is reported as not found.
Action
Get organizationReturns one publishing organisation of the Queensland open data catalogue by its short name, with its title, description and dataset count. The portal blocks its own organisation endpoint, so the organisation is read from a dataset search instead; an organisation with no datasets is reported as not found.
Action
Get resourceReturns one published file or service of the Queensland open data catalogue by its file id, including its download link, format and size.
Action
List datasetsReturns the short name of each dataset on the Queensland Government open data portal, up to 1000 per call.
Action
List groupsReturns every thematic group datasets are filed under on the Queensland open data portal, with a dataset count for each. The portal blocks its own group-list endpoint, so the groups are read from the dataset search's grouped counts.
Action
List organizationsReturns every publishing organisation on the Queensland open data portal, with a dataset count for each. The portal blocks its own organisation-list endpoint, so the organisations are read from the dataset search's grouped counts.
Action
List tagsReturns the tags used to label datasets on the Queensland open data portal, optionally narrowed to tags containing given text or belonging to one vocabulary.
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange 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.
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