Divo

Integrations

What does your firm need Divo to connect to?

Divo is built API-first. Tell us what your firm runs — practice management, document management, or something custom — and we scope a two-way integration to your workflow as part of onboarding. Push reports, pull client data, keep one source of truth.

Practice Management

The platforms we’re ready to build against. Matter data flows both ways — no double-entry, no copy-paste.

C

Clio

The integration we build: two-way sync of matters, contacts, and documents — reports pushed into matters, client data pulled in automatically.

A

ActionStep

Scoped to push calculations and reports into ActionStep matters, with contact records and matter status syncing both ways.

PS

PCLaw / Soluno

Common in Ontario firms — we connect calculations to matter records and time entries based on how your firm uses them.

P

PracticePanther

Covers matter and contact sync, with Divo PDF reports attached directly to PracticePanther matter files.

C

CosmoLex

Scoped to pull client and matter data, and push court-ready reports back into CosmoLex.

Document Management

Pull source documents in, push final reports back. Your DMS stays the source of truth — we build to its API.

N

NetDocuments

Covers reading income disclosures and financial statements from NetDocuments, with final reports saved back to the matter workspace.

I

iManage

Scoped to pull T1s, T4s, and disclosures from iManage Work, storing calculation outputs alongside source documents.

SO

SharePoint / OneDrive

For Microsoft-365-native firms: we build the integration to watch a matter folder and ingest disclosures as they arrive.

Custom

If it has a documented API, we’ll build it.

BY

Build your own

Have a tool with a documented REST or GraphQL API? We scope the build and timeline with you on Enterprise plans.

Request integration →

What we commit to (and what we don’t)

What we commit to

A working two-way sync between Divo and any tool with a documented REST or GraphQL API — scoped to the data fields your firm actually uses, and tested against your real workflow before go-live.

What we don’t

Screen-scraping, undocumented APIs, or one-off file format exports without a vendor-supported endpoint.

Tell us what you’re running.

Every Divo integration is scoped to the firm that needs it. We’ll map your stack on the first call and commit to a timeline with you during onboarding.

Request a custom integration