Platform · Integrations

If it cannot write back, it is still a demo.

Reading is the easy half. The value shows up when the outcome lands in the system your people actually work in: the case file updated, the record created, the memo attached to the right matter.

Liba is designed to connect to enterprise and government systems such as SharePoint, Microsoft 365, Salesforce, SAP, ServiceNow, Snowflake and Priority ERP, and to MCP servers for tools that expose one. We confirm the connection route for each system in your process during mapping, before the scope is agreed.

Connections are governed like everything else

Credentials live in encrypted environment variables, never inside a workflow. Someone reviewing or editing a flow does not thereby see the secrets it uses.

Permissions are set per connection, so an agent gets exactly the reach its process requires and nothing beyond it. Every call an agent makes through a connection is logged as part of the run: what was called, when, and with what result.

When there is no connector

Most of the systems that matter in government and regulated industry were not built to be integrated with. Some predate the web. We treat that as the normal case rather than an exception, and we work down a ladder until something fits.

A generic node first. If the system exposes a REST or SOAP endpoint, or we can be given a read replica or a database view, no bespoke work is needed. This covers more legacy systems than people expect.

An MCP server. If the vendor publishes one, or your team can stand one up, Liba treats it like any other tool, with the same permissions and the same logging.

A scheduled exchange. Older systems often cannot be called but can be made to produce a file. A nightly export to SFTP or a network share, read by an agent, with results written back the same way. It is unglamorous and it holds.

A connector we build. When none of the above works, our engineers build one during delivery, against your instance rather than a generic spec.

One rule governs the choice: whatever the route, the connection is governed like every other. Credentials stay in encrypted environment variables, permissions are set per connection, and every call an agent makes is logged as part of the run.

What that looks like in practice

For a regional water utility, the billing system stays the system of record. The automation reads billing-period data, sorts accounts against approved thresholds and sends only the cases that need judgement to an employee, with the supporting data attached. The utility’s existing SMS and email modules are adopted under a procedure rather than replaced.

The workflow prefers interfaces to screen automation, runs the automation under its own dedicated user so that its actions are distinguishable from an employee’s, and sends any case to an employee if an automated step fails.

What it costs

A connector on the critical path of the pilot process is in scope of the pilot. Connectors for systems beyond that process are quoted separately.

We tell you which side of that line each system falls on during mapping, before the scope is agreed. Discovering it later is how integration projects acquire a reputation.