Real-time
Two-way sync
Changes in Egnyte or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Egnyte to InterSystems IRIS integration — real-time, two-way sync
Keep Egnyte 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 Egnyte and InterSystems IRIS
Keep InterSystems IRIS and Egnyte in step: a row in InterSystems IRIS for every file in Egnyte, 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 Egnyte 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 Tables, Views, Schemas, Persistent Classes in InterSystems IRIS with Events and Audit reports, Files, Folders, Users in Egnyte 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 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
- 03 Write custom Metadata such as classification tags and project fields onto Files and Folders from a governance or DMS system, and read it back for reporting.
- 04 Mirror folder Permissions from a directory or access-management system so entitlements stay consistent across teams.
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 Egnyte, and metadata changed in Egnyte 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 Egnyte, 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 Egnyte 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 Egnyte 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.
| Egnyte objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Groups is specific to Egnyte and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Permissions is specific to Egnyte and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Links is specific to Egnyte and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Metadata Custom metadata keys and project fields on files/folders via the Metadata API; written for classification and read back for reporting. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Metadata is specific to Egnyte and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Events and Audit reports File, login, permission, and sharing activity read via the Events API and Audit Reporting API; consumed read-only for compliance. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Events and Audit reports is specific to Egnyte and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. | Views SQL views expose curated slices of data for outbound replication. | Files is specific to Egnyte and Views to InterSystems IRIS — each maps to any object or custom field on the other side. |
How changes propagate between Egnyte 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.
Egnyte InterSystems IRIS Sub-second propagation
DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
InterSystems IRIS Egnyte 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 Egnyte through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Egnyte: Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request.
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Egnyte ⇄ InterSystems IRIS
Connect Egnyte and InterSystems IRIS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Egnyte–InterSystems IRIS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Egnyte 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 Egnyte or InterSystems IRIS record.
Observability
Monitoring
Track your Egnyte ⇄ 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 Egnyte and InterSystems IRIS.
How the Egnyte and InterSystems IRIS connectors work
Egnyte
- Integration surface
- REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints
- Authentication
- OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header
- Change detection
- Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events
- Capabilities
- read · write · webhooks
- Rate limits
- Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request
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 Egnyte 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 Egnyte 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.
Egnyte
connected
InterSystems IRIS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Egnyte 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 · Egnyte ⇄ 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.
Egnyte InterSystems IRISCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Egnyte and InterSystems IRIS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Egnyte and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Egnyte's Groups and Permissions), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the InterSystems IRIS side: Tables, Views, Schemas, Persistent Classes, plus custom fields where InterSystems IRIS exposes them. On the Egnyte side: Events and Audit reports, Files, Folders, 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 Egnyte and InterSystems IRIS: File metadata kept in step; Records that point at documents; A landing zone for incoming files. Tags, custom properties, owner, or status columns edited on a row in InterSystems IRIS write back to the matching file's metadata in Egnyte, and metadata changed in Egnyte updates the row, so the two never disagree about a file.
-
Egnyte: REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints. Authentication: OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header. InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
-
InterSystems IRIS: IRIS is multi-model: the same stored data can be accessed as relational tables via SQL, as persistent objects, and as multidimensional globals, so integrations usually standardize on the SQL projection. Egnyte: Effective folder permissions combine group and individual grants; the Permissions API can return the computed effective permission for a user on a folder. Stacksync's field mapping accounts for these differences between Egnyte and InterSystems IRIS without custom code.
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 Egnyte and InterSystems IRIS.
Popular · 7 of 458
-
Egnyte ⇄ PostgreSQL -
Egnyte ⇄ Amazon RDS -
Egnyte ⇄ Supabase -
Egnyte ⇄ MySQL -
InterSystems IRIS ⇄ Box -
InterSystems IRIS ⇄ Sharepoint -
InterSystems IRIS ⇄ Amazon S3
No integrations match .
