Integration
Connect Open Government, Australia to Agify
When something happens in Open Government, Australia, your agent does the next thing in Agify. 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, Australia and Agify 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, Australia and Agify
Triggers and actions 1 trigger · 8 actions
Trigger
Dataset updatedFires when a dataset is updated on the portal, detected by polling package_search sorted by last-modified date.
- Find datasets
Search Australian government open datasets by keyword, tag, organization, or format (CKAN package_search).
- Find resources
Search dataset resources (files/links) by field values such as format or url (CKAN resource_search).
- Get dataset
Retrieve full details of a dataset by its id or name, including its resources (CKAN package_show).
- Get group
Retrieve details of a dataset group by id or name, including its member datasets (CKAN group_show).
- Get organization
Retrieve details of a publishing organization by id or name, including its datasets (CKAN organization_show).
- Get resource
Retrieve details of a single dataset resource by its id, including download url and format (CKAN resource_show).
- List datasets
List the names of all datasets on the portal (CKAN package_list).
Action
Predict agePredict the likely age of a person from their name. GET https://api.agify.io?name={name}&apikey={apikey}, optional country_id (ISO 3166-1 alpha-2) to scope prediction to a country. Returns {name, age, count} (age is null when no prediction). Supports batch via repeated name[] params (up to 100) but this op should implement the single-name form.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.