Real-time
Two-way sync
Changes in Exasol or Ironclad instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Business productivity
Exasol to Ironclad integration — real-time, two-way sync
Keep Exasol 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 Exasol and Ironclad
Get the data locked inside Ironclad into Exasol as live tables, and send results back where Ironclad can use them, without writing a pipeline.
Whatever Ironclad is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Entities, Obligations, Webhooks, Workflow Approvals from Ironclad into tables in Exasol continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Exasol can also be written back into fields in Ironclad where the tool can use them.
Common use cases
- 01 Two-way sync Ironclad Records with a warehouse or ERP so executed-contract value, counterparty, renewal dates, and status stay current without manual re-keying.
- 02 Sync Entities (counterparties) two-way with a CRM or ERP so company and vendor master data matches across the CLM and the systems of record.
- 03 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
- 04 Keep dimension tables such as customers and products aligned with the systems of record.
Common sync patterns
Analytics on Ironclad's data
Records and events from Ironclad land in Exasol as queryable tables, current within seconds and ready to join with the rest of the warehouse.
Cross-tool reporting
Combine Ironclad's data with data from every other synced system to answer questions no single tool can.
Where Ironclad accepts updates: operational write-back
Segments, scores, or reference values computed in Exasol sync back onto records in Ironclad, putting analysis where the work happens.
What you can sync between Exasol 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.
| Exasol objects | Ironclad objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces that group the tables a sync reads from or writes into. | 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 Exasol and Workflow Documents to Ironclad — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard 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. | Tables is specific to Exasol and Workflows to Ironclad — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Records The Repository of executed and stored contracts with metadata (value, counterparty, key dates, type) and attachments; full create, read, update, and delete so signed-contract data and PDFs sync to a warehouse, ERP, or CRM. | Views is specific to Exasol and Records to Ironclad — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Entities Structured records for counterparties and other parties linked to workflows and records; read and written to keep company and vendor master data aligned with a CRM or ERP. | Virtual schemas is specific to Exasol and Entities to Ironclad — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Obligations Post-signature commitments, milestones, and renewal dates tied to contracts; synced two-way to drive renewal, compliance, and finance reporting in downstream systems. | UDF scripts is specific to Exasol and Obligations to Ironclad — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | 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. | Users and roles is specific to Exasol and Webhooks to Ironclad — each maps to any object or custom field on the other side. |
How changes propagate between Exasol 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.
Exasol Ironclad Interval-based propagation
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is written to Ironclad through its API, with automatic retries and rate-limit backoff.
Ironclad Exasol 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 Exasol as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session 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 Exasol ⇄ Ironclad
Connect Exasol and Ironclad for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Ironclad connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Exasol 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 Exasol or Ironclad record.
Observability
Monitoring
Track your Exasol ⇄ Ironclad sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Exasol and Ironclad.
How the Exasol and Ironclad connectors work
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session 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 Exasol 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.
- 01
Connect your apps
Authenticate Exasol 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.
Exasol
connected
Ironclad
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Exasol 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.
objects · Exasol ⇄ IroncladCustomers 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.
Exasol IroncladCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Exasol and Ironclad integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Ironclad: authenticate both systems, choose the objects to sync (such as Exasol's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Ironclad: Rate limits are per account per minute and differ by endpoint - for example GET Records is 600/min but POST/PATCH Workflows only 40/min - and exceeding one returns HTTP 429. Exasol: Exasol is an in-memory, columnar MPP database that creates and maintains indexes automatically based on query patterns, rather than requiring manual index design. Stacksync's field mapping accounts for these differences between Exasol and Ironclad without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Exasol and Ironclad records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Ironclad connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Ironclad integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Exasol and Ironclad. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. On Ironclad: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 437 integrations available for Exasol and Ironclad.
Popular · 5 of 437
-
Exasol ⇄ eClinicalWorks -
Ironclad ⇄ Tinybird -
Ironclad ⇄ Vertica -
Ironclad ⇄ Yellowbrick -
Ironclad ⇄ Snowflake
No integrations match .
