DatriseAI-first ETL

GitHub Supabase

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

How Datrise loads GitHub into Supabase

Datrise syncs GitHub's repositories, issues, pull requests, commits, and workflow runs 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

GitHub: Developer platform for repos, issues, and delivery workflows.

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

How GitHub entities map to Supabase

GitHub entitySupabase objectNotes
repositoriesgithub_repositoriesid PK · custom fields → jsonb columns
issuesgithub_issuesid PK · linked to github_repositories
pull requestsgithub_pull_requestsid PK · linked to github_repositories
commitsgithub_commitsid PK · linked to github_repositories

FAQ

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