Skip to main content

Integrations

OpenBuild is the composition layer of the Conduction ecosystem. Each built app reuses the same supporting services every other Conduction app uses — there's no second data layer, no second connector framework, no second document engine.

OpenRegister — the data layer​

Every OpenBuild app's data lives in OpenRegister. Specifically:

  • the parent Application record and its ApplicationVersion rows live in the shared openbuild register;
  • each ApplicationVersion gets its own per-version register (openbuild-{appSlug}-{versionSlug}) seeded with the version's schemas and rows;
  • the BuiltAppRoute index (slug → applicationUuid) gives /apps/openbuild/{slug} its O(1) lookup.

OpenRegister contributes the audit trail (every mutation logged), object time travel (rewind any record to its state at time T), declarative state machines (ADR-031), per-record RBAC, organisation-wide multi-tenancy, and the schema validator.

Schemas you author in OpenBuild are first-class OpenRegister schemas — they show up in the OpenRegister UI, validate against the same OAS-shape contract, and benefit from the same MCP tools.

OpenConnector — system integration​

When an OpenBuild app needs to talk to a system outside Nextcloud — pull supplier data from G2, post a closed record into your ERP, fetch a TenderNed listing — it does so via OpenConnector. OpenConnector handles HTTP, OAuth, REST, SOAP, SFTP, and the mapping between external payloads and OpenRegister schemas.

A built app declares its integrations in the manifest; the connector source rows live in OpenConnector. When the manifest points at integrations.xwiki, OpenConnector exposes the matching live XWiki space through OpenBuild's integration sidebar.

Procest — business workflows​

Decisions, intakes, multi-step approvals — the state machine between the data lives in Procest. OpenBuild + Procest is the pattern for permit-tracking style apps: OpenBuild owns the application form and the manifest; Procest owns the how of moving an application from intake through decision.

The two are loosely coupled — Procest reacts to OpenRegister ObjectTransitionedEvents, so any OpenBuild-authored state transition can fire a Procest workflow without OpenBuild knowing.

Docudesk — document generation​

Turn an OpenBuild record into a PDF, DOCX or signed document via Docudesk. Common patterns:

  • intake confirmation PDF emailed on form submission;
  • agenda + meeting minutes printable export from a Decidesk-style virtual app;
  • signed decision letter for permit approvals.

Docudesk reads the schema (templates bind to schema property paths) and the record (data) and emits the file. OpenBuild apps reference Docudesk templates by slug in their manifest's actions[] declarations.

NL Design System — government theming​

OpenBuild apps inherit the NL Design System tokens via the nldesign Nextcloud theme. When nldesign is enabled, OpenBuild's UI — buttons, inputs, modals, headings, colours — automatically conforms to the Dutch government's design standards, ensuring WCAG AA compliance and visual consistency with the rest of your municipal estate.

No app-side opt-in: it's a Nextcloud theme. Switch it on, every OpenBuild app + every sibling Conduction app re-themes.

MyDash — dashboards across apps​

When stakeholders need a cross-app view — "today's open intakes across every municipality department" — MyDash reads the OpenRegister GraphQL surface and renders widgets. OpenBuild apps expose their data as registers, so MyDash widgets work against an OpenBuild app the same way they work against any sibling app.

Larping App — gamification + onboarding​

Larping App provides onboarding flows, skill-tree progression, and gamified citizen-developer training inside Nextcloud. The "build your first OpenBuild app" tutorial lives there; OpenBuild opens its hello-world preset directly from the Larping tour.

Pluggable integration registry​

OpenBuild's pluggable integration registry (per nc-vue #202..#218 + openregister #1490 / #1493) means any future ecosystem app can publish a sidebar provider for OpenBuild's detail page. When DeskDesk, Decidesk, Pipelinq etc. add a provider, the OpenBuild app shell exposes their UI inline — no per-app patch.