DatriseAI-first ETL

Short.io to Supabase Integration

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

How Datrise loads Short.io into Supabase

Datrise syncs Short.io's links, domains, clicks, referrers, countries, and link tags 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

Short.io: Branded short links and click analytics.

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

How Short.io entities map to Supabase

Short.io entitySupabase objectNotes
linksshort_io_linksid PK · custom fields → jsonb columns
domainsshort_io_domainsid PK · linked to short_io_links
clicksshort_io_clicksid PK · linked to short_io_links
referrersshort_io_referrersid PK · linked to short_io_links

FAQ

How does Datrise handle Short.io'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 Short.io 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 Short.io 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.