Skip to content
CRM ⇄ Marketing

Kommo to Salesforce Marketing Cloud integration — real-time, two-way sync

Keep Kommo and Salesforce Marketing Cloud 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 Salesforce Marketing Cloud

Keep the people you sell to and the people you market to in one shared view: Kommo and Salesforce Marketing Cloud sync contacts, accounts, and engagement in real time, in both directions.

Kommo owns the customer relationship and the pipeline; Salesforce Marketing Cloud runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Users, Chats, Leads, Contacts in Kommo with Automations (Automation Studio), Tracking Events, Transactional Sends, Data Extensions in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — Kommo can own account and opportunity status while Salesforce Marketing Cloud owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 02 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
  • 03 Push CRM or warehouse audience segments into Data Extensions via the async rows API (background bulk insert) so marketing sends to freshly built audiences without manual CSV imports.
  • 04 Fire Journey Builder entry events (/interaction/v1/events) from an app or database when a contact acts, so behavioral journeys trigger on live events instead of scheduled batch loads.

Common sync patterns

Where Salesforce Marketing Cloud generates leads: hand-off without re-keying

New leads or responders captured in Salesforce Marketing Cloud flow into Kommo assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

New and updated people stay in step

When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.

Where Salesforce Marketing Cloud captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Salesforce Marketing Cloud post back to the contact or account in Kommo, so reps see interest before they reach out.

What you can sync between Kommo and Salesforce Marketing Cloud

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 Salesforce Marketing Cloud objects How this pairing syncs
Companies Organization records map to accounts in ERPs and invoicing tools. Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Companies is specific to Kommo and Transactional Sends to Salesforce Marketing Cloud — 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. Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. Pipelines & Statuses is specific to Kommo and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Tasks Follow-up records keep rep activity consistent across systems. Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Tasks is specific to Kommo and Contacts / Subscribers to Salesforce Marketing Cloud — 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. Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. Notes is specific to Kommo and Journeys (Journey Builder) to Salesforce Marketing Cloud — 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. Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Custom Fields is specific to Kommo and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Users is specific to Kommo and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Salesforce Marketing Cloud

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

Salesforce Marketing Cloud Kommo Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

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.
  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with Kommo ⇄ Salesforce Marketing Cloud

Connect Kommo and Salesforce Marketing Cloud for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Kommo ⇄ Salesforce Marketing Cloud 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 Salesforce Marketing Cloud.

How the Kommo and Salesforce Marketing Cloud 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

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
How it works

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

    Choose tables

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

Kommo and Salesforce Marketing Cloud 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 478 integrations available for Kommo and Salesforce Marketing Cloud.

Popular · 8 of 478
All Kommo integrations All Salesforce Marketing Cloud 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