Skip to content
Business productivity ⇄ CRM

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

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

Sync what happens in Ironclad with the customer records in Nutshell, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Ironclad holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Workflow Approvals, Signature Packets, Workflow Documents, Workflows in Ironclad to Tags, Users, Leads, People in Nutshell with bi-directional, real-time sync. Activity and record changes in Ironclad update the matching contact or account in Nutshell, and CRM data flows the other way wherever Ironclad can store and use it.

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 Sync Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
  • 04 Push closed-won leads to accounting software to trigger invoicing automatically.

Common sync patterns

Where Ironclad handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Nutshell, so sales sees open issues before the next call.

Where Ironclad supplies contact or company data

Enriched fields land directly on records in Nutshell, and refreshes keep them from going stale.

Where Ironclad processes payments

Charges, refunds, and subscription changes appear on the account in Nutshell, so revenue context lives with the relationship.

What you can sync between Ironclad and Nutshell

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 Nutshell objects How this pairing syncs
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. Activities Logged calls, meetings, and emails used for engagement reporting Webhooks is specific to Ironclad and Activities to Nutshell — 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. Tasks Rep to-dos mirrored into external work-management or reporting systems Workflow Approvals is specific to Ironclad and Tasks to Nutshell — 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. Notes Free-text history attached to leads and contacts, replicated for a full timeline Signature Packets is specific to Ironclad and Notes to Nutshell — 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. Products Line items attached to leads, used to sync sold products into billing Workflow Documents is specific to Ironclad and Products to Nutshell — each maps to any object or custom field on the other side.
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. Tags Segmentation labels mapped to lists or filters in downstream tools Workflows is specific to Ironclad and Tags to Nutshell — each maps to any object or custom field on the other side.
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. Users Rep records used to resolve ownership when syncing assignments Records is specific to Ironclad and Users to Nutshell — each maps to any object or custom field on the other side.

How changes propagate between Ironclad and Nutshell

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

Nutshell Ironclad Sub-second propagation

DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.

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.
  • Nutshell: Subject to the platform's API rate limits.
What ships with Ironclad ⇄ Nutshell

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Ironclad and Nutshell 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.

Nutshell

Integration surface
JSON-RPC API over HTTPS; a newer REST API is also offered
Authentication
HTTP Basic with account email and API key
Change detection
webhook subscriptions for record events, with polling as fallback
Capabilities
read · write · webhooks
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Ironclad and Nutshell 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 425 integrations available for Ironclad and Nutshell.

Popular · 8 of 425
All Ironclad integrations All Nutshell 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