Integration
Connect Open Government, South Australian Government to Represent by Open North
When something happens in Open Government, South Australian Government, your agent does the next thing in Represent by Open North. 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 Represent by Open North 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 Represent by Open North
Triggers and actions 1 trigger · 15 actions
Trigger
New or updated datasetFires when a dataset on the Data.SA portal is published or its metadata is updated.
- Find datasets
Search South Australian Government open datasets by keyword, tag, organisation, or format.
- Find records in a resource
Query rows from a tabular data resource (the datastore) with filters, full-text search, or SQL.
- Get dataset
Retrieve full metadata and resource list for one dataset by its ID or name.
- Get organisation
Retrieve details and dataset list for one publishing organisation.
- Get resource
Retrieve metadata for one data resource (file/table) belonging to a dataset.
- List datasets
List all dataset names published on the Data.SA open data portal.
- List groups
List the topical groups datasets are categorized under (e.g. Health, Transport, Environment).
- List organisations
List the government organisations that publish datasets on the portal.
Action
Find representatives by pointFind elected officials for a given latitude/longitude. GET /representatives/?point={lat},{lng} (optionally scoped to a representative set via /representatives/{set}/?point=...); supports filters like last_name, party_name, elected_office.
- Find representatives by postal code
Look up elected officials and boundaries covering a Canadian postal code. GET /postcodes/{postal_code}/ — returns boundaries_centroid, boundaries_concordance, representatives_centroid, representatives_concordance; optional sets query param restricts to a boundary set.
- List boundaries
Paginated list of electoral boundaries. GET /boundaries/ (optionally /boundaries/{boundary_set}/, or comma-separated multiple sets via ?sets=); filterable by name/external_id.
- List boundaries covering a point
Find electoral boundaries containing a given latitude/longitude. GET /boundaries/?contains={lat},{lng} (optionally scoped to a boundary set via /boundaries/{set}/?contains=...).
- List boundary sets
List available boundary sets (groups of electoral districts, e.g. federal-electoral-districts, toronto-wards). GET /boundary-sets/; filterable by name/domain. GET /boundary-sets/{slug}/ for a single set.
- List candidates
Paginated list of electoral candidates for tracked elections. GET /candidates/ — behaves like /representatives/, filterable by name, first_name, last_name, gender, district_name, party_name.
- List representatives
Paginated list of elected officials. GET /representatives/ (optionally /representatives/{representative_set}/); filterable by name, first_name, last_name, gender, district_name, elected_office, party_name.
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