Integration
Connect Open Government, South Australian Government to Leexi
When something happens in Open Government, South Australian Government, your agent does the next thing in Leexi. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Open Government, South Australian Government and Leexi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Open Government, South Australian Government can start in Leexi
When New or updated dataset in Open Government, South Australian Government
then Add meeting event in Leexi
When New or updated dataset in Open Government, South Australian Government
then Add team in Leexi
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Open Government, South Australian Government and Leexi
Triggers and actions 1 trigger · 28 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 meeting eventCreate a meeting event (schedule a meeting to be recorded).
Action
Add teamCreate a team in your Leexi workspace.
Action
Add userCreates a user in your Leexi workspace. Requires the write_users permission scope on the API key.
Action
Delete meeting eventDeletes a Leexi meeting event. Requires the write_meeting_events permission scope on the API key.
Action
Delete teamDelete a team of the workspace.
Action
Delete userDeactivates a Leexi user. Leexi never permanently deletes users: their calls and history are kept, sessions are revoked and they stop consuming a license. Deactivating an already inactive user still succeeds.
Action
Get callGet a single Leexi call or meeting, including its topics, AI summary prompts, tasks and transcript.
Action
Get call noteRetrieve a single call note.
Action
Get meeting eventRetrieve a single meeting event.
Action
Get teamRetrieve a single team of the workspace.
Action
Get userRetrieve a single user of the workspace.
Action
Launch meeting assistantSends the Leexi meeting assistant (bot) into a meeting event, or stops the bot that is already running.
Action
List call notesList call notes for a given call.
Action
List callsList the calls and meetings the API key can access, newest first by default, with optional filters on date, source, owner, participants, conversation type and customer contact.
Action
List teamsList all teams in your Leexi workspace.
Action
List usersList all users in your Leexi workspace.
Action
Request presigned recording upload URLRequests a presigned URL for uploading a call recording before creating the call with Add call. Requires the write_calls permission scope on the API key.
Action
Update call noteUpdates the translated text of a call note for one language. The original note text is not modified. Requires the write_calls permission on the API key.
Action
Update teamUpdate the name or active status of a team in your Leexi workspace. Only the values you fill in are changed.
Action
Update userUpdates a Leexi user. Only the fields you fill in are changed.
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
What our customers say
More from Open Government, South Australian Government
Open Government, South Australian Government to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Open Government, South Australian Government to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Open Government, South Australian Government to Google SheetsGoogle Sheets
Open Government, South Australian Government to StripeStripe is a payment processing platform for online businesses.
Open Government, South Australian Government to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Open Government, South Australian Government to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Leexi
HubSpot to LeexiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LeexiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LeexiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LeexiGoogle Sheets
Gmail to LeexiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeexiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Open Government, South Australian Government and Leexi, answered
What can start an automation from Open Government, South Australian Government?
Any of Open Government, South Australian Government's 1 trigger in the catalog, including New or updated dataset. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leexi when something happens in Open Government, South Australian Government?
Any of Leexi's 20 actions, including Update call note, Update team, Update user and Add meeting event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leexi to Open Government, South Australian Government?
Leexi has no triggers in the catalog today, so automations start in Open Government, South Australian Government. If you need the other direction, ask: your agent reads Leexi's API documentation and adds it.
Do I have to build a connector for Open Government, South Australian Government or Leexi?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.