DatriseAI-first ETL

Kommo Sisense

AI-first ETL from Kommo into Sisense. Governed entities, incremental sync, typed landing tables.

How Datrise loads Kommo into Sisense

Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Kommo entities map to Sisense

Kommo entitySisense objectNotes
conversational CRM eventskommo_conversational_crm_eventsdate/time fields events
chatskommo_chatsid PK · linked to kommo_conversational_crm_events
leadskommo_leadsid PK · linked to kommo_conversational_crm_events
sales automation triggerskommo_sales_automation_triggersid PK · linked to kommo_conversational_crm_events

FAQ

How does Datrise handle Kommo's custom fields in Sisense?

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

How does the Kommo to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Kommo to Sisense 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.