Real-time
Two-way sync
Changes in Box or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Kustomer integration — real-time, two-way sync
Keep Box and Kustomer 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 Kustomer
Keep the paperwork with the relationship: Kustomer and Box share every customer's records and files in real time, in both directions.
Kustomer 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, Messages, Companies, Custom Objects (Klasses) in Kustomer aligned with Tasks, Events, Files, Folders 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 Kustomer; and records from Kustomer 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 order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 02 Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance 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
Document status on the record
Metadata kept in Box, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in Kustomer, so people working the account see where the paperwork stands without opening storage.
One place for a customer's files
Attachments that accumulate against a record in Kustomer collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.
A folder per account or deal
When an account or deal is created in Kustomer, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
What you can sync between Box and Kustomer
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 | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Users Agent records map conversation ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Companies Organization records group customers and map to CRM accounts. | Metadata is specific to Box and Companies to Kustomer — 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. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Collaborations is specific to Box and Custom Objects (Klasses) to Kustomer — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Teams Team assignments support routing parity and reporting. | Groups is specific to Box and Teams to Kustomer — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Tags Labels on conversations and customers sync for categorization and analytics. | Tasks is specific to Box and Tags to Kustomer — 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. | Notes Internal annotations carry context alongside synced conversations. | Events is specific to Box and Notes to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Box and Kustomer
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 Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Box Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record 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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Box ⇄ Kustomer
Connect Box and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Box ⇄ Kustomer 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 Kustomer.
How the Box and Kustomer 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.
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Box to Kustomer — 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 Kustomer 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
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Kustomer 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 ⇄ KustomerCustomers 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 KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Kustomer: authenticate both systems, choose the objects to sync (such as Box's Users and Metadata), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Box and Kustomer. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: 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. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kustomer side: Conversations, Messages, Companies, Custom Objects (Klasses), plus custom fields where Kustomer exposes them. On the Box side: Tasks, Events, Files, Folders. 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 Box and Kustomer: Document status on the record; One place for a customer's files; A folder per account or deal. Metadata kept in Box, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in Kustomer, so people working the account see where the paperwork stands without opening storage.
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 409 integrations available for Box and Kustomer.
Popular · 7 of 409
-
Box ⇄ Microsoft Dynamics 365 Sales -
Box ⇄ Attio -
Box ⇄ Pipedrive -
Box ⇄ Zoho CRM -
Kustomer ⇄ Amazon S3 -
Kustomer ⇄ Sharepoint -
Kustomer ⇄ Egnyte
No integrations match .
