Skip to content
CRM ⇄ Human resources

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

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

Keep the people who own accounts in Kommo in step with the workforce records in Namely, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Kommo runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Namely. Namely is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Pipelines & Statuses, Tasks, Notes, Custom Fields in Kommo with Groups, Teams, Reports, Profile Fields in Namely field by field, in real time, and in both directions. You decide which system owns which fields, so Namely stays authoritative on roles and org structure while Kommo keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Mirror pipeline stage changes into BI tools for forecasting
  • 02 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 03 Push Groups and Teams (departments, locations, team categories) into downstream apps to keep org structure and reporting lines aligned.
  • 04 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.

Common sync patterns

Where Namely tracks people the business also engages: contacts stay in sync

A person recorded in Namely, such as a candidate or applicant, can create or update the matching contact in Kommo, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Namely records a new hire, a matching user or owner is created in Kommo, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Namely, their accounts and territory assignments in Kommo update to match, so pipeline stays with the right owner.

What you can sync between Kommo and Namely

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 Namely objects How this pairing syncs
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Groups Departments and locations that organize Profiles; synced to keep org structure aligned with a warehouse or IdP. Custom Fields is specific to Kommo and Groups to Namely — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. Users is specific to Kommo and Teams to Namely — 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. Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. Chats is specific to Kommo and Reports to Namely — 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. Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. Leads is specific to Kommo and Profile Fields to Namely — 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. Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Contacts is specific to Kommo and Events to Namely — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Companies is specific to Kommo and Profiles to Namely — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Namely

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

Namely Kommo Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

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.
  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
What ships with Kommo ⇄ Namely

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
How it works

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

    Choose tables

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

Kommo and Namely 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 415 integrations available for Kommo and Namely.

Popular · 7 of 415
All Kommo integrations All Namely 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