DatriseAI-first ETL

Urban Airship Supabase

AI-first ETL from Urban Airship into Supabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Urban Airship into Supabase

Datrise syncs Urban Airship's records, events, and configuration objects 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

Urban Airship: SaaS or API data source for analytics and warehouse sync.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Urban Airship entities map to Supabase

Urban Airship entitySupabase objectNotes
recordsurban_airship_recordsid PK · custom fields → jsonb columns
eventsurban_airship_eventstimestamptz events
configuration objectsurban_airship_configuration_objectsid PK · linked to urban_airship_records

FAQ

How does Datrise handle Urban Airship'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 Urban Airship 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

Early access

Connect Urban Airship 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.