DatriseAI-first ETL

GitHub Metabase

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

How Datrise loads GitHub into Metabase

Datrise syncs GitHub's repositories, issues, pull requests, commits, and workflow runs into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

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

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How GitHub entities map to Metabase

GitHub entityMetabase objectNotes
repositoriesgithub_repositoriesid PK · custom fields → flattened columns for the question builder
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 Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the GitHub to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect GitHub to Metabase 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.