KMD Nova connector

Nova journal via WorkZone OData (default) or legacy /api/cases REST.

How it works

Connect

Admin credentials

Browse

Folder or case scope

Import

Into a Northdocs case

Apply

Then verify

Write-back

Optional, off by default

Nova defaults to WorkZone OData. Use legacy REST only when IT still exposes /api/cases.

Prerequisites: connectors entitlement; API host; OAuth client; confirmation from IT whether the tenant already speaks WorkZone OData.

Open Integrations, then Connect on KMD Nova. The numbered guide on that page matches the steps below.

Nova is consolidating onto WorkZone OData. Confirm the API style with IT, then connect like WorkZone unless they still expose legacy /api/cases.

1
Confirm the API style with IT
Most tenants already speak WorkZone OData. Leave API style on WorkZone OData unless they still expose /api/cases and /api/documents.
2
Enter the Nova or WorkZone host
When style is WorkZone OData, the URL rules match WorkZone (host only, Northdocs calls /odata). For legacy, the base should be the REST host that serves /api/cases.
3
Add OAuth credentials
Token URL plus client id/secret, same model as WorkZone. Private-link Network if the journal is on-prem.
4
Scope to a sandbox case
Use a non-production File or case id. Do not write back into live citizen cases.
5
Connect with credentials
No Nova login screen. Native version write-back follows WorkZone only when API style is WorkZone OData.

Native version write-back follows WorkZone when API style is workzone.

See also: KMD WorkZone connector (same OData surface when API style is workzone) and ESDH write-back certification.

Still need a hand?

Help center