Real-time
Two-way sync
Changes in Intercom or Marketo instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Marketing
Intercom to Marketo integration — real-time, two-way sync
Keep Intercom 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 Intercom and Marketo
Keep the people you sell to and the people you market to in one shared view: Intercom and Marketo sync contacts, accounts, and engagement in real time, in both directions.
Intercom 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 Conversations, Tickets, Data Events, Custom Data Attributes in Intercom with Activities and Lead Changes, Static Lists, Programs and Program Members, Smart Campaigns in Marketo field by field, in real time, and in both directions. You decide which system owns which fields — Intercom 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 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 02 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
- 03 Two-way sync Marketo Leads with a Postgres or warehouse table, matched on email, so RevOps queries and updates marketing profiles in SQL while marketers keep working in Marketo.
- 04 Extract Marketo Activities (opens, clicks, form fills, Data Value Changes) through Bulk Activity Extract or Get Lead Activities into a warehouse for lead scoring and multi-touch attribution.
Common sync patterns
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 Intercom, 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.
Segments and audiences follow the CRM
Where Marketo builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Intercom, so who receives a campaign reflects current pipeline reality instead of a stale export.
What you can sync between Intercom 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.
| Intercom objects | Marketo objects | How this pairing syncs | |
|---|---|---|---|
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | 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. | |
| Conversations Support and sales threads sync outward for analytics and CRM context. | 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. | Conversations is specific to Intercom and Activities and Lead Changes to Marketo — each maps to any object or custom field on the other side. | |
| Tickets Structured ticket records track issues alongside conversational threads. | 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. | Tickets is specific to Intercom and Static Lists to Marketo — each maps to any object or custom field on the other side. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | 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. | Data Events is specific to Intercom and Programs and Program Members to Marketo — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Smart Campaigns Automation flows read via /rest/v1/campaigns.json and run against a set of Leads by requesting a trigger campaign with POST /rest/v1/campaigns/{id}/trigger.json, so downstream logic can push Leads into a Marketo flow. | Custom Data Attributes is specific to Intercom and Smart Campaigns to Marketo — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | 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. | Tags is specific to Intercom and Leads to Marketo — each maps to any object or custom field on the other side. |
How changes propagate between Intercom 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.
Intercom Marketo Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Marketo through its API, with automatic retries and rate-limit backoff.
Marketo Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Intercom: Subject to per-app rate limits on the Intercom API.
- 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 Intercom ⇄ Marketo
Connect Intercom and Marketo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Marketo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom 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 Intercom or Marketo record.
Observability
Monitoring
Track your Intercom ⇄ Marketo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Intercom and Marketo.
How the Intercom and Marketo connectors work
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
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 Intercom 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 Intercom 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.
Intercom
connected
Marketo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom 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 · Intercom ⇄ 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.
Intercom MarketoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Marketo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Marketo: authenticate both systems, choose the objects to sync (such as Intercom's Companies and Conversations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Intercom and Marketo: Where Marketo captures engagement: activity lands on the record; Lead and lifecycle status agree; Segments and audiences follow the CRM. Opens, clicks, form fills, event attendance, or ad responses recorded in Marketo post back to the contact or account in Intercom, so reps see interest before they reach out.
-
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. 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.
-
Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. Marketo: Activities and Lead Changes are read-only; Marketo's Webhooks feature is a Smart Campaign flow step that POSTs to an external URL, not a subscription feed of record changes, so incremental sync relies on polling. Stacksync's field mapping accounts for these differences between Intercom 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 Intercom and Marketo records are not retained after a sync operation.
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 473 integrations available for Intercom and Marketo.
Popular · 7 of 473
-
Intercom ⇄ Rollworks -
Intercom ⇄ Twitter Ads -
Intercom ⇄ Salesforce Marketing Cloud -
Intercom ⇄ Cvent -
Marketo ⇄ Copper CRM -
Marketo ⇄ Creatio CRM -
Marketo ⇄ Folk CRM
No integrations match .
