Can AI agents automate KMD WorkZone?

The best evidenced path into KMD WorkZone is the vendor-documented OData service. KMD's 2026.1 WorkZone docs state that OData is the data-service layer for create, read, update, and delete on entities in the WorkZone data dictionary, with Files (cases), Records, and Contacts as the main top-level collections. The modules overview names an open WorkZone API based on OData, PDF, Process, and WebDAV, plus a low-level Process API for organisation-specific workflow packages. Authentication is tenant-specific. The Export/Import tool documents authorizationType values MicrosoftIdentity (Entra ID), NTLM, and wzOAuth2 against a tenant OData URI. There is no self-serve public endpoint with a shared cloud API key. WorkZone Client is a browser application. WorkZone Mobile (Legacy) runs on iOS and Android. Deployment is hybrid: KMD sells WorkZone EU-Cloud as SaaS in a Danish datacenter, and the 2025 university press release states that University of Copenhagen, Aarhus University, and Aalborg University are moving to that cloud after years on the standard programme. Zapier, Make, Microsoft Power Automate, and n8n had no KMD WorkZone connector on 2026-08-31. First-party MCP ownership is not established. kmd.dk/llms.txt is a company-wide page list, not a WorkZone agent guide. This record is not KMD Nexus, Public 360, ACOS WebSak, Sikri Elements, cBrain F2, or Workday. Computer-use viability is unassessed. Records and access-control rules still govern every write.

Best path today: api · Overall automatability: 6/10