Real-time
Two-way sync
Changes in Bigcommerce or Intercom instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Bigcommerce to Intercom integration — real-time, two-way sync
Keep Bigcommerce and Intercom 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 Bigcommerce and Intercom
Keep the customers and orders that Intercom and Bigcommerce 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. Bigcommerce 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 Tags, Segments, Admins & Teams, Articles in Intercom to Brands, Inventory, Price Lists, Shipments in Bigcommerce 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 Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
- 02 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
- 03 Two-way sync of Products and Variants between BigCommerce and a PIM or ERP so catalog content, SKUs, and pricing stay aligned across systems.
- 04 Write Inventory levels from a WMS or ERP onto BigCommerce Variants and SKUs so storefront availability reflects warehouse on-hand counts.
Common sync patterns
Where Bigcommerce records orders: purchase history on the account
Orders and their status from Bigcommerce 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 Bigcommerce 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 Bigcommerce and 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.
| Bigcommerce objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Customers is specific to Bigcommerce and Contacts to Intercom — each maps to any object or custom field on the other side. | |
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Categories is specific to Bigcommerce and Companies to Intercom — each maps to any object or custom field on the other side. | |
| Brands Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent. | Conversations Support and sales threads sync outward for analytics and CRM context. | Brands is specific to Bigcommerce and Conversations to Intercom — each maps to any object or custom field on the other side. | |
| Inventory Product- or variant-level stock, plus multi-location counts via the V3 Inventory API; written from a WMS to reflect on-hand quantities. | Tickets Structured ticket records track issues alongside conversational threads. | Inventory is specific to Bigcommerce and Tickets to Intercom — each maps to any object or custom field on the other side. | |
| Price Lists V3 price lists and records driving customer-group and B2B pricing; pushed from an ERP so tiered prices stay current. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Price Lists is specific to Bigcommerce and Data Events to Intercom — each maps to any object or custom field on the other side. | |
| Shipments Order shipments with tracking numbers; created in BigCommerce from a 3PL or fulfillment system as packages ship. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Shipments is specific to Bigcommerce and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce and Intercom
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.
Bigcommerce Intercom Sub-second propagation
DetectionBigcommerce notifies Stacksync of record changes through webhook events. Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more).
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Bigcommerce 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 Bigcommerce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bigcommerce: OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Bigcommerce ⇄ Intercom
Connect Bigcommerce and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce or Intercom 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 Bigcommerce or Intercom record.
Observability
Monitoring
Track your Bigcommerce ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bigcommerce and Intercom.
How the Bigcommerce and Intercom connectors work
Bigcommerce
- Integration surface
- REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
- Authentication
- OAuth API account credentials — a store-generated client ID and permanent access token sent in the X-Auth-Token header, limited to the OAuth scopes granted when the account is created (e.g. store_v2_orders, store_v2_products)
- Change detection
- Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers
- Capabilities
- read · write · webhooks
- Rate limits
- OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
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
How it works
How to connect Bigcommerce to Intercom — 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 Bigcommerce and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bigcommerce
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce and Intercom 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 · Bigcommerce ⇄ IntercomCustomers 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.
Bigcommerce IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Intercom: authenticate both systems, choose the objects to sync (such as Bigcommerce's Customers and Categories), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Intercom side: Tags, Segments, Admins & Teams, Articles, plus custom fields where Intercom exposes them. On the Bigcommerce side: Brands, Inventory, Price Lists, Shipments. 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 Bigcommerce and Intercom: Where Bigcommerce records orders: purchase history on the account; New buyers become CRM records; Contact and address details stay consistent. Orders and their status from Bigcommerce 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.
-
Bigcommerce: REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs. Authentication: OAuth API account credentials — a store-generated client ID and permanent access token sent in the X-Auth-Token header, limited to the OAuth scopes granted when the account is created (e.g. store_v2_orders, store_v2_products). Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. 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. Bigcommerce: BigCommerce splits its API across V2 and V3 — Orders live largely in V2 while Catalog (Products, Variants, Categories) uses V3 — so a sync must map both surfaces. Stacksync's field mapping accounts for these differences between Bigcommerce and Intercom 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 Bigcommerce and Intercom.
Popular · 8 of 471
-
Bigcommerce ⇄ Gorgias -
Bigcommerce ⇄ Infor CRM -
Bigcommerce ⇄ Insightly -
Bigcommerce ⇄ Kommo -
Intercom ⇄ Akeneo -
Intercom ⇄ Channelengine -
Intercom ⇄ Easypost -
Intercom ⇄ Magento
No integrations match .
