Integration
Connect Open Government, South Australian Government to Billage
When something happens in Open Government, South Australian Government, your agent does the next thing in Billage. 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, South Australian Government and Billage 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, South Australian Government and Billage
Triggers and actions 1 trigger · 24 actions
Trigger
New or updated datasetFires when a dataset on the Data.SA portal is published or its metadata is updated.
Action
Find datasetsSearch South Australian Government open datasets by keyword, tag, organisation, or format.
Action
Find records in a resourceQuery rows from a tabular data resource (the datastore) with filters, full-text search, or SQL.
Action
Get datasetRetrieve full metadata and resource list for one dataset by its ID or name.
Action
Get organisationRetrieve details and dataset list for one publishing organisation.
Action
Get resourceRetrieve metadata for one data resource (file/table) belonging to a dataset.
Action
List datasetsList all dataset names published on the Data.SA open data portal.
Action
List groupsList the topical groups datasets are categorized under (e.g. Health, Transport, Environment).
Action
List organisationsList the government organisations that publish datasets on the portal.
Action
Add ProductCreate a new Billage product. POST /v2/products.
Action
Create AccountCreates a new account.
Action
Create ContactCreates a new contact in an account.
Action
Delete AccountDelete a Billage account by id. DELETE /v2/accounts/{account-id}.
Action
Delete ContactDelete a Billage contact by id. DELETE /v2/contacts/{id}.
Action
Delete LeadDelete a Billage lead by id. DELETE /v2/leads/{id}.
Action
Get AccountFetch a single Billage account (company/customer record) by id. GET /v2/accounts/{account-id}.
Action
Get ContactFetch a single Billage contact by id. GET /v2/contacts/{id}.
Action
Get LeadFetch a single Billage lead by id. GET /v2/leads/{id}.
Action
Get ProductFind a Billage product by id. GET /v2/products/{id}.
Action
List AccountsList/search Billage accounts by name, alias, vat, tags, etc. GET /v2/accounts.
Action
List ContactsList/search Billage contacts by criteria. GET /v2/contacts.
Action
List LeadsList Billage leads. GET /v2/leads.
Action
List ProductsList/search Billage products by alias or name. GET /v2/products.
Action
Update AccountUpdate an existing Billage account. PUT /v2/accounts.
Action
Update ContactUpdate an existing Billage contact. PUT /v2/contacts.
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