Skip to content
Storage ⇄ Data warehouse

Box to Starburst Enterprise integration — real-time, two-way sync

Keep Box and Starburst Enterprise 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 Starburst Enterprise

Bridge query-ready tables and stored files: Starburst Enterprise and Box keep the same records in step, in real time, in both directions.

Starburst Enterprise 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 Starburst Enterprise, or a result in Starburst Enterprise 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 Columns, Catalogs, Schemas, Tables in Starburst Enterprise with Metadata, Collaborations, Users, Groups 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 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 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

Where Box is the shared drive: publish results back as files

Curated tables and query results from Starburst Enterprise are written to Box as files the rest of the business can open, keeping the shared copy current without a hand-run export.

One dataset, kept consistent both ways

Where the same dataset lives as a file in Box and a table in Starburst Enterprise, 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 Columns, Catalogs, Schemas, Tables in Starburst Enterprise, so file metadata can be joined against the rest of your data and reported on.

What you can sync between Box and Starburst Enterprise

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 Starburst Enterprise 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Metadata is specific to Box and Schemas to Starburst Enterprise — 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. Tables Queryable relations; writes pass through to sources whose connectors support them. Collaborations is specific to Box and Tables to Starburst Enterprise — 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. Views Engine-level SQL views used to shape federated data before syncing it out. Users is specific to Box and Views to Starburst Enterprise — 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. Materialized views Precomputed results that make repeated sync reads cheaper. Groups is specific to Box and Materialized views to Starburst Enterprise — 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. Columns Typed per the Trino type system, mapped from each source's native types. Tasks is specific to Box and Columns to Starburst Enterprise — 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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Events is specific to Box and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Box and Starburst Enterprise

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 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Box Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Box ⇄ Starburst Enterprise

Connect Box and Starburst Enterprise for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Box or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Box ⇄ Starburst Enterprise 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 Starburst Enterprise.

How the Box and Starburst Enterprise 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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Box to Starburst Enterprise — 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.

  1. 01

    Connect your apps

    Authenticate Box and Starburst Enterprise with each platform's 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
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box and Starburst Enterprise 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Box ⇄ Starburst Enterprise
    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 Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Box and Starburst Enterprise integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 427 integrations available for Box and Starburst Enterprise.

Popular · 7 of 427
All Box integrations All Starburst Enterprise integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own