DatriseAI-first ETL

Typeform Metabase

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

How Datrise loads Typeform into Metabase

Datrise syncs Typeform's forms, responses, questions, workspaces, and completion metrics 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

Typeform: Conversational forms and response analytics.

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

How Typeform entities map to Metabase

Typeform entityMetabase objectNotes
formstypeform_formsid PK · custom fields → flattened columns for the question builder
responsestypeform_responsesid PK · linked to typeform_forms
questionstypeform_questionsid PK · linked to typeform_forms
workspacestypeform_workspacesid PK · linked to typeform_forms

FAQ

How does Datrise handle Typeform'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 Typeform to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Typeform 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.