OpenConnector
The integration layer for . REST, SOAP, GraphQL, file drops, message queues. Pulls data from your existing systems into typed registers without writing glue code.
No middleware. No nightly batch.
Configure a source, map fields to a register schema, set the trigger (webhook, schedule, manual), and OpenConnector keeps the register filled. Bidirectional: pushes back to the source when the register changes.
Six protocols, one config UI.
REST, SOAP, GraphQL, file drops (FTP / SFTP), message queues (RabbitMQ / Kafka), and database connectors (MySQL / PostgreSQL / MSSQL). Same configuration shape across all of them.
Schema-aware mapping.
Drop a register's JSON Schema in, OpenConnector generates the field mapping UI. Validation happens at the connector before the register is touched.
Triggers: webhook, schedule, manual.
Real-time webhooks for source systems that can push, cron-style schedules for those that can't, manual run for migration cut-overs. Mix and match.
Audit log per record.
Every connector run leaves a tamper-evident trail: source, target, fields touched, conflicts resolved. WOO and BIO compliance evidence shipped with the install.
Bidirectional sync.
OpenConnector pushes register changes back to the source when configured. Your zaaksysteem stays the system of record; the register is the queryable surface.
Partners shipping OpenConnector
Implementation, hosting, and integration partners that deliver OpenConnector to their customers. Pick the partner you already work with, or one whose stack matches yours.
Ship Conduction to your customers.
Three tiers: Host (ship our apps), Service (SLA + third-line support), Certified (trained, joint roadmap, tender-eligible). The apps stay open source, the relationship stays direct.
Apply through Support →Source to register, observed end to end.
Scroll the cards. Each pins as you reach it; the next slides up to cover.
REST, SOAP, GraphQL, file drops, message queues.
OpenConnector pulls from whatever your existing systems speak. Configure a source, point at a target register, and the data flows. No middleware, no glue code.
See the connectorLands in OpenRegister, validated on arrival.
Every record is mapped to a typed register schema. Bad data is rejected at the door, good data shows up in catalogue and dashboard the same minute.
See OpenRegisterWatch every run, retry the failures.
Each pipeline run logs to a register row. Failures are visible in MyDash, replays are a click. No black-box scheduler.
See MyDashOn every Nextcloud dashboard.
Install OpenConnector and the home screen tells you what is flowing, what is failing, and what needs a retry. Operations stays a one-tab job.
Recent runs
Last pipeline runs across every active source. Status hex (mint = ok, orange = retry, red = failed), source name, duration.
Pipeline health
Donut KPI of run outcomes this week. Click through to the run-by-run view; retry failures with one button.
Failed deliveries
Outbound deliveries that need attention. Source-system, error code, retry button. Empty in the happy path.
The bridge from anywhere to your registers.
OpenConnector is itself an integration plane. These are the three integrations users meet most often: routing email and files, talking to workflow engines, and calling LLM providers.
Route inbound email into the right register; route outbound documents from a register through Mail. The Mail and Files sidebars show pipeline status when an item is part of an active flow.
See the routing guide