Two-way sync
Changes in Box or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Box and Nutshell in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Nutshell 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 Tags, Users, Leads, People in Nutshell aligned with Groups, Tasks, Events, Files 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 Nutshell; and records from Nutshell 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.
When an account or deal is created in Nutshell, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Nutshell, so the customer's paperwork sits with the relationship instead of a shared drive.
Records from Nutshell 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.
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 | Nutshell 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 Rep records used to resolve ownership when syncing assignments | 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 Rep to-dos mirrored into external work-management or reporting systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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 Segmentation labels mapped to lists or filters in downstream tools | Collaborations is specific to Box and Tags to Nutshell — 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. | Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Groups is specific to Box and Leads to Nutshell — 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. | People Individual contacts, kept consistent with marketing and outreach tools | Events is specific to Box and People to Nutshell — 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. | Companies Account records that group people and leads for account-level syncs | Files is specific to Box and Companies to Nutshell — each maps to any object or custom field on the other side. |
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.
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 Nutshell through its API, with automatic retries and rate-limit backoff.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Nutshell connection.
Changes in Box or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Box or Nutshell data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Box or Nutshell record.
Track your Box ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Box and Nutshell.
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.
Authenticate Box and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Box and Nutshell 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Box and Nutshell: 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.
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. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
Nutshell: Nutshell's most full-featured API is JSON-RPC: each call names a method such as findLeads or editLead instead of hitting resource URLs, though a newer REST API is also available. Box: The user Events API is consumed with a stream_position and long-polling; enterprise/admin events retain roughly one year of history and can lag strict ordering for near-real-time reads. Stacksync's field mapping accounts for these differences between Box and Nutshell 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 Nutshell records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Nutshell connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Nutshell integration in-house.
Yes — Stacksync ships production-grade connectors for both Box and Nutshell. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 411 integrations available for Box and Nutshell.