Skip to content
Business productivity ⇄ Database

Ironclad to TiDB integration — real-time, two-way sync

Keep Ironclad and TiDB 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 Ironclad and TiDB

Mirror Ironclad's data into TiDB 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 TiDB.

Stacksync mirrors Records, Entities, Obligations, Webhooks from Ironclad into Views, Columns, Indexes, Sequences in TiDB 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 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.
  • 02 Pull executed contract PDFs from Records attachments into a document store or archive as each workflow completes.
  • 03 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • 04 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

Common sync patterns

Read Ironclad with a query

Records from Ironclad are ordinary rows in TiDB; 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 TiDB and Stacksync propagates the change into Ironclad, replacing custom integration code.

React to changes as they happen

Updates in Ironclad arrive as row changes in TiDB, so triggers, jobs, and services can respond in near real time.

What you can sync between Ironclad and TiDB

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.

Ironclad objects TiDB objects How this pairing syncs
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. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Entities is specific to Ironclad and Tables to TiDB — each maps to any object or custom field on the other side.
Obligations Post-signature commitments, milestones, and renewal dates tied to contracts; synced two-way to drive renewal, compliance, and finance reporting in downstream systems. Views Logical views for shaping reads before syncing outward. Obligations is specific to Ironclad and Views to TiDB — each maps to any object or custom field on the other side.
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. Columns MySQL-compatible types mapped to fields in the paired system. Webhooks is specific to Ironclad and Columns to TiDB — each maps to any object or custom field on the other side.
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. Indexes Secondary indexes that keep incremental sync queries efficient. Workflow Approvals is specific to Ironclad and Indexes to TiDB — each maps to any object or custom field on the other side.
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. Sequences Server-side ID generation relevant when external systems write rows. Signature Packets is specific to Ironclad and Sequences to TiDB — each maps to any object or custom field on the other side.
Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. Databases MySQL-style schemas addressed by any MySQL-compatible client. Workflow Documents is specific to Ironclad and Databases to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Ironclad and TiDB

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.

Ironclad TiDB 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 TiDB as a row-level write, with types converted between the two schemas.

TiDB Ironclad Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

DeliveryEach detected change is written to Ironclad through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • 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.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Ironclad ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Ironclad ⇄ TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Ironclad and TiDB.

How the Ironclad and TiDB connectors work

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.

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

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

    Choose tables

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

Ironclad and TiDB 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 434 integrations available for Ironclad and TiDB.

Popular · 6 of 434
All Ironclad integrations All TiDB 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