Real-time
Two-way sync
Changes in Box or ClickHouse instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Data warehouse
Box to ClickHouse integration — real-time, two-way sync
Keep Box and ClickHouse 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 ClickHouse
Bridge query-ready tables and stored files: ClickHouse and Box keep the same records in step, in real time, in both directions.
ClickHouse keeps the tables and query results a business reports on; Box keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Box that has to become rows in ClickHouse, or a result in ClickHouse that people downstream need back as a file in Box. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.
Stacksync syncs Materialized views, Distributed tables, Dictionaries, Tables (MergeTree family) in ClickHouse with Files, Folders, Metadata, Collaborations in Box field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
- 02 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
- 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
One dataset, kept consistent both ways
Where the same dataset lives as a file in Box and a table in ClickHouse, a change on either side propagates to the other, ending the drift between the file people read and the table people query.
Where Box holds the file inventory: make it queryable
The catalog of documents, owners, and folders in Box appears as Materialized views, Distributed tables, Dictionaries, Tables (MergeTree family) in ClickHouse, so file metadata can be joined against the rest of your data and reported on.
Where ClickHouse computes the labels: push them onto the files
Classifications, scores, or status derived in ClickHouse are written back onto the matching Files, Folders, Metadata, Collaborations in Box as metadata or tags, so the file store reflects what analytics decided.
What you can sync between Box and ClickHouse
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 | ClickHouse 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. | Databases Namespaces that group tables and scope permissions for sync users. | Metadata is specific to Box and Databases to ClickHouse — 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. | Views Saved queries used as curated, read-only sync sources. | Collaborations is specific to Box and Views to ClickHouse — 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. | Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Users is specific to Box and Materialized views to ClickHouse — 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. | Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Groups is specific to Box and Distributed tables to ClickHouse — 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. | Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Tasks is specific to Box and Dictionaries to ClickHouse — 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. | Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Events is specific to Box and Tables (MergeTree family) to ClickHouse — each maps to any object or custom field on the other side. |
How changes propagate between Box and ClickHouse
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 ClickHouse 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 ClickHouse as a row-level write, with types converted between the two schemas.
ClickHouse Box Interval-based propagation
DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.
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 ⇄ ClickHouse
Connect Box and ClickHouse for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–ClickHouse connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or ClickHouse 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 ClickHouse record.
Observability
Monitoring
Track your Box ⇄ ClickHouse 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 ClickHouse.
How the Box and ClickHouse 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.
ClickHouse
- Integration surface
- Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
- Authentication
- Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
- Change detection
- No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
- Capabilities
- read · write
How it works
How to connect Box to ClickHouse — 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 ClickHouse 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
ClickHouse
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and ClickHouse 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 ⇄ ClickHouseCustomers 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 ClickHouseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and ClickHouse integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and ClickHouse: 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.
-
ClickHouse: Updates and deletes are asynchronous mutations that rewrite data parts, so syncs into ClickHouse favor append-and-deduplicate patterns (for example ReplacingMergeTree) over row-level upserts. Box: Server-auth apps (JWT or CCG) act through a service account and only see content that account owns or is collaborated on, unless enterprise as-user or admin scopes are granted. Stacksync's field mapping accounts for these differences between Box and ClickHouse 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 ClickHouse records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and ClickHouse connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–ClickHouse integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and ClickHouse. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 ClickHouse: No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 ClickHouse.
Popular · 7 of 531
-
Box ⇄ Starburst Enterprise -
Box ⇄ StarRocks -
Box ⇄ Teradata Vantage -
Box ⇄ Tinybird -
ClickHouse ⇄ Egnyte -
ClickHouse ⇄ Amazon S3 -
ClickHouse ⇄ Sharepoint
No integrations match .
