Workspace

CSV import & load

Name: Nexoxa Bridge
Author: Nexoxa

Upload spreadsheets into PostgreSQL tables with column mapping.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Client sends a 12 MB CSV of legacy products — 40 columns, inconsistent headers, one urgent ask: get it into Postgres tonight.

Sam opens CSV import, uploads the file, previews rows, maps Spreadsheet Header → products.sku, skips junk columns, runs bulk insert into staging. No one writes a brittle Python script that breaks on the next file format twist.

PostgreSQL-only by design — the right tool for relational bulk load, not a lowest-common-denominator importer.

Bridge path: /import

Step 1

Upload and preview

Sam drags products.csv in, scans first 50 rows for encoding surprises, fixes header row offset.
Preview catches doubled quotes before they become bad rows.

Upload spreadsheets into PostgreSQL tables with column mapping. Available on postgres:// connections. Upload → preview → map → insert pipeline at /import.

Step 2

Map columns deliberately

Legacy column PROD_SKU maps to sku; DESCRIPTION maps to name; empty maps to skip. Sam saves mapping mentally for the next monthly drop.
Type mismatches warn before insert.

Header-to-column mapping with type validation. Target table picker from catalog. Bulk insert with progress.

Step 3

Verify in the data grid

Insert completes — Sam opens Data grid on products, filters imported batch by created_at, spot-checks five rows.
Ticket closed; client thinks Sam is magic.

Post-import verification via Workspace → Data grid. Pair with Query lab for aggregate counts.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

Database connection URLs