Kommo → Domo
AI-first ETL from Kommo into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads Kommo into Domo
Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.
Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.
Ideal for all-in-one cloud BI with built-in ETL.
Endpoints
Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.
Domo: Cloud BI platform combining data integration and executive dashboards.
How Kommo entities map to Domo
| Kommo entity | Domo object | Notes |
|---|---|---|
| conversational CRM events | kommo_conversational_crm_events | date/time columns events |
| chats | kommo_chats | id PK · linked to kommo_conversational_crm_events |
| leads | kommo_leads | id PK · linked to kommo_conversational_crm_events |
| sales automation triggers | kommo_sales_automation_triggers | id PK · linked to kommo_conversational_crm_events |
FAQ
How does Datrise handle Kommo's custom fields in Domo?
Flexible values are stored as flattened columns for Magic ETL, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Domo types.
How does the Kommo to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for Kommo
Early access
Connect Kommo to Domo 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.