Connectors

A connector is an outbound pipeline that publishes data from Nexa’s consumption layer (the gold / C360 tables) to an external system — a database, a message queue, or object storage. Where a connection is just saved coordinates, a connector is the live job that moves rows. It publishes updates immediately after a change to the source entity (live mode) or on a schedule (batch mode). Manage connectors on the Connectors screen.

How a connector is put together

A connector binds three things:

1. A target system — Message Queue, RDS (JDBC Connection), or File System (Storage).
2. A connection of that target system, which supplies host/credentials.
3. One or more consumption source tables, each mapped to a target name in the external system.

The source tables come from the consumption layer built by data integration; the connector is the reverse-ETL step that pushes those curated tables back out to operational systems.

Connector list

The Connectors screen is a searchable, sortable, paginated table. Each row shows:

Column	Meaning
Connector Name	The name you gave it.
Alias	System-generated identifier used in API calls.
Target	The connection type (for example postgresql, kafka).
Connection Name	The connection it references.
Published Tables	The consumption tables it publishes.
Status	Current lifecycle state (see below).
Last Run	Timestamp of the most recent run.
Actions	Play/pause, view run logs, delete.

Filter by status and sync mode (live/batch), and sort by created date, last modified, or name.

Statuses

ActivePausedNot DeployedFailed

Status	Meaning
Not Deployed	Created in the app but not yet deployed to the data platform.
Active	Deployed and running — its trigger is unpaused.
Paused	Deployed but its trigger is paused; no new runs fire.
Failed	The most recent run failed. Open the run logs to diagnose.

Use the play/pause action to toggle a deployed connector between Active and Paused without deleting it. The view action opens the run logs for the connector’s job.

Note

Creating, editing, and deleting connectors are gated to non-production (dev) contexts. In production the list is read-only, and changes flow through review and promotion.

Lifecycle

1. Create a connector against a connection and select tables. It starts as Not Deployed. See Creating a connector.
2. Deploy it. The secret-sync pipeline copies the connection’s secret from GitHub into the data platform, and the connector’s job is created. It becomes Active.
3. Run — in live or batch mode. Pause/resume as needed.
4. Edit its published tables, or delete it when no longer needed.

Related

Creating a connectorSelect tables, map target names, and set sync mode.

Execution modesLive vs batch, and the cron scheduler.

Secret syncHow the connection secret reaches the data platform on deploy.

Connections overviewThe saved coordinates a connector references.