Skip to content
Database ⇄ CRM

InterSystems IRIS to Kommo integration — real-time, two-way sync

Keep InterSystems IRIS 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 InterSystems IRIS and Kommo

Treat Kommo like part of your database: its records live in InterSystems IRIS 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 InterSystems IRIS, where it can be queried and joined like everything else.

Stacksync mirrors Companies, Pipelines & Statuses, Tasks, Notes from Kommo into Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS 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

  • Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
  • Keep customer records consistent between Kommo and invoicing or ERP systems
  • Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting

Product events onto CRM records

Signup, usage, or lifecycle changes written to InterSystems IRIS 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 InterSystems IRIS, ready to drive jobs and notifications.

What you can sync between InterSystems IRIS 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.

InterSystems IRIS objects Kommo objects
Schemas Schema organization scopes which tables a sync connection can see. Contacts Person records sync with other CRMs and databases for a shared contact file.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Companies Organization records map to accounts in ERPs and invoicing tools.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools.
Namespaces Namespaces partition databases and determine the connection context for integrations. Tasks Follow-up records keep rep activity consistent across systems.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Notes Free-text and system notes attach context to synced leads and contacts.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Custom Fields Per-entity custom fields hold data written from external databases and enrichment.
What ships with InterSystems IRIS ⇄ Kommo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Kommo connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

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 InterSystems IRIS 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 InterSystems IRIS 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
    InterSystems IRIS connected
    Kommo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS 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 · InterSystems IRIS ⇄ 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
    InterSystems IRIS Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for InterSystems IRIS and Kommo.

Popular · 8 of 386
All InterSystems IRIS integrations All Kommo integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own