Keep your systems. Lose the swivel chair.
Hendl connects to the systems your cases already live in — policy admin, documents, email, finance — through governed, two-way connectors. Agents read and write where the work is, and nobody re-keys anything again.
Hendl works where your work already is.
The fastest way to fail an automation programme is to demand a migration first. Hendl doesn’t — it connects, governs, and gets to work.
Hendl sits on top of the systems you already run — policy admin, DMS, email, finance — reading and writing through governed connectors.
Not an export. Changes flow both directions in near real time, so neither system ever holds a stale copy of the truth.
Every connector has scoped permissions and every write is on the audit trail — integration without losing control.
The systems cases live in.
Configuration, not projects.Watch a claim cross your stack.
An agent moves one claim through email, policy admin, documents and finance — each hop through a governed connector, each write on the trail.
Each connector gets only the objects and actions it needs — nothing blanket.
Every write to an external system lands on the trail with its cause and approver.
Retries, conflict handling and drift detection — no silent failures.
A full REST API and webhooks for anything the catalogue doesn’t cover.
Questions teams ask about connecting.
Do we have to replace our existing systems?
No. Hendl is designed to sit on top of them. Your policy admin, DMS and finance systems stay the systems of record where you want them to.
How long does a connector take to set up?
Catalogue connectors are configuration, not projects — typically hours to days, including permission scoping and a sandbox test.
What if our system isn’t in the catalogue?
The REST API and webhooks cover custom systems, and our team builds new connectors continuously — tell us what you run.
Can agents write to external systems?
Yes, through the same governed connectors — scoped permissions, approval gates where you set them, and every write on the audit trail.
How is data kept in sync?
Connectors sync in near real time with retries and conflict handling. Drift is detected and flagged rather than silently ignored.
What happens if a connector fails?
Work queues rather than disappears. The failure raises a signal, affected cases are flagged, and everything replays once the connection recovers.