Can AI agents automate SmartDok?

SmartDok AS (Visma) · saas · constructionfield-service

SmartDok is automatable today through the SmartDok REST API, not through Zapier-class connectors. SmartDok AS, a Visma company, publishes an OpenAPI catalog at api.smartdok.no. Sales must enable API access. An administrator then creates a one-year API access token under Firmainnstillinger → API-administrasjon. That token is exchanged at POST /Authorize/ApiToken for a Bearer JWT session token used on later calls. The v1 catalog has 128 paths across time, projects, forms, RUE incidents, quality deviations, machines, goods, orders, and users, with GET, POST, PUT, and DELETE. Hours can be registered through POST /WorkHours. RUE and submitted-form reads include PDF export. Webhook subscriptions have create, read, update, and delete paths. PUT replaces the whole resource. Coverage is partial because access is sales-gated and some HMS objects are read-only in the published spec. The homepage and smartdok.com/integrations name packaged connections to Tripletex, Visma, PowerOffice, HMSREG, Microsoft 365, and Xledger. Those are vendor-operated ERP and register handoffs, not the product API. The public SmartDok GitHub org has no API catalog. Zapier, Make, Microsoft Power Automate, and n8n had no SmartDok connector on 2026-09-07. First-party MCP ownership is not established. Computer-use viability is unassessed. This record is the SmartDok construction field app. It is not Tripletex or another Visma ERP.

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

Modalities

ModalityStatusDetail
APIyesrestapi-access-tokenbearer-jwt
coverage: partial · docs
SDKunknown
official: unknown
MCPunknown
verdict: unknown
Integrationsno
CLIunknown
Extensibilityyespackaged-erp-integrations
webhooks: True
Data access
export: pdf · import: unknown
RPA / UI automationunknownweb-dom
No repeatable UI probe was run. Daily field work is time, HMS/KS, crew lists, machines, and documents in the hosted web client at web.smartdok.no and the SmartDok mobile app. The documented machine path is the SmartDok REST API. Packaged Tripletex, Visma, PowerOffice, and HMSREG connections are product integrations, not a substitute for that API. Tripletex and other Visma ERP products are outside this record.
Computer useunknown
measured verdicts only — "unknown" means not yet probed by us

Scores

apimcpintegrationsclirpacomputer useoverall
6—0———6

Evidence

FactTierSourceDate
homepagedeclaredsource2026-09-07
vendordeclaredsource2026-09-07
licensedeclaredsource2026-09-07
statusdeclaredsource2026-09-07
deploymentdeclaredsource2026-09-07
platformsdeclaredsource2026-09-07
modalities.api.existsdeclaredsource2026-09-07
modalities.api.existsdeclaredsource2026-09-07
modalities.api.kinds[0]declaredsource2026-09-07
modalities.api.auth[0]declaredsource2026-09-07
modalities.api.auth[0]declaredsource2026-09-07
modalities.api.auth[1]declaredsource2026-09-07
modalities.api.coveragedeclaredsource2026-09-07
modalities.api.docsdeclaredsource2026-09-07
modalities.extensibility.webhooksdeclaredsource2026-09-07
modalities.extensibility.scripting[0]declaredsource2026-09-07
modalities.data_access.export[0]declaredsource2026-09-07
modalities.rpa.ui_stack[0]declaredsource2026-09-07
modalities.integrations.zapierscrapedsource2026-09-07
modalities.integrations.makescrapedsource2026-09-07
modalities.integrations.power_automatescrapedsource2026-09-07
modalities.integrations.n8nscrapedsource2026-09-07
verdict.scores.integrationsscrapedsource2026-09-07
verdict.scores.apideclaredsource2026-09-07
modalities.agent_docs.llms_txtscrapedsource2026-09-07
modalities.mcp.first_partyscrapedsource2026-09-07
modalities.api.existsdeclaredsource2026-09-07
freshness.watch[0].urldeclaredsource2026-09-07
freshness.watch[1].urldeclaredsource2026-09-07
freshness.watch[2].urldeclaredsource2026-09-07

Related tools

Other products in this database that share a category with SmartDok.

Last verified 2026-09-07 · volatility medium · JSON record