Real-time
Two-way sync
Changes in Box or Intercom instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Intercom integration — real-time, two-way sync
Keep Box 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 Box and Intercom
Keep the paperwork with the relationship: Intercom and Box share every customer's records and files in real time, in both directions.
Intercom holds the customer relationship as structured records; Box holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.
Stacksync keeps Conversations, Tickets, Data Events, Custom Data Attributes in Intercom aligned with Collaborations, Users, Groups, Tasks in Box, in real time. A new account or deal can open its own folder in Box; a document filed in Box can surface as a link and metadata on the matching record in Intercom; and records from Intercom can be written into Box as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.
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 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
- 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
Common sync patterns
A folder per account or deal
When an account or deal is created in Intercom, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
Documents linked back to the record
A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Intercom, so the customer's paperwork sits with the relationship instead of a shared drive.
CRM records archived into storage
Records from Intercom are written into Box as files or objects on the schedule you set, giving you a durable copy for backup, retention, and compliance without an export to run by hand.
What you can sync between Box 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.
| Box objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Tasks is specific to Box and Companies to Intercom — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Conversations Support and sales threads sync outward for analytics and CRM context. | Events is specific to Box and Conversations to Intercom — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Tickets Structured ticket records track issues alongside conversational threads. | Files is specific to Box and Tickets to Intercom — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Folders is specific to Box and Data Events to Intercom — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Metadata is specific to Box and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Collaborations is specific to Box and Tags to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Box 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.
Box Intercom Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Box 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 Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Box ⇄ Intercom
Connect Box and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box 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 Box or Intercom record.
Observability
Monitoring
Track your Box ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Intercom.
How the Box and Intercom connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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 Box 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 Box 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.
Box
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box 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 · Box ⇄ 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.
Box IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Intercom: authenticate both systems, choose the objects to sync (such as Box's Tasks and Events), 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 Box and Intercom: A folder per account or deal; Documents linked back to the record; CRM records archived into storage. When an account or deal is created in Intercom, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
-
Box: REST API (api.box.com/2.0), plus the Events API and V2 Webhooks. Authentication: OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing. 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: API behavior is pinned per app using a version header, so integrations control when they adopt breaking changes. Box: Webhooks are capped per application and per file/folder target, must be verified with Box's signature keys, and their payloads carry the object reference rather than the full changed content. Stacksync's field mapping accounts for these differences between Box and Intercom 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 Box and Intercom 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 504 integrations available for Box and Intercom.
Popular · 7 of 504
-
Box ⇄ Microsoft Dynamics 365 Sales -
Box ⇄ Attio -
Box ⇄ Pipedrive -
Box ⇄ Zoho CRM -
Intercom ⇄ Amazon S3 -
Intercom ⇄ Sharepoint -
Intercom ⇄ Egnyte
No integrations match .
