Can AI agents automate ACOS WebSak?
ACOS · saas · public-sectorrecords-management
This record covers ACOS WebSak only; no primary source established that the queue's discovered Uni-View label is the same product or a valid alias. WebSak is a cloud-hosted Norwegian case and archive system with substantial vendor-supported workflow and integration capability. Its Mottak+ module applies configurable rules to structured incoming data and reduces manual archival work. ACOS names automated integrations for Husbanken Kobo and Startlan, Landbruksdirektoratet, Arealplaner.no, email, Teams and external line-of-business systems, and says it integrates with most specialist systems. Public evidence also confirms that ACOS Cloud can enable Noark 4 web services for integrations. ACOS itself calls N4WS old and identifies security challenges, requiring customer setup, an integrating-system name, source IP and a dedicated archive section, so it is a constrained legacy path rather than a modern general API. Newer integration contracts may be available through the customer portal or procurement, but their protocols, schemas and authentication were not public enough to score. WebSak writes are records actions governed by Noark, access, retention and disclosure rules. No product-specific first-party MCP, general CLI, public SDK, repeatable visual RPA result or computer-use result was established.
Best path today: api · Overall automatability: 4/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | noark4-web-servicescustomer-credentialssource-ip-allowlist coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | unknown | verdict: unknown |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | noark4-web-servicesmottak-rulesstandard-integrationspartner-integrations webhooks: unknown |
| Data access | export: cases, records, documents, metadata, public-disclosure, reports · import: cases, records, documents, metadata, emails, form-submissions | |
| RPA / UI automation | unknown | web-domoffice-integrationmobile-web No repeatable UI probe was run. Contracted integrations and structured intake through Mottak+ are preferable to visual control for governed case and archive actions. The exact tenant, enabled modules, Noark interface, access rules, retention policy, custom workflow and disclosure boundary must be qualified before any write automation.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 4 | — | — | — | — | — | 4 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-08-17 |
platforms | declared | source | 2026-08-17 |
license | declared | source | 2026-08-17 |
modalities.api.exists | declared | source | 2026-08-17 |
modalities.api.kinds[0] | declared | source | 2026-08-17 |
modalities.api.auth[0] | declared | source | 2026-08-17 |
modalities.api.auth[1] | declared | source | 2026-08-17 |
modalities.api.coverage | declared | source | 2026-08-17 |
modalities.integrations | declared | source | 2026-08-17 |
modalities.extensibility.scripting | declared | source | 2026-08-17 |
modalities.data_access.export | declared | source | 2026-08-17 |
modalities.data_access.import | declared | source | 2026-08-17 |
verdict.scores.api | declared | source | 2026-08-17 |
freshness.watch[0].url | declared | source | 2026-08-17 |
freshness.watch[1].url | declared | source | 2026-08-17 |
freshness.watch[2].url | declared | source | 2026-08-17 |
Last verified 2026-08-17 · volatility high · JSON record