DatriseAI-first ETL

LionDesk to ClickHouse Integration

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

How Datrise loads LionDesk into ClickHouse

Datrise syncs LionDesk's leads, contacts, deals, drip campaigns, tasks, and video messages into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

LionDesk: Real estate CRM with video messaging and drip campaigns.

ClickHouse: Columnar OLAP engine for fast aggregations.

How LionDesk entities map to ClickHouse

LionDesk entityClickHouse objectNotes
leadsliondesk_leadsid PK · custom fields → JSON or Map columns
contactsliondesk_contactsid PK · linked to liondesk_leads
dealsliondesk_dealsid PK · linked to liondesk_leads
drip campaignsliondesk_drip_campaignsid PK · linked to liondesk_leads

FAQ

How does Datrise handle LionDesk's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the LionDesk to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

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