Skip to content
Storage

Connect Box to any app with two-way sync.

Two-way sync Box across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Box.

These objects sync between Box and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Box exposes them.

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.
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.
Metadata
Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search.
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.
Users
Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source.
Groups
Named user collections used for bulk collaboration; membership synced from a directory or IdP.
Tasks
Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals.
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.
API surface

How Stacksync connects to Box.

The connector runs on Box's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Box

Connect Box for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Box instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box 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 record.

Observability

Monitoring

Track your Box sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Box connector.

Box is the cloud content-management system of record for regulated mid-market and enterprise organizations, owned by IT and content or records administrators. Contracts, design assets, financial documents, and collaboration files live there, governed by folder hierarchies, metadata templates, retention policies, and per-object collaborations. Because it holds the authoritative copy of unstructured content and its access grants, other systems push files in and read metadata and audit events out.

  • IT administrators
  • Box enterprise admins
  • Security and compliance teams
  • Records / content managers
  • Data engineering
  1. Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.

  2. Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.

  3. Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.

  4. Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.

  5. Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.

  6. Two-way sync Files and their Metadata instances between Box and Postgres so an internal app tracks document state in SQL while users keep working in Box, and status changes flow back onto the Box record.

All Box integrations

Pick the system you need to keep in sync with Box. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up Box in minutes, without APIs.

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.

  1. 01

    Connect your apps

    Authenticate Box with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Box connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Box
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Box database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

Box connector FAQ

What can I sync with the Box connector?

Box's core objects — Files, Folders, Metadata, Collaborations and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Box?

Via REST API (api.box.com/2.0), plus the Events API and V2 Webhooks, authenticated with 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. Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Box connector two-way?

Yes. Changes made in Box propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Box integration take to set up?

Most Box integrations go live in minutes: authenticate Box and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Box data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Box data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.