Real-time
Two-way sync
Changes in Ironclad or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Ironclad to Salesforce integration — real-time, two-way sync
Keep Ironclad and Salesforce 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 Salesforce
Sync what happens in Ironclad with the customer records in Salesforce, 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 Custom Objects, Accounts, Contacts, Leads in Salesforce with bi-directional, real-time sync. Activity and record changes in Ironclad update the matching contact or account in Salesforce, and CRM data flows the other way wherever Ironclad can store and use it.
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 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 04 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
Common sync patterns
Where Ironclad handles support or shared inboxes
Tickets and conversations attach to the right contact and account in Salesforce, so sales sees open issues before the next call.
Where Ironclad supplies contact or company data
Enriched fields land directly on records in Salesforce, and refreshes keep them from going stale.
Where Ironclad processes payments
Charges, refunds, and subscription changes appear on the account in Salesforce, so revenue context lives with the relationship.
What you can sync between Ironclad and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Workflows is specific to Ironclad and Contacts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Records is specific to Ironclad and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Entities is specific to Ironclad and Opportunities to Salesforce — 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. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Obligations is specific to Ironclad and Cases to Salesforce — 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. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Webhooks is specific to Ironclad and Campaigns to Salesforce — 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 and Events Activity records; usually read-only in syncs to feed activity reporting. | Workflow Approvals is specific to Ironclad and Tasks and Events to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Ironclad and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Ironclad Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Ironclad ⇄ Salesforce
Connect Ironclad and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ironclad–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ironclad or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Ironclad ⇄ Salesforce 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 Salesforce.
How the Ironclad and Salesforce 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.
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Ironclad to Salesforce — 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 Ironclad and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Ironclad
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ironclad and Salesforce 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 · Ironclad ⇄ SalesforceCustomers 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.
Ironclad SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ironclad and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ironclad and Salesforce: authenticate both systems, choose the objects to sync (such as Ironclad's Workflows and Records), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Ironclad and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Ironclad and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ironclad–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Ironclad and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Ironclad side: Workflow Approvals, Signature Packets, Workflow Documents, Workflows, plus custom fields where Ironclad exposes them. On the Salesforce side: Custom Objects, Accounts, Contacts, Leads. Stacksync auto-detects both schemas and converts types between the two systems.
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 542 integrations available for Ironclad and Salesforce.
Popular · 8 of 542
-
Ironclad ⇄ DealCloud -
Ironclad ⇄ Chorusai -
Ironclad ⇄ Clari -
Ironclad ⇄ Dun And Bradstreet -
Salesforce ⇄ Campfire -
Salesforce ⇄ Front -
Salesforce ⇄ Amazon Seller Central -
Salesforce ⇄ SendGrid
No integrations match .
