Real-time
Two-way sync
Changes in Kommo or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Kommo to Ukg Pro integration — real-time, two-way sync
Keep Kommo and Ukg Pro 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 Ukg Pro
Keep the people who own accounts in Kommo in step with the workforce records in Ukg Pro, 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 Ukg Pro. Ukg Pro 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 Custom Fields, Users, Chats, Leads in Kommo with Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables) in Ukg Pro field by field, in real time, and in both directions. You decide which system owns which fields, so Ukg Pro 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 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 02 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 03 Replicate Compensation and pay-statement / earnings history into a warehouse for headcount, labor-cost, and payroll reporting without manual BI exports.
- 04 Deprovision accounts by subscribing to UKG Pro termination and job-change webhook events to disable IdP and app access as changes become effective.
Common sync patterns
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Ukg Pro tracks people the business also engages: contacts stay in sync
A person recorded in Ukg Pro, 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 Ukg Pro 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.
What you can sync between Kommo and Ukg Pro
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 | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text and system notes attach context to synced leads and contacts. | Employee (Person Details) Core worker record with demographics and identifiers; read by listing employee IDs then fetching each profile, and created on hire via the personnel/onboarding endpoints. | Notes is specific to Kommo and Employee (Person Details) to Ukg Pro — 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. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Custom Fields is specific to Kommo and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Users Account users map lead ownership to people in other systems. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Users is specific to Kommo and Job / Position History to Ukg Pro — 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. | Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. | Chats is specific to Kommo and Compensation Details to Ukg Pro — 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. | Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. | Leads is specific to Kommo and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — 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. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Contacts is specific to Kommo and Terminations to Ukg Pro — each maps to any object or custom field on the other side. |
How changes propagate between Kommo and Ukg Pro
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 Ukg Pro 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 Ukg Pro through its API, with automatic retries and rate-limit backoff.
Ukg Pro Kommo Sub-second propagation
DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.
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.
- Ukg Pro: An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
What ships with Kommo ⇄ Ukg Pro
Connect Kommo and Ukg Pro for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Ukg Pro connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo or Ukg Pro 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 Ukg Pro record.
Observability
Monitoring
Track your Kommo ⇄ Ukg Pro 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 Ukg Pro.
How the Kommo and Ukg Pro 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
Ukg Pro
- Integration surface
- REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services
- Authentication
- Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint.
- Change detection
- No CDC stream. UKG Pro publishes Pro HCM Webhook Events for changes such as new hire, employee and job detail changes, termination, and PTO, which Stacksync subscribes to for near-real-time triggers; bulk and historical loads use paged reads with each service's modified-since filters.
- Capabilities
- read · write · webhooks
- Rate limits
- An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
How it works
How to connect Kommo to Ukg Pro — 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.
- 01
Connect your apps
Authenticate Kommo and Ukg Pro with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Kommo
connected
Ukg Pro
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo and Ukg Pro 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.
objects · Kommo ⇄ Ukg ProCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Kommo Ukg ProCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Ukg Pro integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Ukg Pro: authenticate both systems, choose the objects to sync (such as Kommo's Notes and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Kommo: Webhooks on record add and update events, plus polling for backfill. On Ukg Pro: No CDC stream. UKG Pro publishes Pro HCM Webhook Events for changes such as new hire, employee and job detail changes, termination, and PTO, which Stacksync subscribes to for near-real-time triggers; bulk and historical loads use paged reads with each service's modified-since filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kommo side: Custom Fields, Users, Chats, Leads, plus custom fields where Kommo exposes them. On the Ukg Pro side: Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Kommo and Ukg Pro: One directory of people; Where Ukg Pro tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Ukg Pro: REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services. Authentication: Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint. Stacksync manages authentication, retries, and rate limits on both sides.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 518 integrations available for Kommo and Ukg Pro.
Popular · 8 of 518
-
Kommo ⇄ Success Factors -
Kommo ⇄ Hibob -
Kommo ⇄ Ceridian Dayforce -
Kommo ⇄ D2l Brightspace -
Ukg Pro ⇄ Gladly -
Ukg Pro ⇄ Gorgias -
Ukg Pro ⇄ Infor CRM -
Ukg Pro ⇄ Insightly
No integrations match .
