Real-time
Two-way sync
Changes in Box or Close instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Close integration — real-time, two-way sync
Keep Box and Close 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 Close
Keep the paperwork with the relationship: Close and Box share every customer's records and files in real time, in both directions.
Close 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 Custom Fields, Users, Smart Views, Leads in Close aligned with Metadata, Collaborations, Users, Groups 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 Close; and records from Close 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 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
- 02 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
- 03 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
- 04 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
Common sync patterns
One place for a customer's files
Attachments that accumulate against a record in Close 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 Close, 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 Close, so the customer's paperwork sits with the relationship instead of a shared drive.
What you can sync between Box and Close
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 | Close 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 Sales reps referenced as owners on leads, opportunities, and activities. | 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 items assigned to users; synced for workload and SLA reporting. | 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. | Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Metadata is specific to Box and Custom Activities to Close — 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 Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Collaborations is specific to Box and Custom Fields to Close — 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. | Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Groups is specific to Box and Smart Views to Close — 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. | Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Events is specific to Box and Leads to Close — each maps to any object or custom field on the other side. |
How changes propagate between Box and Close
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 Close 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 Close through its API, with automatic retries and rate-limit backoff.
Close Box Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
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.
- Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Box ⇄ Close
Connect Box and Close for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Close connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Close 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 Close record.
Observability
Monitoring
Track your Box ⇄ Close 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 Close.
How the Box and Close 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.
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
How it works
How to connect Box to Close — 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 Close 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
Close
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Close 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 ⇄ CloseCustomers 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 CloseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Close integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Close: 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.
-
Common patterns for Box and Close: 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 Close 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. Close: REST API. Authentication: API key (sent via HTTP Basic auth). Stacksync manages authentication, retries, and rate limits on both sides.
-
Close: Calling, SMS, and email are native activity types, so communication history is available through the same API as CRM records rather than a separate telephony integration. 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 Close 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 Close records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Close connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Close 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 520 integrations available for Box and Close.
Popular · 7 of 520
-
Box ⇄ Gladly -
Box ⇄ Gorgias -
Box ⇄ Infor CRM -
Box ⇄ Insightly -
Close ⇄ Egnyte -
Close ⇄ Amazon S3 -
Close ⇄ Sharepoint
No integrations match .
