Skip to content
Database ⇄ CRM

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

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

Treat Seismic like part of your database: its records live in InterSystems IRIS as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in InterSystems IRIS, where it can be queried and joined like everything else.

Stacksync mirrors LiveSend Links, Digital Sales Rooms, Reporting Activities, Library Content from Seismic into Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Seismic with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Sync Library Content metadata and Custom Property Schemas with a DAM or PIM so one taxonomy governs assets across systems.
  • 02 React to ContentManager and DSR webhook events to update a database when documents are published, versioned, or expired.
  • 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

Trigger workflows from CRM changes

Field and stage updates in Seismic arrive as row changes in InterSystems IRIS, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Seismic become tables in InterSystems IRIS you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to InterSystems IRIS sync onto the matching records in Seismic, giving go-to-market teams live product context.

What you can sync between InterSystems IRIS and Seismic

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 Seismic objects How this pairing syncs
Schemas Schema organization scopes which tables a sync connection can see. Reporting Activities Content-interaction, engagement, and usage analytics extracted read-only through the ETL-oriented Reporting API v2 for a warehouse. Schemas is specific to InterSystems IRIS and Reporting Activities to Seismic — 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. Library Content Documents, decks, and assets stored in teamsites; created, moved, and retrieved via the Content Management API, each with a contentId. Persistent Classes is specific to InterSystems IRIS and Library Content to Seismic — 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. Content Versions Version history for a library item; new versions upload via API and old ones expire, with events firing on ContentManager webhooks. Globals is specific to InterSystems IRIS and Content Versions to Seismic — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Users User records managed through SCIM 2.0 and legacy user endpoints; created, updated, and deactivated for provisioning sync. Namespaces is specific to InterSystems IRIS and Users to Seismic — 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. User Groups Group definitions and membership that govern content access; synced from an IdP or HRIS to keep permissions current. Stored Procedures is specific to InterSystems IRIS and User Groups to Seismic — 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. Teamsites Tenant-scoped workspace partitions organizing Library content, permissions, and config; scoped by teamSiteId on most content calls. Tables is specific to InterSystems IRIS and Teamsites to Seismic — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Seismic

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

Seismic InterSystems IRIS Sub-second propagation

DetectionSeismic notifies Stacksync of record changes through webhook events. Webhooks for content, version, user, group, workflow, DSR, and LiveSend events.

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.
  • Seismic: Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers.
What ships with InterSystems IRIS ⇄ Seismic

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Seismic

Integration surface
REST Integration APIs and Reporting API v2
Authentication
OAuth 2.0 / OpenID Connect; Bearer token in the Authorization header, via Authorization Code (user context) or client-credentials app-only flows
Change detection
Webhooks for content, version, user, group, workflow, DSR, and LiveSend events; the Reporting API v2 is polled for batch historical extracts (ETL-oriented, not high-frequency)
Capabilities
read · write · webhooks
Rate limits
Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers
Seismic setup guide
How it works

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

    Choose tables

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

InterSystems IRIS and Seismic 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 490 integrations available for InterSystems IRIS and Seismic.

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