Flexport to Supabase Integration
AI-first ETL from Flexport into Supabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Flexport into Supabase
Datrise syncs Flexport's shipments, containers, bookings, invoices, milestones, and products into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.
Ideal for app builders who want CRM data alongside their Supabase product data.
Endpoints
Flexport: Freight forwarding and supply chain visibility.
Supabase: Postgres platform with auth, storage, and realtime APIs.
How Flexport entities map to Supabase
| Flexport entity | Supabase object | Notes |
|---|---|---|
| shipments | flexport_shipments | id PK · custom fields → jsonb columns |
| containers | flexport_containers | id PK · linked to flexport_shipments |
| bookings | flexport_bookings | id PK · linked to flexport_shipments |
| invoices | flexport_invoices | id PK · linked to flexport_shipments |
FAQ
How does Datrise handle Flexport's custom fields in Supabase?
Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.
How does the Flexport to Supabase sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.
Related pipelines
More destinations for Flexport
Early access
Connect Flexport to Supabase the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.