Kommo → PlanetScale
AI-first ETL from Kommo into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads Kommo into PlanetScale
Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.
Ideal for horizontally scalable MySQL apps on Vitess.
Endpoints
Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How Kommo entities map to PlanetScale
| Kommo entity | PlanetScale object | Notes |
|---|---|---|
| conversational CRM events | kommo_conversational_crm_events | DATETIME 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 PlanetScale?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.
How does the Kommo to PlanetScale sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Kommo
Early access
Connect Kommo to PlanetScale 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.