Werkborg
NederlandsBook a call

Integrations

See which integrations still require evidence

This page defines the proposed evidence record for future connectors: status, scope, test date and known limitation. No production connector has been proven; local Service Intake adapter 1.1.0 performs zero external actions.

Intended delivery

A proposed integration matrix that will distinguish locally tested, pilot-tested and planned connectors only after separate testing.

Evidence required before delivery

  • Current local evidence: Service Intake adapter 1.1.0.
  • Frozen test set: 150 calibration and 120 holdout records.
  • Evidence boundary: zero external actions; email, CRM and business-software connectors are untested.

Authority boundary

What this solution explicitly does not promise

  1. 01

    Availability may vary by software version, API permission, contract and tenant configuration.

  2. 02

    A planned connector is never sold as supported.

A logo is not evidence

Connector readiness at this moment

IntegrationCurrent statusRequired before it is sold as supported
Microsoft 365 emailFirst production target · blocked

Tenant consent, exact required fields, mailbox scope, Graph permissions, paging/429/revocation and a test account.

Syntess / field serviceNot published as supported

API version, contract rights, test tenant and write scope are not yet proven.

SharePoint / OneDriveAssessment required

Site scope, document types, classification, permissions and retention.

Web form / webhookPilot candidate

Schema, authentication, rate limit, replay protection and an error queue.

Local JSON/CSV exportLOCAL · 2026-08-01 · 270 frozen synthetic records validated

Engine 1.1.0: app/operator/service-intake-engine.ts · schema: product/service-intake/contracts/export.schema.json · evidence manifest: product/service-intake/evidence/manifest.json. No production environment or customer acceptance.

Only the local, provider-neutral JSON/CSV contracts are tested. The 270 records prove only the contract and export checks: not model quality, customer results, a production connector or return on investment. No Microsoft 365, Syntess or other customer connector is sold as supported without a version, date, customer environment, permissions, failure tests and customer acceptance.

Next step

Start with one provable workflow.

No generic AI presentation. Bring volume, systems, exceptions and the human decision-maker.

Assess your systems

Logical next step

SolutionTurn a service request into a controlled work-order draftThe tested local adapter structures entered report text, identifies the customer, location, asset and issue, flags missing information and creates a reply and work-order draft only. Email, form and target-system connectors are not yet proven.TrustClaim security controls only with implementation evidenceThis page defines a proposed review structure for identity and access, encryption, secrets, development, backup and incident response. No production environment has yet been verified as evidence that these controls operate for Werkborg.TrustSee where your AI data comes from, goes and remainsThe proposed Werkborg data-flow format maps each implementation's components, data types, locations, transit, temporary and persistent storage, logging and deletion. No universal or production-validated data flow exists yet.