Skip to content
Database ⇄ Business productivity

InterSystems IRIS to Sysaid integration — real-time, two-way sync

Keep InterSystems IRIS and Sysaid 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 Sysaid

Mirror Sysaid's data into InterSystems IRIS so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Sysaid through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in InterSystems IRIS.

Stacksync mirrors Problems, Changes, Users, Assets from Sysaid into Schemas, Persistent Classes, Globals, Namespaces in InterSystems IRIS and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Sysaid, so the tool and the database never disagree.

Common use cases

  • 01 Stream Service Records into a warehouse for SLA, backlog, and MTTR reporting without manual CSV exports.
  • 02 Two-way sync Incidents and Service Requests with a Postgres database so on-call and internal apps read and update tickets in SQL while agents keep working in SysAid.
  • 03 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
  • 04 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing

Common sync patterns

Automate Sysaid from your codebase

Write to the synced tables in InterSystems IRIS and Stacksync propagates the change into Sysaid, replacing custom integration code.

React to changes as they happen

Updates in Sysaid arrive as row changes in InterSystems IRIS, so triggers, jobs, and services can respond in near real time.

One integration pattern for the whole stack

Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.

What you can sync between InterSystems IRIS and Sysaid

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 Sysaid objects How this pairing syncs
Namespaces Namespaces partition databases and determine the connection context for integrations. Incidents Break/fix tickets under /api/v1/sr with type=incident; created and updated two-way with status, priority, assignee, category, and SLA fields. Namespaces is specific to InterSystems IRIS and Incidents to Sysaid — 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. Service Requests Catalog and help-desk requests on the same /sr endpoint (type=request); written or read so fulfillment can be driven from another system. Stored Procedures is specific to InterSystems IRIS and Service Requests to Sysaid — 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. Problems Root-cause records that group related incidents; read and written to keep problem management aligned with an external ITSM or reporting store. Tables is specific to InterSystems IRIS and Problems to Sysaid — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. Views is specific to InterSystems IRIS and Changes to Sysaid — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. Schemas is specific to InterSystems IRIS and Users to Sysaid — 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. Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. Persistent Classes is specific to InterSystems IRIS and Assets to Sysaid — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Sysaid

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 Sysaid 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 Sysaid through its API, with automatic retries and rate-limit backoff.

Sysaid InterSystems IRIS Sub-second propagation

DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.

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.
  • Sysaid: Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.
What ships with InterSystems IRIS ⇄ Sysaid

Connect InterSystems IRIS and Sysaid for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Sysaid connection.

Real-time

Two-way sync

Changes in InterSystems IRIS or Sysaid instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Sysaid 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 Sysaid record.

Observability

Monitoring

Track your InterSystems IRIS ⇄ Sysaid 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 Sysaid.

How the InterSystems IRIS and Sysaid 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

Sysaid

Integration surface
REST API (JSON)
Authentication
Client-credentials app keys: an application key (clientId/clientSecret) is created via /v1/application-keys, then exchanged at /v1/access-tokens for a bearer token (default 24h, up to 30 days); an x-sysaid-accountid header scopes the account. Legacy V0 uses session-cookie login.
Change detection
Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature; otherwise poll the /sr endpoint filtering on update_time.gte.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.
How it works

How to connect InterSystems IRIS to Sysaid — 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 InterSystems IRIS and Sysaid 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
    InterSystems IRIS connected
    Sysaid connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS and Sysaid 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 · InterSystems IRIS ⇄ Sysaid
    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
    InterSystems IRIS Sysaid
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS and Sysaid 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
CSA STAR
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 472 integrations available for InterSystems IRIS and Sysaid.

Popular · 8 of 472
All InterSystems IRIS integrations All Sysaid 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