Real-time
Two-way sync
Changes in Box or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Box to DuckDB integration — real-time, two-way sync
Keep Box and DuckDB 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 DuckDB
Keep DuckDB and Box in step: a row in DuckDB 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 DuckDB 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 External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas in DuckDB with Folders, Metadata, Collaborations, Users 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 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- 02 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
- 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
Common sync patterns
A queryable index of the file store
Every file or object in Box shows up as a row in DuckDB, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.
File metadata kept in step
Tags, custom properties, owner, or status columns edited on a row in DuckDB 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 DuckDB 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.
What you can sync between Box and DuckDB
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 | DuckDB objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | Tasks is specific to Box and Attached databases to DuckDB — 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. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Events is specific to Box and Database files to DuckDB — 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. | Schemas Namespaces within a database used to organize tables in sync outputs. | Files is specific to Box and Schemas to DuckDB — 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. | Tables Columnar tables created via SQL; the destination for materialized sync data. | Folders is specific to Box and Tables to DuckDB — 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. | Views SQL views used to shape or filter data for downstream consumers. | Metadata is specific to Box and Views to DuckDB — 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. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Collaborations is specific to Box and External files (Parquet/CSV/JSON) to DuckDB — each maps to any object or custom field on the other side. |
How changes propagate between Box and DuckDB
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 DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.
DuckDB Box Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
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.
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with Box ⇄ DuckDB
Connect Box and DuckDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–DuckDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or DuckDB 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 DuckDB record.
Observability
Monitoring
Track your Box ⇄ DuckDB 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 DuckDB.
How the Box and DuckDB 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.
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
How it works
How to connect Box to DuckDB — 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 DuckDB 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
DuckDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and DuckDB 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 ⇄ DuckDBCustomers 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 DuckDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and DuckDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and DuckDB: authenticate both systems, choose the objects to sync (such as Box's Tasks and Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Box: 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. On DuckDB: Polling or full re-reads; no change feed or transaction log API. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the DuckDB side: External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas, plus custom fields where DuckDB exposes them. On the Box side: Folders, Metadata, Collaborations, Users. 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 DuckDB: A queryable index of the file store; File metadata kept in step; Records that point at documents. Every file or object in Box shows up as a row in DuckDB, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.
-
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. DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Stacksync manages authentication, retries, and rate limits on both sides.
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 439 integrations available for Box and DuckDB.
Popular · 7 of 439
-
Box ⇄ VoltDB -
Box ⇄ YugabyteDB -
Box ⇄ Amazon DynamoDB -
Box ⇄ Reltio -
DuckDB ⇄ Sharepoint -
DuckDB ⇄ Egnyte - DuckDB ⇄ Amazon S3
No integrations match .
