Real-time
Two-way sync
Changes in Box or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Box to InterSystems IRIS integration — real-time, two-way sync
Keep Box and InterSystems IRIS 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 InterSystems IRIS
Keep InterSystems IRIS and Box in step: a row in InterSystems IRIS 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 InterSystems IRIS 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 Stored Procedures, Tables, Views, Schemas in InterSystems IRIS with Collaborations, Users, Groups, Tasks 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 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
- 02 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
- 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
File metadata kept in step
Tags, custom properties, owner, or status columns edited on a row in InterSystems IRIS 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 InterSystems IRIS 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.
A landing zone for incoming files
Files that arrive in a folder or bucket in Box become rows in InterSystems IRIS as they land, so a database-driven process can pick them up without polling the storage system's API.
What you can sync between Box and InterSystems IRIS
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 | InterSystems IRIS 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. | Schemas Schema organization scopes which tables a sync connection can see. | Tasks is specific to Box and Schemas to InterSystems IRIS — 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. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Events is specific to Box and Persistent Classes to InterSystems IRIS — 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. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Files is specific to Box and Globals to InterSystems IRIS — 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. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Folders is specific to Box and Namespaces to InterSystems IRIS — 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. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Metadata is specific to Box and Stored Procedures to InterSystems IRIS — 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 Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Collaborations is specific to Box and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. |
How changes propagate between Box and InterSystems IRIS
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 InterSystems IRIS 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 InterSystems IRIS as a row-level write, with types converted between the two schemas.
InterSystems IRIS Box Interval-based propagation
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
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.
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Box ⇄ InterSystems IRIS
Connect Box and InterSystems IRIS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–InterSystems IRIS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or InterSystems IRIS 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 InterSystems IRIS record.
Observability
Monitoring
Track your Box ⇄ InterSystems IRIS 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 InterSystems IRIS.
How the Box and InterSystems IRIS 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.
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published API rate limits
How it works
How to connect Box to InterSystems IRIS — 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 InterSystems IRIS 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
InterSystems IRIS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and InterSystems IRIS 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 ⇄ InterSystems IRISCustomers 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 InterSystems IRISCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and InterSystems IRIS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and InterSystems IRIS: 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.
-
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 InterSystems IRIS records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–InterSystems IRIS integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and InterSystems IRIS. 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 InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the InterSystems IRIS side: Stored Procedures, Tables, Views, Schemas, plus custom fields where InterSystems IRIS exposes them. On the Box side: Collaborations, Users, Groups, Tasks. Stacksync auto-detects both schemas and converts types between the two systems.
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 458 integrations available for Box and InterSystems IRIS.
Popular · 7 of 458
-
Box ⇄ Postgres Heroku -
Box ⇄ Airtable -
Box ⇄ AWS Aurora MySQL - Box ⇄ AWS Aurora PostgreSQL
-
InterSystems IRIS ⇄ Sharepoint -
InterSystems IRIS ⇄ Egnyte -
InterSystems IRIS ⇄ Amazon S3
No integrations match .
