Real-time
Two-way sync
Changes in Intercom or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ ERP
Intercom to Körber WMS integration — real-time, two-way sync
Keep Intercom and Körber WMS 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 Körber WMS
Close the gap between front office and back office: Intercom and Körber WMS share customers and status in real time, in both directions.
Intercom holds the customer relationship; Körber WMS runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Tags, Segments, Admins & Teams, Articles in Intercom with Orders, Shipments, Locations, Tasks in Körber WMS field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
- Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
- Consolidate warehouse task and throughput data into a BI warehouse for operations reporting
- Sync inventory positions from Körber WMS to an OMS or e-commerce platform so sellable stock reflects the warehouse
Where Körber WMS is the finance system of record: money status on the account
Invoice and payment state from Körber WMS shows on the account in Intercom, so reps see balances before promising the next order.
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Where Körber WMS manages people and org data: keep Intercom aligned
Owners, territories, and org structure informed by Körber WMS stay current in Intercom.
What you can sync between Intercom and Körber WMS
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 | Körber WMS objects | |
|---|---|---|
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Shipments Ship confirmations and tracking references return to the order source system. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Locations Bin and zone definitions scope inventory data during mapping. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Tasks Warehouse task data supports labor and throughput reporting. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Items Item definitions keep the WMS aligned with the ERP item master. | |
| Articles Help center content is accessible via API for knowledge sync and audits. | Inventory On-hand quantities by location feed availability in order-taking systems. |
What ships with Intercom ⇄ Körber WMS
Connect Intercom and Körber WMS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Körber WMS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom or Körber WMS 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 Körber WMS record.
Observability
Monitoring
Track your Intercom ⇄ Körber WMS 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 Körber WMS.
How the Intercom and Körber WMS 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
Körber WMS
- Integration surface
- Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware
- Authentication
- Credentials issued per deployment
- Change detection
- Polling or message/file-based export from the WMS host interface
- Capabilities
- read · write
- Rate limits
- Constrained by deployment architecture rather than published API rate limits
How it works
How to connect Intercom to Körber WMS — 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 Körber WMS 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
Körber WMS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom and Körber WMS 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 ⇄ Körber WMSCustomers 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 Körber WMSCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Körber WMS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Körber WMS: authenticate both systems, choose the objects to sync (such as Intercom's Data Events and Custom Data Attributes), 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 Körber WMS: Where Körber WMS is the finance system of record: money status on the account; One customer master; Where Körber WMS manages people and org data: keep Intercom aligned. Invoice and payment state from Körber WMS shows on the account in Intercom, so reps see balances before promising the next order.
-
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Körber WMS: Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware. Authentication: Credentials issued per deployment. 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. Körber WMS: As is typical for large-scale WMS deployments, integration with ERP hosts is usually implemented through defined host interfaces and middleware rather than a single public SaaS API, so the integration surface varies by deployment. Stacksync's field mapping accounts for these differences between Intercom and Körber WMS 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 Körber WMS records are not retained after a sync operation.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Intercom and Körber WMS.
Popular · 8 of 386
-
Intercom ⇄ JobBOSS² -
Intercom ⇄ Linnworks -
Intercom ⇄ Logiwa WMS - Intercom ⇄ Macola ERP
-
Körber WMS ⇄ Apollo.io -
Körber WMS ⇄ Clearbit -
Körber WMS ⇄ Close -
Körber WMS ⇄ Copper CRM
No integrations match .
