Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in Ironclad with the customer records in Intercom, 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 Documents, Workflows, Records, Entities in Ironclad to Articles, Contacts, Companies, Conversations in Intercom with bi-directional, real-time sync. Activity and record changes in Ironclad update the matching contact or account in Intercom, and CRM data flows the other way wherever Ironclad can store and use it.

Common use cases

  • 01 Pull executed contract PDFs from Records attachments into a document store or archive as each workflow completes.
  • 02 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.
  • 03 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
  • 04 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history

Common sync patterns

Where Ironclad supplies contact or company data

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

Where Ironclad processes payments

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

Where Ironclad can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Intercom sync into Ironclad, so people working there have the context without switching tools.

What you can sync between Intercom 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.

Intercom objects Ironclad objects How this pairing syncs
Data Events Behavioral events pushed in from product databases trigger messages and flows. 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. Data Events is specific to Intercom and Entities to Ironclad — each maps to any object or custom field on the other side.
Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. Obligations Post-signature commitments, milestones, and renewal dates tied to contracts; synced two-way to drive renewal, compliance, and finance reporting in downstream systems. Custom Data Attributes is specific to Intercom and Obligations to Ironclad — each maps to any object or custom field on the other side.
Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. 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. Tags is specific to Intercom and Webhooks to Ironclad — each maps to any object or custom field on the other side.
Segments Saved audience definitions are readable for targeting parity across tools. 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. Segments is specific to Intercom and Workflow Approvals to Ironclad — each maps to any object or custom field on the other side.
Admins & Teams Teammate records map conversation ownership to CRM users. 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. Admins & Teams is specific to Intercom and Signature Packets to Ironclad — each maps to any object or custom field on the other side.
Articles Help center content is accessible via API for knowledge sync and audits. Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. Articles is specific to Intercom and Workflow Documents to Ironclad — each maps to any object or custom field on the other side.

How changes propagate between Intercom 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.

Intercom Ironclad Sub-second propagation

DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.

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

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

Rate-limit considerations

  • Intercom: Subject to per-app rate limits on the Intercom API.
  • 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 Intercom ⇄ Ironclad

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Intercom and Ironclad connectors work

Intercom

Integration surface
REST API
Authentication
OAuth 2.0 for public apps or a workspace access token
Change detection
Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-app rate limits on the Intercom API

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 Intercom 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 Intercom 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
    Intercom connected
    Ironclad connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Intercom 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 518 integrations available for Intercom and Ironclad.

Popular · 7 of 518
All Intercom 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