Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in ServiceNow 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 ServiceNow 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 Knowledge Articles, Custom Tables, Incidents, Change Requests in ServiceNow to Tasks, Notes, Custom Fields, Users in Kommo with bi-directional, real-time sync. Activity and record changes in ServiceNow update the matching contact or account in Kommo, and CRM data flows the other way wherever ServiceNow can store and use it.

Common use cases

  • 01 Mirror incident and task data into Postgres or a warehouse for SLA and workload reporting
  • 02 Create ServiceNow tickets automatically from CRM cases and sync status back as agents work them
  • 03 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
  • 04 Keep customer records consistent between Kommo and invoicing or ERP systems

Common sync patterns

Where ServiceNow 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 ServiceNow supplies contact or company data

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

Where ServiceNow can store CRM context: fields kept current

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

What you can sync between Kommo and ServiceNow

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 ServiceNow objects How this pairing syncs
Tasks Follow-up records keep rep activity consistent across systems. Tasks The base task table that incidents, changes, and requests extend. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Contacts Person records sync with other CRMs and databases for a shared contact file. Configuration Items (CMDB) Asset and infrastructure records synced with discovery tools and asset databases. Contacts is specific to Kommo and Configuration Items (CMDB) to ServiceNow — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Users and Groups Sys_user and group tables synced with HR systems and identity providers. Companies is specific to Kommo and Users and Groups to ServiceNow — 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. Knowledge Articles Support content that can be mirrored to help centers or search indexes. Pipelines & Statuses is specific to Kommo and Knowledge Articles to ServiceNow — each maps to any object or custom field on the other side.
Notes Free-text and system notes attach context to synced leads and contacts. Custom Tables Scoped or u_-prefixed tables are addressable through the same Table API as standard ones. Notes is specific to Kommo and Custom Tables to ServiceNow — 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. Incidents The core ITSM ticket; commonly synced with engineering trackers and CRMs. Custom Fields is specific to Kommo and Incidents to ServiceNow — each maps to any object or custom field on the other side.

How changes propagate between Kommo and ServiceNow

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

ServiceNow Kommo Interval-based propagation

DetectionStacksync polls ServiceNow for changes on an incremental schedule, reading only records changed since the previous pass. Polling on sys_updated_on timestamps.

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.
  • ServiceNow: Subject to instance-level API rate limits and concurrency semaphores configured by administrators.
What ships with Kommo ⇄ ServiceNow

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

ServiceNow

Integration surface
REST API (Table, Import Set, and Aggregate APIs); SOAP remains for legacy integrations
Authentication
OAuth 2.0 or basic authentication against the instance
Change detection
Polling on sys_updated_on timestamps; instance admins can configure outbound push through business rules or Flow Designer
Capabilities
read · write
Rate limits
Subject to instance-level API rate limits and concurrency semaphores configured by administrators
How it works

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

    Choose tables

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

Kommo and ServiceNow 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
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 497 integrations available for Kommo and ServiceNow.

Popular · 8 of 497
All Kommo integrations All ServiceNow 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