Real-time
Two-way sync
Changes in Intercom or Shipwire instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ E-commerce
Intercom to Shipwire integration — real-time, two-way sync
Keep Intercom and Shipwire 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 Shipwire
Keep the customers and orders that Intercom and Shipwire share aligned in real time, so sales works from live purchase history and the store works from current account details.
Intercom holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Shipwire runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links Conversations, Tickets, Data Events, Custom Data Attributes in Intercom to Receivings, Returns, Purchase Orders, Trackings in Shipwire with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
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 Orders between a storefront or ERP database and Shipwire so new orders create fulfillment requests and Stacksync writes Trackings and status (processed, submitted, delivered) back.
- 04 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
Common sync patterns
Where Shipwire records orders: purchase history on the account
Orders and their status from Shipwire appear on the matching contact or account in Intercom, so reps see what a customer has bought and what is in flight before the next conversation.
New buyers become CRM records
A customer created in Shipwire creates or updates the matching contact or account in Intercom, so first-time and repeat buyers land in the relationship system without a manual import.
Contact and address details stay consistent
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
What you can sync between Intercom and Shipwire
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 | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Orders B2C fulfillment orders (create, update, cancel, get) with item, hold, routing, and tracking subresources; typically written from a storefront or ERP and synced back with status and trackings. | Tags is specific to Intercom and Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Products Catalog SKUs including kits, virtual kits, and marketplace products; created and edited via API, commonly mastered in a PIM or ERP and pushed into Shipwire with dimensions and pricing. | Segments is specific to Intercom and Products to Shipwire — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Admins & Teams is specific to Intercom and Stock to Shipwire — 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. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Articles is specific to Intercom and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Contacts is specific to Intercom and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Companies is specific to Intercom and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Intercom and Shipwire
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 Shipwire 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 Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Intercom Sub-second propagation
DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.
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.
- Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Intercom ⇄ Shipwire
Connect Intercom and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom or Shipwire 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 Shipwire record.
Observability
Monitoring
Track your Intercom ⇄ Shipwire 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 Shipwire.
How the Intercom and Shipwire 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
Shipwire
- Integration surface
- REST API (v3)
- Authentication
- Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
- Change detection
- Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
- Capabilities
- read · write · webhooks
- Rate limits
- No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works
How to connect Intercom to Shipwire — 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 Shipwire 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
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom and Shipwire 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 ⇄ ShipwireCustomers 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 ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Shipwire: authenticate both systems, choose the objects to sync (such as Intercom's Tags and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Intercom side: Conversations, Tickets, Data Events, Custom Data Attributes, plus custom fields where Intercom exposes them. On the Shipwire side: Receivings, Returns, Purchase Orders, Trackings. Stacksync auto-detects both schemas and converts types between the two systems.
-
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 Shipwire: Where Shipwire records orders: purchase history on the account; New buyers become CRM records; Contact and address details stay consistent. Orders and their status from Shipwire appear on the matching contact or account in Intercom, so reps see what a customer has bought and what is in flight before the next conversation.
-
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Shipwire: REST API (v3). Authentication: Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com). Stacksync manages authentication, retries, and rate limits on both sides.
-
Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Shipwire: Stock and Rates are effectively read-only (inventory levels and quote estimates); Orders, Products, Receivings, Returns, and Purchase Orders support create and update. Stacksync's field mapping accounts for these differences between Intercom and Shipwire without custom code.
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 471 integrations available for Intercom and Shipwire.
Popular · 8 of 471
-
Intercom ⇄ Akeneo -
Intercom ⇄ Bigcommerce -
Intercom ⇄ Channelengine -
Intercom ⇄ Easypost -
Shipwire ⇄ Affinity -
Shipwire ⇄ 6sense -
Shipwire ⇄ Apollo.io -
Shipwire ⇄ Clearbit
No integrations match .
