Real-time
Two-way sync
Changes in Box or Kommo instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Kommo integration — real-time, two-way sync
Keep Box and Kommo 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 Kommo
Keep the paperwork with the relationship: Kommo and Box share every customer's records and files in real time, in both directions.
Kommo 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 Users, Chats, Leads, Contacts in Kommo aligned with Events, Files, Folders, Metadata 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 Kommo; and records from Kommo 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 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
- 02 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
- 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
Common sync patterns
One place for a customer's files
Attachments that accumulate against a record in Kommo 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 Kommo, 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 Kommo, so the customer's paperwork sits with the relationship instead of a shared drive.
What you can sync between Box and Kommo
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 | Kommo 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 Account users map lead ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Tasks Follow-up records keep rep activity consistent across systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Leads The central pipeline record; external signups and form fills sync in as leads. | Events is specific to Box and Leads to Kommo — 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. | Contacts Person records sync with other CRMs and databases for a shared contact file. | Files is specific to Box and Contacts to Kommo — 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. | Companies Organization records map to accounts in ERPs and invoicing tools. | Folders is specific to Box and Companies to Kommo — 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. | Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Metadata is specific to Box and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Box and Kommo
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 Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Box Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update 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.
- Kommo: Subject to per-account request rate limits.
What ships with Box ⇄ Kommo
Connect Box and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Kommo 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 Kommo record.
Observability
Monitoring
Track your Box ⇄ Kommo 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 Kommo.
How the Box and Kommo 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.
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
How it works
How to connect Box to Kommo — 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 Kommo 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
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Kommo 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 ⇄ KommoCustomers 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 KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Kommo: authenticate both systems, choose the objects to sync (such as Box's Users and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Kommo side: Users, Chats, Leads, Contacts, plus custom fields where Kommo exposes them. On the Box side: Events, Files, Folders, Metadata. 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 Kommo: One place for a customer's files; A folder per account or deal; Documents linked back to the record. Attachments that accumulate against a record in Kommo 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.
-
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. Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: The API uses OAuth 2.0 with short-lived access tokens refreshed via refresh tokens, and supports webhooks on record lifecycle events. Box: Server-auth apps (JWT or CCG) act through a service account and only see content that account owns or is collaborated on, unless enterprise as-user or admin scopes are granted. Stacksync's field mapping accounts for these differences between Box and Kommo 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 509 integrations available for Box and Kommo.
Popular · 7 of 509
-
Box ⇄ Zoho SalesIQ -
Box ⇄ ZoomInfo -
Box ⇄ Vitally -
Box ⇄ DealCloud -
Kommo ⇄ Egnyte -
Kommo ⇄ Amazon S3 -
Kommo ⇄ Sharepoint
No integrations match .
