Integration
Connect Open Government, Australia to Byteplant Phone Validator
When something happens in Open Government, Australia, your agent does the next thing in Byteplant Phone Validator. 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 Byteplant Phone Validator 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 Byteplant Phone Validator
Triggers and actions 1 trigger · 9 actions
Trigger
Dataset updatedFires when a dataset is updated on the portal, detected by polling package_search sorted by last-modified date.
Action
Find datasetsSearch Australian government open datasets by keyword, tag, organization, or format (CKAN package_search).
Action
Find resourcesSearch dataset resources (files/links) by field values such as format or url (CKAN resource_search).
Action
Get datasetRetrieve full details of a dataset by its id or name, including its resources (CKAN package_show).
Action
Get groupRetrieve details of a dataset group by id or name, including its member datasets (CKAN group_show).
Action
Get organizationRetrieve details of a publishing organization by id or name, including its datasets (CKAN organization_show).
Action
Get resourceRetrieve details of a single dataset resource by its id, including download url and format (CKAN resource_show).
Action
List datasetsList the names of all datasets on the portal (CKAN package_list).
Action
Bulk Validate Phone NumbersUpload a CSV file (up to 100K phone numbers) for asynchronous bulk validation. POST https://api.phone-validator.net/api/v2/bulk-verify with Content-Type: text/csv and the CSV as the raw request body. Params: APIKey (required), TaskName, CountryCode, Locale, Mode (express|extensive), NotifyEmail, NotifyURL (optional). Response: {status: SUCC|FAIL, info: <task id if SUCC>}. Completion is announced via email and/or an HTTP GET to NotifyURL with a taskid query param; the vendor docs do not expose a separate poll/result-fetch endpoint.
Action
Validate Phone NumberValidate a phone number.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.