A visual, event-driven workflow engine
Before any system can exchange data, something has to handle the unglamorous part: how to authenticate, which endpoints to call, how to page through results, what to do when a request times out. The System Connector handles all of it.
It is the technical contract with a single system. It knows how to sign in, how to call the system’s native API, and how to move data in and out reliably. It works with the system’s native objects, the shapes that system already passes and expects, so an automation can act on a system directly without any canonical translation.
Every Business Connector is built on top of a System Connector. The System Connector provides the connection. The Business Connector adds the business meaning. You can use the System Connector on its own, or build up from it.
What a System Connector handles
The connectivity essentials, built once and managed centrally, so no automation has to reinvent them.
System Connector first. Business Connector on top.
The two are not alternatives. One handles connectivity; the other adds business meaning on top of it.
One System Connector can power many things: a direct automation today, a full Business Connector tomorrow.
Use a System Connector directly when you just need to reach a system
When the job is “when X happens, call system Y,” you do not need canonical translation. The automation calls the System Connector and acts on the system in its native shape. No OES, no Business Connector required.
Connect
Point the System Connector at your system and authenticate once.
Trigger
An event in one system, or a schedule, kicks off the automation.
Call
The flow calls the system’s API through the connector, with retries and rate limits handled.
Act
Read, create, or update records in the target system, in its native format.
The base every Business Connector is built on
A Business Connector does not start from scratch. It starts from a System Connector. The connection, authentication, and API handling are already solved, so the work that remains is the valuable part: mapping the system to the OneEnterprise Specification (OES) and encoding its business rules.
That separation is deliberate. Connectivity changes rarely. Business meaning is where the depth lives. By keeping them in separate layers, a fix to an API endpoint never touches the business logic, and new business logic never breaks the connection.
Build connectivity once. Extend it anytime.
Specialist partners build the System Connector for a system they know, validate it, and publish it. That connectivity becomes the reliable base others can build a full Business Connector on, without re-solving authentication or API handling.
Build the plumbing once, and it works for every automation and every Business Connector on the platform.
