DatriseAI-first ETL

Nimble Metabase

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

How Datrise loads Nimble into Metabase

Datrise syncs Nimble's relationship records, deals, tasks, and activity intelligence 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

Nimble: Relationship-focused CRM for SMB sales teams.

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

How Nimble entities map to Metabase

Nimble entityMetabase objectNotes
relationship recordsnimble_relationship_recordsid PK · custom fields → flattened columns for the question builder
dealsnimble_dealsid PK · linked to nimble_relationship_records
tasksnimble_tasksid PK · linked to nimble_relationship_records
activity intelligencenimble_activity_intelligencetemporal columns for trends events

FAQ

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

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

Related pipelines

Early access

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