Two-way sync
Changes in Intercom or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Invoice and payment state from Körber WMS shows on the account in Intercom, so reps see balances before promising the next order.
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Owners, territories, and org structure informed by Körber WMS stay current in Intercom.
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 | How this pairing syncs | |
|---|---|---|---|
| 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. | Data Events is specific to Intercom and Shipments to Körber WMS — 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. | Locations Bin and zone definitions scope inventory data during mapping. | Custom Data Attributes is specific to Intercom and Locations to Körber WMS — 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. | Tasks Warehouse task data supports labor and throughput reporting. | Tags is specific to Intercom and Tasks to Körber WMS — each maps to any object or custom field on the other side. | |
| 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. | Segments is specific to Intercom and Returns to Körber WMS — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Items Item definitions keep the WMS aligned with the ERP item master. | Admins & Teams is specific to Intercom and Items to Körber WMS — each maps to any object or custom field on the other side. | |
| 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. | Articles is specific to Intercom and Inventory to Körber WMS — each maps to any object or custom field on the other side. |
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.
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 Körber WMS through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Körber WMS for changes on an incremental schedule, reading only records changed since the previous pass. Polling or message/file-based export from the WMS host interface.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Körber WMS connection.
Changes in Intercom or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Körber WMS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Körber WMS record.
Track your Intercom ⇄ Körber WMS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Körber WMS.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 288 integrations available for Intercom and Körber WMS.