Skip to content
Database ⇄ Business productivity

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

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

Mirror Ironclad'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 Ironclad 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 Webhooks, Workflow Approvals, Signature Packets, Workflow Documents from Ironclad 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 Ironclad, so the tool and the database never disagree.

Common use cases

  • 01 Stream workflow approval and signature webhook events into an operational database for cycle-time, bottleneck, and SLA reporting across the contract lifecycle.
  • 02 Push Obligations and renewal dates from Ironclad into a finance or task system so post-signature commitments and renewals are tracked and actioned on time.
  • 03 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
  • 04 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools

Common sync patterns

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.

Read Ironclad with a query

Records from Ironclad are ordinary rows in InterSystems IRIS; join them, index them, and use them in application logic without touching the vendor API.

Automate Ironclad from your codebase

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

What you can sync between InterSystems IRIS and Ironclad

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 Ironclad objects How this pairing syncs
Namespaces Namespaces partition databases and determine the connection context for integrations. Obligations Post-signature commitments, milestones, and renewal dates tied to contracts; synced two-way to drive renewal, compliance, and finance reporting in downstream systems. Namespaces is specific to InterSystems IRIS and Obligations to Ironclad — 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. Webhooks Event subscriptions that push workflow, approval, signature, document, and comment changes to Stacksync in near real time; created, listed, and deleted through the API across 40+ event types. Stored Procedures is specific to InterSystems IRIS and Webhooks to Ironclad — 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. Workflow Approvals Per-workflow approval requests and their state; read to report approval status and cycle time, and status changes arrive live through the workflow_approval_status_changed event. Tables is specific to InterSystems IRIS and Workflow Approvals to Ironclad — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Signature Packets The e-signature packets on a workflow (sent, signatures collected, fully signed); read to track signing progress, with packet events delivered by webhook for real-time status. Views is specific to InterSystems IRIS and Signature Packets to Ironclad — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. Schemas is specific to InterSystems IRIS and Workflow Documents to Ironclad — 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. Workflows The core unit of Ironclad: a live contract process (NDA, MSA, order form) moving through creation, review, approval, and signature. Launched via POST, updated via PATCH, and read for status, so contract processes move two-way between Ironclad and a database, CRM, or ERP. Persistent Classes is specific to InterSystems IRIS and Workflows to Ironclad — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Ironclad

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

Ironclad InterSystems IRIS Sub-second propagation

DetectionIronclad notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /webhooks) fire on 40+ workflow, approval, signature, document, and comment events, and Ironclad retries a failing.

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.
  • Ironclad: Limits are enforced per account per minute by endpoint: GET Workflows 400 and POST/PATCH Workflows 40; GET Records 600 and POST/PATCH Records 200; GET Entities 600 and POST/PATCH Entities 200; Webhooks 600; all other endpoints 800. Exceeding a limit returns HTTP 429, and Ironclad recommends exponential backoff with jitter.
What ships with InterSystems IRIS ⇄ Ironclad

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Ironclad

Integration surface
REST/JSON Public API (CLM API) at https://na1.ironcladapp.com/public/api/v1 (NA1 and EU1 regions plus a demo/sandbox), with a native Webhooks subscription API; described by an OpenAPI 3.1 spec.
Authentication
OAuth 2.0 - Authorization Code grant (PKCE for public clients) and Client Credentials grant for server-to-server; access tokens are Bearer, expire after 6 hours, and every endpoint is gated by a resource scope. The legacy static API bearer token was deprecated on 2024-11-22.
Change detection
Native webhook subscriptions (POST /webhooks) fire on 40+ workflow, approval, signature, document, and comment events, and Ironclad retries a failing endpoint up to 10 times over about 13.6 hours with exponential backoff. Otherwise poll the list endpoints by last-updated. There is no database change-data-capture log.
Capabilities
read · write · webhooks
Rate limits
Limits are enforced per account per minute by endpoint: GET Workflows 400 and POST/PATCH Workflows 40; GET Records 600 and POST/PATCH Records 200; GET Entities 600 and POST/PATCH Entities 200; Webhooks 600; all other endpoints 800. Exceeding a limit returns HTTP 429, and Ironclad recommends exponential backoff with jitter.
How it works

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

    Choose tables

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

InterSystems IRIS and Ironclad 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 Ironclad.

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