Kommo → GoodData
AI-first ETL from Kommo into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Kommo into GoodData
Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Kommo entities map to GoodData
| Kommo entity | GoodData object | Notes |
|---|---|---|
| conversational CRM events | kommo_conversational_crm_events | date dimensions 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 GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Kommo to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Kommo
Early access
Connect Kommo to GoodData 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.