Skip to content
Database ⇄ CRM

Elasticsearch to Kommo integration — real-time, two-way sync

Keep Elasticsearch and Kommo 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 Elasticsearch and Kommo

Treat Kommo like part of your database: its records live in Elasticsearch as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Elasticsearch, where it can be queried and joined like everything else.

Stacksync mirrors Leads, Contacts, Companies, Pipelines & Statuses from Kommo into Index mappings, Aliases, Data streams, Ingest pipelines in Elasticsearch with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kommo with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
  • Sync CRM accounts and contacts into an Elasticsearch index to power internal search across customer records.
  • Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Elasticsearch sync onto the matching records in Kommo, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Kommo API, limits, and retries.

Trigger workflows from CRM changes

Field and stage updates in Kommo arrive as row changes in Elasticsearch, ready to drive jobs and notifications.

What you can sync between Elasticsearch and Kommo

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.

Elasticsearch objects Kommo objects
Indices Target containers for synced records; each holds a table-like collection of JSON documents. Companies Organization records map to accounts in ERPs and invoicing tools.
Documents The unit of sync; JSON records created, updated, and deleted by _id. Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools.
Index mappings Field type definitions that determine how synced fields are indexed and queried. Tasks Follow-up records keep rep activity consistent across systems.
Aliases Stable read/write names that let a sync cut over between index versions without downtime. Notes Free-text and system notes attach context to synced leads and contacts.
Data streams Append-only targets for time-series or event data pushed from source systems. Custom Fields Per-entity custom fields hold data written from external databases and enrichment.
Ingest pipelines Server-side transforms applied to documents as a sync writes them. Users Account users map lead ownership to people in other systems.
What ships with Elasticsearch ⇄ Kommo

Connect Elasticsearch and Kommo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Kommo connection.

Real-time

Two-way sync

Changes in Elasticsearch or Kommo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Elasticsearch or Kommo 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 Elasticsearch or Kommo record.

Observability

Monitoring

Track your Elasticsearch ⇄ Kommo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Elasticsearch and Kommo.

How the Elasticsearch and Kommo connectors work

Elasticsearch

Integration surface
REST API (JSON over HTTP)
Authentication
API keys or basic authentication; Elastic Cloud also issues service account tokens
Change detection
Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks
Capabilities
read · write
Rate limits
No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity

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
How it works

How to connect Elasticsearch to Kommo — 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.

  1. 01

    Connect your apps

    Authenticate Elasticsearch and Kommo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Elasticsearch connected
    Kommo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Elasticsearch and Kommo 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Elasticsearch ⇄ Kommo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Elasticsearch Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Elasticsearch and Kommo integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Elasticsearch and Kommo.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.