Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in Monday with the customer records in Kommo, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Monday holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Updates, Users, Workspaces, Boards in Monday to Notes, Custom Fields, Users, Chats in Kommo with bi-directional, real-time sync. Activity and record changes in Monday update the matching contact or account in Kommo, and CRM data flows the other way wherever Monday can store and use it.

Common use cases

  • 01 Write closed deals or provisioning records from a CRM or ERP into monday.com Items to kick off delivery and onboarding boards.
  • 02 Mirror monday.com Boards, Groups, and Subitems into a warehouse for cross-project reporting on status and timelines without CSV exports.
  • 03 Mirror pipeline stage changes into BI tools for forecasting
  • 04 Route leads that originate in WhatsApp or Instagram conversations into other systems of record

Common sync patterns

Where Monday can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Kommo sync into Monday, so people working there have the context without switching tools.

Where Monday handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Kommo, so sales sees open issues before the next call.

Where Monday supplies contact or company data

Enriched fields land directly on records in Kommo, and refreshes keep them from going stale.

What you can sync between Kommo and Monday

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 Monday objects How this pairing syncs
Users Account users map lead ownership to people in other systems. Users Account members referenced by people columns; read to resolve owner and assignee IDs to names and emails. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Updates Comment and activity threads attached to items; read out into a database for reporting or written back as notes. Chats is specific to Kommo and Updates to Monday — 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. Workspaces Top-level containers that hold boards; used to scope which boards a given sync covers. Leads is specific to Kommo and Workspaces to Monday — 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. Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. Contacts is specific to Kommo and Boards to Monday — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. Companies is specific to Kommo and Items to Monday — each maps to any object or custom field on the other side.
Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. Pipelines & Statuses is specific to Kommo and Subitems to Monday — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Monday

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 Monday 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 Monday through its API, with automatic retries and rate-limit backoff.

Monday Kommo Sub-second propagation

DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.

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.
  • Monday: Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window.
What ships with Kommo ⇄ Monday

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Kommo ⇄ Monday 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 Monday.

How the Kommo and Monday 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

Monday

Integration surface
GraphQL API (single endpoint, api.monday.com/v2)
Authentication
OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header
Change detection
Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field
Capabilities
read · write · webhooks
Rate limits
Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window
Monday setup guide
How it works

How to connect Kommo to Monday — 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 Kommo and Monday 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
    Kommo connected
    Monday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Kommo and Monday integration FAQ

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.

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 523 integrations available for Kommo and Monday.

Popular · 8 of 523
All Kommo integrations All Monday 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