Real-time
Two-way sync
Changes in Kommo or Marketo instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Marketing
Kommo to Marketo integration — real-time, two-way sync
Keep Kommo and Marketo 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 Marketo
Keep the people you sell to and the people you market to in one shared view: Kommo and Marketo sync contacts, accounts, and engagement in real time, in both directions.
Kommo owns the customer relationship and the pipeline; Marketo 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 Pipelines & Statuses, Tasks, Notes, Custom Fields in Kommo with Companies, Opportunities and Opportunity Roles, Custom Objects, Activities and Lead Changes in Marketo 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 Marketo 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 Load purchase or product-usage records into Custom Objects linked to Leads so nurture campaigns branch on behavior mastered in another system.
- 04 Add or remove Leads on Static Lists or set Program Member status from lifecycle stage computed downstream, then run a trigger Smart Campaign against them.
Common sync patterns
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 Marketo captures engagement: activity lands on the record
Opens, clicks, form fills, event attendance, or ad responses recorded in Marketo post back to the contact or account in Kommo, so reps see interest before they reach out.
Lead and lifecycle status agree
Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.
What you can sync between Kommo and Marketo
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 | Marketo objects | How this pairing syncs | |
|---|---|---|---|
| Leads The central pipeline record; external signups and form fills sync in as leads. | Leads Core person records (called Leads/People), deduped on email address by default or a configured dedupe field; read via GET /rest/v1/leads.json with a filterType, upserted via POST /rest/v1/leads.json (action createOrUpdate/createOnly/updateOnly), bulk-imported via CSV through POST /bulk/v1/leads.json, and bulk-exported via /bulk/v1/leads/export/create.json. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Companies Organization records map to accounts in ERPs and invoicing tools. | Companies Company records linked to Leads via a company link field; read and upserted through /rest/v1/companies.json, typically mastered in a CRM or ERP and written into Marketo for account context. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Contacts Person records sync with other CRMs and databases for a shared contact file. | Custom Objects Auxiliary data tables described via /rest/v1/customobjects.json and read/written via /rest/v1/customobjects/{apiName}.json, linked to Leads by a dedupe/link field so campaigns branch on records like purchases or subscriptions. | Contacts is specific to Kommo and Custom Objects to Marketo — 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. | Activities and Lead Changes Engagement feed (opens, clicks, form fills, Data Value Changes) read via GET /rest/v1/activities.json using a paging token from /rest/v1/activities/pagingtoken.json (sinceDatetime), plus Get Lead Changes and Get Deleted Leads; read-only, also available via async Bulk Activity Extract. | Pipelines & Statuses is specific to Kommo and Activities and Lead Changes to Marketo — each maps to any object or custom field on the other side. | |
| Tasks Follow-up records keep rep activity consistent across systems. | Static Lists Named static lists; read via /rest/v1/lists.json, with Leads added or removed via POST and DELETE on /rest/v1/lists/{listId}/leads.json to control campaign membership from lifecycle logic computed downstream. | Tasks is specific to Kommo and Static Lists to Marketo — 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. | Programs and Program Members Marketing programs read via /rest/v1/programs.json; program membership and member status managed via /rest/v1/leads/programs/{programId}.json and the program status endpoint for acquisition and attribution reporting. | Notes is specific to Kommo and Programs and Program Members to Marketo — each maps to any object or custom field on the other side. |
How changes propagate between Kommo and Marketo
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 Marketo 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 Marketo through its API, with automatic retries and rate-limit backoff.
Marketo Kommo Interval-based propagation
DetectionStacksync polls Marketo for changes on an incremental schedule, reading only records changed since the previous pass. Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on.
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.
- Marketo: Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.
What ships with Kommo ⇄ Marketo
Connect Kommo and Marketo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Marketo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo or Marketo 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 Marketo record.
Observability
Monitoring
Track your Kommo ⇄ Marketo 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 Marketo.
How the Kommo and Marketo 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
Marketo
- Integration surface
- Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages
- Authentication
- OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026).
- Change detection
- Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on createdAt/updatedAt. Marketo's Webhooks are Smart Campaign flow-step outbound HTTP calls to a URL, not a general record-change subscription, so there is no push feed of arbitrary CRUD.
- Capabilities
- read · write
- Rate limits
- Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.
How it works
How to connect Kommo to Marketo — 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 Marketo 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
Marketo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo and Marketo 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 ⇄ MarketoCustomers 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 MarketoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Marketo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Marketo: authenticate both systems, choose the objects to sync (such as Kommo's Leads 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. Marketo: Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages. Authentication: OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026). Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: Kommo is the former amoCRM, and its data model centers on leads moving through configurable pipelines and statuses, with contacts and companies linked to each lead. Marketo: Interactive calls are limited to 100 per 20 seconds (error 606) and 10 concurrent calls (error 615) per instance, neither of which can be increased, under a default 50,000-calls-per-day quota that resets at midnight CST. Stacksync's field mapping accounts for these differences between Kommo and Marketo 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 Marketo records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Kommo and Marketo connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Kommo–Marketo integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Kommo and Marketo. 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 478 integrations available for Kommo and Marketo.
Popular · 8 of 478
-
Kommo ⇄ Salesforce Marketing Cloud -
Kommo ⇄ Cvent -
Kommo ⇄ Demandbase -
Kommo ⇄ Eloqua -
Marketo ⇄ Shopify -
Marketo ⇄ Affinity -
Marketo ⇄ 6sense -
Marketo ⇄ Apollo.io
No integrations match .
