--- title: "Kommo connector: setup and compatibility | Stacksync" description: "Kommo integration guide: plan Companies and Contacts, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/kommo last_modified: 2026-09-15 --- CRM · Two-way sync platform # Kommo integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Kommo workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Companies, Contacts and Leads. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Leads** - **Contacts** - **Companies** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=kommo) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Kommo records to discuss. These Kommo record examples help scope a technical review. They are not a list of verified Stacksync operations. Leads Retain the lead ID and record its relationship to any converted contact or company. Contacts Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Companies Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. ### See 3 more record examples Pipelines & Statuses Identify this record type and the operation you need to review with Stacksync. Tasks Use a stable task/work-item ID and preserve its project or parent-ticket reference. Notes Identify this record type and the operation you need to review with Stacksync. Connection setup ## Kommo connection requirements. Review Kommo access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Kommo account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Kommo, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Kommo integration. Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Kommo **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Load related records in the right order Resolve parent organizations, business units, and currency references before dependent transactions. ### Mapping checks by record type #### Companies Confirm object support with Stacksync Identity Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Fields to consider Source record ID · Legal or display name · Business-unit reference · Lifecycle status Related records to resolve first Resolve parent organizations, business units, and currency references before dependent transactions. Test before going live Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. #### Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. #### Leads Confirm object support with Stacksync Identity Retain the lead ID and record its relationship to any converted contact or company. Fields to consider Source lead ID · Qualification status · Owner reference · Conversion reference Related records to resolve first Resolve owner and campaign references and decide how conversion changes the identity relationship. Test before going live Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity. #### Tasks Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. #### Users Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Kommo integration in four steps. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### View the four setup tests and expected results 1. ### Confirm the intended Kommo account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Companies Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. **Expected result:** A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. 3. ### Test the operation your workflow needs Review one Kommo record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Kommo integration. ### Diagnose record matching, delayed changes, and rejected operations A Kommo record appears under the wrong destination record Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Resolve parent organizations, business units, and currency references before dependent transactions. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Kommo implementation’s change-detection method for Companies, Contacts and Leads. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Kommo object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Kommo workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=kommo) ## Kommo integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Kommo connector FAQ ### How should I plan an integration with Kommo? Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Kommo connector write changes back? Write-back support is not established for this connection. Review the Kommo records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Kommo data? Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. ### Which related records should I load first for Kommo? Resolve parent organizations, business units, and currency references before dependent transactions. ### How do I validate Kommo changes after the initial load? Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### What should I include when estimating Kommo integration costs? Estimate the number of Companies, Contacts and Leads records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades. AI assistant ## Set up Kommo from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Kommo and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Kommo. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Kommo record changes.” - “Create a Genie that answers questions about our Kommo data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Kommo connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Kommo and Odoo](https://www.stacksync.com/integrations/kommo-and-odoo) - [HubSpot and Kommo](https://www.stacksync.com/integrations/hubspot-and-kommo) - [Kommo and Twilio](https://www.stacksync.com/integrations/kommo-and-twilio) - [Kommo and Stripe](https://www.stacksync.com/integrations/kommo-and-stripe) - [Kommo and Microsoft Power BI](https://www.stacksync.com/integrations/kommo-and-microsoft-power-bi) - [Infobip and Kommo](https://www.stacksync.com/integrations/infobip-and-kommo) - [Aircall and Kommo](https://www.stacksync.com/integrations/aircall-and-kommo) - [Coupa and Kommo](https://www.stacksync.com/integrations/coupa-and-kommo) ### CRM · 45 - [Kommo and 6sense](https://www.stacksync.com/integrations/6sense-and-kommo) - [Kommo and Affinity](https://www.stacksync.com/integrations/affinity-and-kommo) - [Kommo and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-kommo) - [Kommo and Attio](https://www.stacksync.com/integrations/attio-and-kommo) - [Kommo and Chorusai](https://www.stacksync.com/integrations/chorusai-and-kommo) - [Kommo and Clari](https://www.stacksync.com/integrations/clari-and-kommo) - [Kommo and Clearbit](https://www.stacksync.com/integrations/clearbit-and-kommo) - [Kommo and Close](https://www.stacksync.com/integrations/close-and-kommo) - [Kommo and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-kommo) - [Kommo and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-kommo) - [Kommo and Crustdata](https://www.stacksync.com/integrations/crustdata-and-kommo) - [Kommo and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-kommo) - [Kommo and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-kommo) - [Kommo and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-kommo) - [Kommo and Freshsales](https://www.stacksync.com/integrations/freshsales-and-kommo) - [Kommo and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-kommo) - [Kommo and Gladly](https://www.stacksync.com/integrations/gladly-and-kommo) - [Kommo and Gong](https://www.stacksync.com/integrations/gong-and-kommo) - [Kommo and Gorgias](https://www.stacksync.com/integrations/gorgias-and-kommo) - [Kommo and HubSpot](https://www.stacksync.com/integrations/hubspot-and-kommo) - [Kommo and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-kommo) - [Kommo and Insightly](https://www.stacksync.com/integrations/insightly-and-kommo) - [Kommo and Intercom](https://www.stacksync.com/integrations/intercom-and-kommo) - [Kommo and Kustomer](https://www.stacksync.com/integrations/kommo-and-kustomer) - [Kommo and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/kommo-and-microsoft-dynamics-365-sales) - [Kommo and Nimble](https://www.stacksync.com/integrations/kommo-and-nimble) - [Kommo and Nutshell](https://www.stacksync.com/integrations/kommo-and-nutshell) - [Kommo and Oracle CX Sales](https://www.stacksync.com/integrations/kommo-and-oracle-cx-sales) - [Kommo and Outreach](https://www.stacksync.com/integrations/kommo-and-outreach) - [Kommo and Pipedrive](https://www.stacksync.com/integrations/kommo-and-pipedrive) - [Kommo and Salesforce](https://www.stacksync.com/integrations/kommo-and-salesforce) - [Kommo and Salesloft](https://www.stacksync.com/integrations/kommo-and-salesloft) - [Kommo and SAP Sales Cloud](https://www.stacksync.com/integrations/kommo-and-sap-sales-cloud) - [Kommo and Seismic](https://www.stacksync.com/integrations/kommo-and-seismic) - [Kommo and Shopify](https://www.stacksync.com/integrations/kommo-and-shopify) - [Kommo and Streak CRM](https://www.stacksync.com/integrations/kommo-and-streak-crm) - [Kommo and SugarCRM](https://www.stacksync.com/integrations/kommo-and-sugarcrm) - [Kommo and Twenty CRM](https://www.stacksync.com/integrations/kommo-and-twenty-crm) - [Kommo and Veeva CRM](https://www.stacksync.com/integrations/kommo-and-veeva-crm) - [Kommo and Vitally](https://www.stacksync.com/integrations/kommo-and-vitally) - [Kommo and Vtiger CRM](https://www.stacksync.com/integrations/kommo-and-vtiger-crm) - [Kommo and Xactly](https://www.stacksync.com/integrations/kommo-and-xactly) - [Kommo and Zoho CRM](https://www.stacksync.com/integrations/kommo-and-zoho-crm) - [Kommo and Zoho SalesIQ](https://www.stacksync.com/integrations/kommo-and-zoho-salesiq) - [Kommo and ZoomInfo](https://www.stacksync.com/integrations/kommo-and-zoominfo) ### ERP · 34 - [Kommo and Acumatica](https://www.stacksync.com/integrations/acumatica-and-kommo) - [Kommo and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-kommo) - [Kommo and Cin7](https://www.stacksync.com/integrations/cin7-and-kommo) - [Kommo and DEAR Inventory](https://www.stacksync.com/integrations/dear-inventory-and-kommo) - [Kommo and Dynamics 365 Business Central](https://www.stacksync.com/integrations/kommo-and-microsoft-dynamics-365-business-central) - [Kommo and Dynamics 365 F&O](https://www.stacksync.com/integrations/dynamics-365-finance-operations-and-kommo) - [Kommo and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-kommo) - [Kommo and Extensiv (3PL Central)](https://www.stacksync.com/integrations/extensiv-3pl-central-and-kommo) - [Kommo and Fishbowl Manufacturing](https://www.stacksync.com/integrations/fishbowl-manufacturing-and-kommo) - [Kommo and Infor CloudSuite](https://www.stacksync.com/integrations/infor-cloudsuite-and-kommo) - [Kommo and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-kommo) - [Kommo and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-kommo) - [Kommo and Linnworks](https://www.stacksync.com/integrations/kommo-and-linnworks) - [Kommo and Macola ERP](https://www.stacksync.com/integrations/kommo-and-macola-erp) - [Kommo and Microsoft Dynamics GP](https://www.stacksync.com/integrations/kommo-and-microsoft-dynamics-gp) - [Kommo and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/kommo-and-microsoft-dynamics-nav) - [Kommo and NetSuite](https://www.stacksync.com/integrations/kommo-and-netsuite) - [Kommo and Odoo](https://www.stacksync.com/integrations/kommo-and-odoo) - [Kommo and Oracle Fusion ERP](https://www.stacksync.com/integrations/kommo-and-oracle-fusion-erp) - [Kommo and Plex ERP](https://www.stacksync.com/integrations/kommo-and-plex-erp) - [Kommo and QAD ERP](https://www.stacksync.com/integrations/kommo-and-qad-erp) - [Kommo and Rootstock ERP](https://www.stacksync.com/integrations/kommo-and-rootstock-erp) - [Kommo and Sage 100](https://www.stacksync.com/integrations/kommo-and-sage-100) - [Kommo and Sage 300](https://www.stacksync.com/integrations/kommo-and-sage-300) - [Kommo and Sage Intacct](https://www.stacksync.com/integrations/kommo-and-sage-intacct) - [Kommo and Sage X3](https://www.stacksync.com/integrations/kommo-and-sage-x3) - [Kommo and SAP](https://www.stacksync.com/integrations/kommo-and-sap) - [Kommo and SAP Business ByDesign](https://www.stacksync.com/integrations/kommo-and-sap-business-bydesign) - [Kommo and SAP Business One](https://www.stacksync.com/integrations/kommo-and-sap-business-one) - [Kommo and SAP S/4HANA](https://www.stacksync.com/integrations/kommo-and-sap-s4hana) - [Kommo and SuiteAnalytics](https://www.stacksync.com/integrations/kommo-and-suite-analytics) - [Kommo and Syspro](https://www.stacksync.com/integrations/kommo-and-syspro) - [Kommo and TikTok Shop](https://www.stacksync.com/integrations/kommo-and-tiktok) - [Kommo and Unleashed Software](https://www.stacksync.com/integrations/kommo-and-unleashed-software) ### Database · 49 - [Kommo and Airtable](https://www.stacksync.com/integrations/airtable-and-kommo) - [Kommo and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-kommo) - [Kommo and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-kommo) - [Kommo and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-kommo) - [Kommo and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-kommo) - [Kommo and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-kommo) - [Kommo and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-kommo) - [Kommo and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-kommo) - [Kommo and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-kommo) - [Kommo and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-kommo) - [Kommo and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-kommo) - [Kommo and Citus](https://www.stacksync.com/integrations/citus-and-kommo) - [Kommo and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-kommo) - [Kommo and Couchbase](https://www.stacksync.com/integrations/couchbase-and-kommo) - [Kommo and DuckDB](https://www.stacksync.com/integrations/duckdb-and-kommo) - [Kommo and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-kommo) - [Kommo and Firebase](https://www.stacksync.com/integrations/firebase-and-kommo) - [Kommo and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-kommo) - [Kommo and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-kommo) - [Kommo and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-kommo) - [Kommo and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-kommo) - [Kommo and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-kommo) - [Kommo and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-kommo) - [Kommo and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-kommo) - [Kommo and JDBC](https://www.stacksync.com/integrations/jdbc-and-kommo) - [Kommo and MariaDB](https://www.stacksync.com/integrations/kommo-and-mariadb) - [Kommo and MarkLogic](https://www.stacksync.com/integrations/kommo-and-marklogic) - [Kommo and MongoDB](https://www.stacksync.com/integrations/kommo-and-mongodb) - [Kommo and MySQL](https://www.stacksync.com/integrations/kommo-and-mysql) - [Kommo and Neo4j](https://www.stacksync.com/integrations/kommo-and-neo4j) - [Kommo and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/kommo-and-oci-database) - [Kommo and OpenSearch](https://www.stacksync.com/integrations/kommo-and-opensearch) - [Kommo and Oracle DB](https://www.stacksync.com/integrations/kommo-and-oracle-db) - [Kommo and Postgres Heroku](https://www.stacksync.com/integrations/kommo-and-postgres-heroku) - [Kommo and PostgreSQL](https://www.stacksync.com/integrations/kommo-and-postgresql) - [Kommo and RavenDB](https://www.stacksync.com/integrations/kommo-and-ravendb) - [Kommo and Redis Enterprise](https://www.stacksync.com/integrations/kommo-and-redis-enterprise) - [Kommo and Reltio](https://www.stacksync.com/integrations/kommo-and-reltio) - [Kommo and Render Postgres](https://www.stacksync.com/integrations/kommo-and-render-postgres) - [Kommo and SAP ASE (Sybase)](https://www.stacksync.com/integrations/kommo-and-sap-ase-sybase) - [Kommo and SAP HANA](https://www.stacksync.com/integrations/kommo-and-sap-hana) - [Kommo and Scaleway Postgres](https://www.stacksync.com/integrations/kommo-and-scaleway-postgres) - [Kommo and SingleStore](https://www.stacksync.com/integrations/kommo-and-singlestore) - [Kommo and SQL Server](https://www.stacksync.com/integrations/kommo-and-sql-server) - [Kommo and Supabase](https://www.stacksync.com/integrations/kommo-and-supabase) - [Kommo and TiDB](https://www.stacksync.com/integrations/kommo-and-tidb) - [Kommo and TimescaleDB](https://www.stacksync.com/integrations/kommo-and-timescaledb) - [Kommo and VoltDB](https://www.stacksync.com/integrations/kommo-and-voltdb) - [Kommo and YugabyteDB](https://www.stacksync.com/integrations/kommo-and-yugabytedb) ### Data warehouse · 29 - [Kommo and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-kommo) - [Kommo and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-kommo) - [Kommo and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-kommo) - [Kommo and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-kommo) - [Kommo and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-kommo) - [Kommo and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-kommo) - [Kommo and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-kommo) - [Kommo and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-kommo) - [Kommo and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-kommo) - [Kommo and BigQuery](https://www.stacksync.com/integrations/bigquery-and-kommo) - [Kommo and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-kommo) - [Kommo and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-kommo) - [Kommo and Databricks](https://www.stacksync.com/integrations/databricks-and-kommo) - [Kommo and Dremio](https://www.stacksync.com/integrations/dremio-and-kommo) - [Kommo and Exasol](https://www.stacksync.com/integrations/exasol-and-kommo) - [Kommo and Firebolt](https://www.stacksync.com/integrations/firebolt-and-kommo) - [Kommo and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-kommo) - [Kommo and Greenplum](https://www.stacksync.com/integrations/greenplum-and-kommo) - [Kommo and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-kommo) - [Kommo and Materialize](https://www.stacksync.com/integrations/kommo-and-materialize) - [Kommo and MotherDuck](https://www.stacksync.com/integrations/kommo-and-motherduck) - [Kommo and Rockset](https://www.stacksync.com/integrations/kommo-and-rockset) - [Kommo and Snowflake](https://www.stacksync.com/integrations/kommo-and-snowflake) - [Kommo and Starburst Enterprise](https://www.stacksync.com/integrations/kommo-and-starburst-enterprise) - [Kommo and StarRocks](https://www.stacksync.com/integrations/kommo-and-starrocks) - [Kommo and Teradata Vantage](https://www.stacksync.com/integrations/kommo-and-teradata-vantage) - [Kommo and Tinybird](https://www.stacksync.com/integrations/kommo-and-tinybird) - [Kommo and Vertica](https://www.stacksync.com/integrations/kommo-and-vertica) - [Kommo and Yellowbrick](https://www.stacksync.com/integrations/kommo-and-yellowbrick) ### Business productivity · 34 - [Kommo and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-kommo) - [Kommo and Agiloft](https://www.stacksync.com/integrations/agiloft-and-kommo) - [Kommo and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-kommo) - [Kommo and Asana](https://www.stacksync.com/integrations/asana-and-kommo) - [Kommo and BetterContact](https://www.stacksync.com/integrations/better-contact-and-kommo) - [Kommo and Braze](https://www.stacksync.com/integrations/braze-and-kommo) - [Kommo and Campfire](https://www.stacksync.com/integrations/campfire-and-kommo) - [Kommo and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-kommo) - [Kommo and Customer.io](https://www.stacksync.com/integrations/customer-io-and-kommo) - [Kommo and Docusign](https://www.stacksync.com/integrations/docusign-and-kommo) - [Kommo and Front](https://www.stacksync.com/integrations/front-and-kommo) - [Kommo and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-kommo) - [Kommo and Gainsight](https://www.stacksync.com/integrations/gainsight-and-kommo) - [Kommo and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-kommo) - [Kommo and GitHub](https://www.stacksync.com/integrations/github-and-kommo) - [Kommo and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-kommo) - [Kommo and Ironclad](https://www.stacksync.com/integrations/ironclad-and-kommo) - [Kommo and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-kommo) - [Kommo and Lemlist](https://www.stacksync.com/integrations/kommo-and-lemlist) - [Kommo and Lusha](https://www.stacksync.com/integrations/kommo-and-lusha) - [Kommo and Microsoft 365](https://www.stacksync.com/integrations/kommo-and-microsoft-365) - [Kommo and Microsoft Dynamics 365](https://www.stacksync.com/integrations/kommo-and-microsoft-dynamics-365) - [Kommo and Monday](https://www.stacksync.com/integrations/kommo-and-monday) - [Kommo and Notion](https://www.stacksync.com/integrations/kommo-and-notion) - [Kommo and Quip](https://www.stacksync.com/integrations/kommo-and-quip) - [Kommo and Resend](https://www.stacksync.com/integrations/kommo-and-resend) - [Kommo and SendGrid](https://www.stacksync.com/integrations/kommo-and-sendgrid) - [Kommo and ServiceMax](https://www.stacksync.com/integrations/kommo-and-servicemax) - [Kommo and ServiceNow](https://www.stacksync.com/integrations/kommo-and-servicenow) - [Kommo and Smartsheet](https://www.stacksync.com/integrations/kommo-and-smartsheet) - [Kommo and SysAid](https://www.stacksync.com/integrations/kommo-and-sysaid) - [Kommo and Twilio](https://www.stacksync.com/integrations/kommo-and-twilio) - [Kommo and Wrike](https://www.stacksync.com/integrations/kommo-and-wrike) - [Kommo and Zendesk](https://www.stacksync.com/integrations/kommo-and-zendesk) ### Accounting and finance · 17 - [Kommo and Adyen](https://www.stacksync.com/integrations/adyen-and-kommo) - [Kommo and Anaplan](https://www.stacksync.com/integrations/anaplan-and-kommo) - [Kommo and BILL](https://www.stacksync.com/integrations/bill-and-kommo) - [Kommo and Braintree](https://www.stacksync.com/integrations/braintree-and-kommo) - [Kommo and Chargebee](https://www.stacksync.com/integrations/chargebee-and-kommo) - [Kommo and Coupa](https://www.stacksync.com/integrations/coupa-and-kommo) - [Kommo and Hyperline](https://www.stacksync.com/integrations/hyperline-and-kommo) - [Kommo and LogiSense](https://www.stacksync.com/integrations/kommo-and-logisense) - [Kommo and Navan](https://www.stacksync.com/integrations/kommo-and-navan) - [Kommo and Pigment](https://www.stacksync.com/integrations/kommo-and-pigment) - [Kommo and QuickBooks](https://www.stacksync.com/integrations/kommo-and-quickbooks) - [Kommo and Ramp](https://www.stacksync.com/integrations/kommo-and-ramp) - [Kommo and Recurly](https://www.stacksync.com/integrations/kommo-and-recurly) - [Kommo and Rillet](https://www.stacksync.com/integrations/kommo-and-rillet) - [Kommo and Stripe](https://www.stacksync.com/integrations/kommo-and-stripe) - [Kommo and Workday](https://www.stacksync.com/integrations/kommo-and-workday) - [Kommo and Zuora](https://www.stacksync.com/integrations/kommo-and-zuora) ### AI · 5 - [Kommo and Anthropic](https://www.stacksync.com/integrations/anthropic-and-kommo) - [Kommo and Autopilot](https://www.stacksync.com/integrations/autopilot-and-kommo) - [Kommo and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-kommo) - [Kommo and OpenAI](https://www.stacksync.com/integrations/kommo-and-openai) - [Kommo and Pinecone](https://www.stacksync.com/integrations/kommo-and-pinecone) ### Analytics · 7 - [Kommo and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-kommo) - [Kommo and Microsoft Power BI](https://www.stacksync.com/integrations/kommo-and-microsoft-power-bi) - [Kommo and Mixpanel](https://www.stacksync.com/integrations/kommo-and-mixpanel) - [Kommo and Pendo](https://www.stacksync.com/integrations/kommo-and-pendo) - [Kommo and Splunk](https://www.stacksync.com/integrations/kommo-and-splunk) - [Kommo and Tableau](https://www.stacksync.com/integrations/kommo-and-tableau) - [Kommo and Treasure Data](https://www.stacksync.com/integrations/kommo-and-treasuredata) ### Communications · 6 - [Kommo and Aircall](https://www.stacksync.com/integrations/aircall-and-kommo) - [Kommo and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-kommo) - [Kommo and Gmail](https://www.stacksync.com/integrations/gmail-and-kommo) - [Kommo and Infobip](https://www.stacksync.com/integrations/infobip-and-kommo) - [Kommo and RingCentral](https://www.stacksync.com/integrations/kommo-and-ringcentral) - [Kommo and Zoom](https://www.stacksync.com/integrations/kommo-and-zoom) ### E-commerce · 8 - [Kommo and Akeneo](https://www.stacksync.com/integrations/akeneo-and-kommo) - [Kommo and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-kommo) - [Kommo and ChannelEngine](https://www.stacksync.com/integrations/channelengine-and-kommo) - [Kommo and EasyPost](https://www.stacksync.com/integrations/easypost-and-kommo) - [Kommo and Magento](https://www.stacksync.com/integrations/kommo-and-magento) - [Kommo and NuORDER](https://www.stacksync.com/integrations/kommo-and-nuorder) - [Kommo and Shipwire](https://www.stacksync.com/integrations/kommo-and-shipwire) - [Kommo and Shopware](https://www.stacksync.com/integrations/kommo-and-shopware) ### Human resources · 13 - [Kommo and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-kommo) - [Kommo and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-kommo) - [Kommo and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-kommo) - [Kommo and Hibob](https://www.stacksync.com/integrations/hibob-and-kommo) - [Kommo and Jobvite](https://www.stacksync.com/integrations/jobvite-and-kommo) - [Kommo and Lever](https://www.stacksync.com/integrations/kommo-and-lever) - [Kommo and Namely](https://www.stacksync.com/integrations/kommo-and-namely) - [Kommo and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/kommo-and-oracle-fusion-cloud-hcm) - [Kommo and Paylocity](https://www.stacksync.com/integrations/kommo-and-paylocity) - [Kommo and SmartRecruiters](https://www.stacksync.com/integrations/kommo-and-smartrecruiters) - [Kommo and Success Factors](https://www.stacksync.com/integrations/kommo-and-success-factors) - [Kommo and UKG Pro](https://www.stacksync.com/integrations/kommo-and-ukg-pro) - [Kommo and UKG Ready](https://www.stacksync.com/integrations/kommo-and-ukg-ready) ### Marketing · 9 - [Kommo and Bingads](https://www.stacksync.com/integrations/bingads-and-kommo) - [Kommo and Cvent](https://www.stacksync.com/integrations/cvent-and-kommo) - [Kommo and Demandbase](https://www.stacksync.com/integrations/demandbase-and-kommo) - [Kommo and Eloqua](https://www.stacksync.com/integrations/eloqua-and-kommo) - [Kommo and Iterable](https://www.stacksync.com/integrations/iterable-and-kommo) - [Kommo and Marketo](https://www.stacksync.com/integrations/kommo-and-marketo) - [Kommo and RollWorks](https://www.stacksync.com/integrations/kommo-and-rollworks) - [Kommo and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/kommo-and-salesforce-marketing-cloud) - [Kommo and Twitter Ads](https://www.stacksync.com/integrations/kommo-and-twitter-ads) ### Security and identity · 6 - [Kommo and Active Directory](https://www.stacksync.com/integrations/active-directory-and-kommo) - [Kommo and Auth0](https://www.stacksync.com/integrations/auth0-and-kommo) - [Kommo and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-kommo) - [Kommo and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-kommo) - [Kommo and Okta](https://www.stacksync.com/integrations/kommo-and-okta) - [Kommo and OneLogin](https://www.stacksync.com/integrations/kommo-and-onelogin) ### Storage · 4 - [Kommo and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-kommo) - [Kommo and Box](https://www.stacksync.com/integrations/box-and-kommo) - [Kommo and Egnyte](https://www.stacksync.com/integrations/egnyte-and-kommo) - [Kommo and SharePoint](https://www.stacksync.com/integrations/kommo-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)