Concept 6 of 10

Connector

The bridge between systems — enabling integration, object publishing, and data exchange.

What Is a Connector?

A Connector is an Asset that makes communication between systems possible. It is the bridge between SeekBytes and a System, or between one part of a Project and another.

Depending on the design, a Connector may:

Connect to a specific external System
Expose or publish objects (business data items)
Subscribe to data from another Connector
Transform or route information
Enable one-way or two-way data exchange
Participate in secure machine-to-machine communication

Why Do Connectors Matter?

Connectors are one of the most practical building blocks on the platform. They make integration real. Without Connectors, a Project would know about Systems but would have no useful bridge for exchanging data and triggering meaningful movement between them.

Connectors and Objects

Connectors work with objects — business items or data structures that can be shared or synchronized. Examples of objects include:

Customer records
Invoices and purchase orders
Products and inventory updates
Tickets and work orders

A Connector can publish selected objects so that another Connector (or Automation) can use them. This publishing model is how data availability and exchange are structured.

Real-World Example

The IT team connects incident management to asset tracking:

A ServiceNow Connector publishes resolved incidents, affected assets, and resolution details.
A CMDB Connector subscribes to those published objects to update asset records and configuration items automatically.

The Connection between these two Connectors defines what data flows and in which direction.

Connectors in the AI Era

A Connector can remain purely integration-focused, or it can gain new capabilities through Agentic Capability:

Intelligent routing of data
AI-assisted field mapping
Semantic object handling
Anomaly detection in exchange behavior

Connectors can evolve without losing their original meaning.

What a Connector Is Not

A Connector is not the Tenant. A Connector is not the whole Project. A Connector is not necessarily the System itself — it is the active integration component that helps systems communicate.

Helpful Metaphor

If Systems are islands, Connectors are the bridges and shipping routes between them. They carry goods (objects/data) from one island to another, following agreed routes (Connections).

Short Definition

Connector: An asset that enables integration with a system, publishes objects, and exchanges data with other entities.