DatriseAI-first ETL

Recurly Supabase

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

How Datrise loads Recurly into Supabase

Datrise syncs Recurly's subscriptions, invoices, plans, transactions, and dunning events 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

Recurly: Subscription management and recurring billing platform.

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

How Recurly entities map to Supabase

Recurly entitySupabase objectNotes
subscriptionsrecurly_subscriptionsid PK · custom fields → jsonb columns
invoicesrecurly_invoicesid PK · linked to recurly_subscriptions
plansrecurly_plansid PK · linked to recurly_subscriptions
transactionsrecurly_transactionsid PK · linked to recurly_subscriptions

FAQ

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