KMD WorkZone connector
WorkZone OData Files/Documents with WzOAuth2 client credentials.
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
Prerequisites: Trial or Enterprise with connectors; a public HTTPS WorkZone host or an active private link; WzOAuth2 client id/secret and token URL; a sandbox File (case) id.
Open Integrations, then Connect on KMD WorkZone. The numbered guide on that page matches the steps below.
WorkZone is credentials-based. Kommune IT gives you a public HTTPS host (or you create a private link) plus a WzOAuth2 client. There is no WorkZone login screen in Northdocs.
- 1
Get a WorkZone integration client
Ask IT for WzOAuth2 client_credentials: API host, token URL, client id, and secret. If the journal is on-prem, create a private link first (Integrations → Private links), then come back here.
- 2
Enter the API base (host only)
Example: https://workzone.kommune.dk. Do not append /odata. Northdocs calls {base}/odata/Files (cases) and {base}/odata/Documents (files).
- 3
Paste the token URL and client
Token URL is often Entra or the WorkZone STS. Client id and secret go in Credentials. Token URL may stay public even when the journal API uses a private link.
- 4
Scope to a sandbox File
Put a non-production case id in Sandbox case id. Never point write-back at live citizen cases.
- 5
Connect, then browse
Connect mints a client_credentials token. Then Browse & import from the connector card. Native version write-back is supported on WorkZone Documents after sandbox certification.
Native version write-back is supported on WorkZone Documents.
See also: Danish ESDH connectors and ESDH write-back certification.
Related articles
Still need a hand?