Real-time
Two-way sync
Changes in Box or MongoDB instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Box to MongoDB integration — real-time, two-way sync
Keep Box and MongoDB 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 MongoDB
Keep MongoDB and Box in step: a row in MongoDB for every file in Box, with names, paths, metadata, and status staying consistent in real time, in both directions.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in MongoDB says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Collections, Documents, Embedded documents and arrays, Indexes in MongoDB with Files, Folders, Metadata, Collaborations in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Common use cases
- 01 Keep a MongoDB-backed product catalog aligned with an ERP's item master in both directions.
- 02 Consolidate documents from multiple clusters or tenants into a single warehouse-facing store.
- 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
File metadata kept in step
Tags, custom properties, owner, or status columns edited on a row in MongoDB write back to the matching file's metadata in Box, and metadata changed in Box updates the row, so the two never disagree about a file.
Records that point at documents
Where a record in MongoDB references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
A landing zone for incoming files
Files that arrive in a folder or bucket in Box become rows in MongoDB as they land, so a database-driven process can pick them up without polling the storage system's API.
What you can sync between Box and MongoDB
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 | MongoDB objects | How this pairing syncs | |
|---|---|---|---|
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Views Read-only aggregation-defined sources for filtered sync datasets. | Metadata is specific to Box and Views to MongoDB — 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. | Change streams The oplog-backed event feed that powers real-time change capture. | Collaborations is specific to Box and Change streams to MongoDB — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | GridFS files Chunked file storage whose metadata can be referenced by synced documents. | Users is specific to Box and GridFS files to MongoDB — 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. | Databases Logical groupings of collections that scope a sync connection. | Groups is specific to Box and Databases to MongoDB — 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. | Collections The table-like sync unit; each collection maps to a table or object in the paired system. | Tasks is specific to Box and Collections to MongoDB — 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. | Documents BSON records created, updated, and deleted during syncs, keyed by _id. | Events is specific to Box and Documents to MongoDB — each maps to any object or custom field on the other side. |
How changes propagate between Box and MongoDB
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 MongoDB 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 applied to MongoDB as a row-level write, with types converted between the two schemas.
MongoDB Box Sub-second propagation
DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).
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.
What ships with Box ⇄ MongoDB
Connect Box and MongoDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–MongoDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or MongoDB 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 MongoDB record.
Observability
Monitoring
Track your Box ⇄ MongoDB 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 MongoDB.
How the Box and MongoDB 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.
MongoDB
- Integration surface
- MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
- Authentication
- Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
- Change detection
- MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time
- Capabilities
- read · write · CDC
How it works
How to connect Box to MongoDB — 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 MongoDB 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
MongoDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and MongoDB 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 ⇄ MongoDBCustomers 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 MongoDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and MongoDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and MongoDB: authenticate both systems, choose the objects to sync (such as Box's Metadata and Collaborations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Box and MongoDB: File metadata kept in step; Records that point at documents; A landing zone for incoming files. Tags, custom properties, owner, or status columns edited on a row in MongoDB write back to the matching file's metadata in Box, and metadata changed in Box updates the row, so the two never disagree about a file.
-
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. MongoDB: MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management. Authentication: Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required. Stacksync manages authentication, retries, and rate limits on both sides.
-
MongoDB: Change streams expose ordered change events with resume tokens, so an interrupted sync can pick up exactly where it stopped without a full re-read. 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 MongoDB 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 MongoDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and MongoDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–MongoDB integration in-house.
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 531 integrations available for Box and MongoDB.
Popular · 7 of 531
-
Box ⇄ Elasticsearch -
Box ⇄ Google Cloud Spanner - Box ⇄ Google Cloud SQL
-
Box ⇄ IBM AS/400 -
MongoDB ⇄ Amazon S3 -
MongoDB ⇄ Sharepoint -
MongoDB ⇄ Egnyte
No integrations match .
