Real-time
Two-way sync
Changes in InterSystems IRIS or Workday instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
InterSystems IRIS to Workday integration — real-time, two-way sync
Keep InterSystems IRIS and Workday 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 InterSystems IRIS and Workday
Work with Workday's financial data straight from InterSystems IRIS: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Customers and Invoices, Journal Entries, Custom Reports (RaaS), Workers from Workday into Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against InterSystems IRIS, and rows your code writes or updates flow back into Workday with validation, so the finance system stays the system of record.
Common use cases
- 01 Import journal entries from external billing or expense systems into Workday Financials.
- 02 Keep supervisory-organization hierarchies aligned with planning and workforce tools that model the same structure.
- 03 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 04 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
Common sync patterns
Internal tools without API plumbing
Build dashboards and back-office tools directly on InterSystems IRIS; Stacksync handles the API calls, rate limits, and retries against Workday.
Write back safely
Updates written to the synced tables in InterSystems IRIS propagate into Workday, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Workday appear in InterSystems IRIS as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between InterSystems IRIS and Workday
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.
| InterSystems IRIS objects | Workday objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Schema organization scopes which tables a sync connection can see. | Workers The central HCM record covering employment, job, and personal data; the anchor of most syncs. | Schemas is specific to InterSystems IRIS and Workers to Workday — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Organizations Supervisory and company hierarchies read to drive routing and reporting in other systems. | Persistent Classes is specific to InterSystems IRIS and Organizations to Workday — each maps to any object or custom field on the other side. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Positions Job seats synced with recruiting and planning tools. | Globals is specific to InterSystems IRIS and Positions to Workday — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Compensation Pay components read into payroll, planning, and equity systems under strict access control. | Namespaces is specific to InterSystems IRIS and Compensation to Workday — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Time Off and Absence Balances and requests synced with scheduling and workforce tools. | Stored Procedures is specific to InterSystems IRIS and Time Off and Absence to Workday — each maps to any object or custom field on the other side. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Payroll Results Completed pay data exported to finance and benefits systems. | Tables is specific to InterSystems IRIS and Payroll Results to Workday — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS and Workday
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.
InterSystems IRIS Workday 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 Workday through its API, with automatic retries and rate-limit backoff.
Workday InterSystems IRIS Interval-based propagation
DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with InterSystems IRIS ⇄ Workday
Connect InterSystems IRIS and Workday for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Workday connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS or Workday 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 InterSystems IRIS or Workday record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ Workday sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Workday.
How the InterSystems IRIS and Workday connectors work
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
Workday
- Integration surface
- SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
- Authentication
- OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
- Change detection
- Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
- Capabilities
- read · write
How it works
How to connect InterSystems IRIS to Workday — 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 InterSystems IRIS and Workday with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
InterSystems IRIS
connected
Workday
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS and Workday 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 · InterSystems IRIS ⇄ WorkdayCustomers 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.
InterSystems IRIS WorkdayCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and Workday integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and Workday: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Schemas and Persistent Classes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed InterSystems IRIS and Workday connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–Workday integration in-house.
-
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Workday. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On Workday: Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Workday side: Customers and Invoices, Journal Entries, Custom Reports (RaaS), Workers, plus custom fields where Workday exposes them. On the InterSystems IRIS side: Persistent Classes, Globals, Namespaces, Stored Procedures. 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.
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 456 integrations available for InterSystems IRIS and Workday.
Popular · 6 of 456
-
InterSystems IRIS ⇄ Anaplan -
InterSystems IRIS ⇄ Chargebee -
Workday ⇄ Dynamo DB -
Workday ⇄ IBM Db2 -
Workday ⇄ Firebase -
Workday ⇄ SingleStore
No integrations match .
