Real-time
Two-way sync
Changes in Kommo or Onelogin instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Security and identity
Kommo to Onelogin integration — real-time, two-way sync
Keep Kommo and Onelogin 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 Onelogin
Keep the people Kommo and Onelogin both track in agreement in real time: the internal users who own records in Kommo, and the customer login accounts in Onelogin.
A CRM and an identity system usually describe different populations. Kommo tracks customers, contacts, and the deals in motion; Onelogin governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Kommo are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Kommo are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Kommo, and a signup in Onelogin never reaches the account it belongs to.
Stacksync syncs Custom Fields, Users, Chats, Leads in Kommo with Apps (app instances), Groups, Mappings (mapping rules), Events in Onelogin in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.
Common use cases
- 01 Keep customer records consistent between Kommo and invoicing or ERP systems
- 02 Mirror pipeline stage changes into BI tools for forecasting
- 03 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
- 04 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
Common sync patterns
Where a closed deal should provision access: Kommo drives Onelogin
A won or activated customer in Kommo can create or update the corresponding user or account in Onelogin, so provisioning starts from the CRM record instead of a separate ticket.
Where Onelogin governs your workforce: CRM users kept current
New employees in Onelogin become active users in Kommo with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.
Deactivation and record hand-off
When someone is disabled in Onelogin, the matching user in Kommo is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
What you can sync between Kommo and Onelogin
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 | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Users Account users map lead ownership to people in other systems. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Companies Organization records map to accounts in ERPs and invoicing tools. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Companies is specific to Kommo and Authentication factors (MFA) to Onelogin — 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. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Pipelines & Statuses is specific to Kommo and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Tasks Follow-up records keep rep activity consistent across systems. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Tasks is specific to Kommo and Roles to Onelogin — 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. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Notes is specific to Kommo and Apps (app instances) to Onelogin — 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. | Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. | Custom Fields is specific to Kommo and Groups to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Kommo and Onelogin
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 Onelogin 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 Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Kommo Sub-second propagation
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
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.
- Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Kommo ⇄ Onelogin
Connect Kommo and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo or Onelogin 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 Onelogin record.
Observability
Monitoring
Track your Kommo ⇄ Onelogin 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 Onelogin.
How the Kommo and Onelogin 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
Onelogin
- Integration surface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
- Change detection
- Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
- Capabilities
- read · write · webhooks
- Rate limits
- Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works
How to connect Kommo to Onelogin — 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 Onelogin 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
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo and Onelogin 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 ⇄ OneloginCustomers 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 OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Onelogin: authenticate both systems, choose the objects to sync (such as Kommo's Users and Companies), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Onelogin: OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery. Authentication: OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: As a messenger-first CRM, chat threads from channels like WhatsApp and Instagram attach directly to leads, which is context most other CRMs lack when records are synced across. Onelogin: The Event Webhook (Event Broadcaster) delivers batches of events to a registered URL for near-real-time triggers, while the Events API filters by since/until for historical pulls; there is no database-level CDC. Stacksync's field mapping accounts for these differences between Kommo and Onelogin without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Kommo and Onelogin records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Kommo and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Kommo–Onelogin integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Kommo and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 516 integrations available for Kommo and Onelogin.
Popular · 8 of 516
-
Kommo ⇄ Jumpcloud -
Kommo ⇄ Active Directory - Kommo ⇄ Azure Active Directory
-
Kommo ⇄ Okta -
Onelogin ⇄ Freshsales -
Onelogin ⇄ Freshworks CRM -
Onelogin ⇄ Gladly -
Onelogin ⇄ Gorgias
No integrations match .
