DatriseAI-first ETL

LionDesk Metabase

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

How Datrise loads LionDesk into Metabase

Datrise syncs LionDesk's contacts, accounts, deals, activities, and lifecycle events 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

LionDesk: Real estate CRM for leads, listings, and agent follow-up.

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

How LionDesk entities map to Metabase

LionDesk entityMetabase objectNotes
contactsliondesk_contactsid PK · custom fields → flattened columns for the question builder
accountsliondesk_accountsid PK · linked to liondesk_contacts
dealsliondesk_dealsid PK · linked to liondesk_contacts
activitiesliondesk_activitiestemporal columns for trends events

FAQ

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

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

Related pipelines

Early access

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