Real-time
Two-way sync
Changes in Kommo or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Kommo to Treasuredata integration — real-time, two-way sync
Keep Kommo and Treasuredata in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kommo and Treasuredata
Put live Kommo data behind every dashboard and cohort in Treasuredata, and write the segments and scores Treasuredata computes back onto the Kommo record — one connection, not a nightly export.
Treasuredata turns data into dashboards, cohorts, and metrics; Kommo is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.
Stacksync syncs Notes, Custom Fields, Users, Chats from Kommo into Treasuredata field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Treasuredata write back to fields in Kommo, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
- 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
- 03 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 04 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
Common sync patterns
Where Kommo accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Treasuredata sync onto fields in Kommo, putting the analysis where reps and owners actually work the accounts.
One customer across analytics and CRM
The same account or person is keyed consistently in both systems, so a profile or row in Treasuredata lines up with the contact or account in Kommo.
A record that outlives edits in the CRM
A continuously synced copy of Kommo's records and activity in Treasuredata keeps a queryable history even as records change or age out of the CRM.
What you can sync between Kommo and Treasuredata
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Kommo objects | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text and system notes attach context to synced leads and contacts. | Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Notes is specific to Kommo and Journeys to Treasuredata — each maps to any object or custom field on the other side. | |
| Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. | Custom Fields is specific to Kommo and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Users Account users map lead ownership to people in other systems. | Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. | Users is specific to Kommo and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side. | |
| Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | Chats is specific to Kommo and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| Leads The central pipeline record; external signups and form fills sync in as leads. | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Leads is specific to Kommo and Databases to Treasuredata — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with other CRMs and databases for a shared contact file. | Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. | Contacts is specific to Kommo and Tables to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between Kommo and Treasuredata
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Kommo Treasuredata Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata Kommo Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kommo: Subject to per-account request rate limits.
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Kommo ⇄ Treasuredata
Connect Kommo and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo or Treasuredata data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Kommo or Treasuredata record.
Observability
Monitoring
Track your Kommo ⇄ Treasuredata sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kommo and Treasuredata.
How the Kommo and Treasuredata connectors work
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works
How to connect Kommo to Treasuredata — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Kommo and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Kommo
connected
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo and Treasuredata objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Kommo ⇄ TreasuredataCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Kommo TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Treasuredata: authenticate both systems, choose the objects to sync (such as Kommo's Notes and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Kommo: Webhooks on record add and update events, plus polling for backfill. On Treasuredata: Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Treasuredata side: Master (Parent) Segments, Segments, Journeys, Predictive Segments, plus custom fields where Treasuredata exposes them. On the Kommo side: Notes, Custom Fields, Users, Chats. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Kommo and Treasuredata: Where Kommo accepts updates: segments and scores back on the record; One customer across analytics and CRM; A record that outlives edits in the CRM. Cohorts, scores, and computed metrics from Treasuredata sync onto fields in Kommo, putting the analysis where reps and owners actually work the accounts.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Treasuredata: TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys. Authentication: API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints). Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 392 integrations available for Kommo and Treasuredata.
Popular · 8 of 392
-
Kommo ⇄ Microsoft Power Bi -
Kommo ⇄ Tableau -
Kommo ⇄ Adobeanalytics -
Kommo ⇄ Pendo -
Treasuredata ⇄ Attio -
Treasuredata ⇄ Pipedrive -
Treasuredata ⇄ Zoho CRM -
Treasuredata ⇄ Shopify
No integrations match .
