Real-time
Two-way sync
Changes in Folk CRM or Ironclad instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Folk CRM to Ironclad integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Ironclad
Sync what happens in Ironclad with the customer records in Folk CRM, 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 Records, Entities, Obligations, Webhooks in Ironclad to Companies, Groups, Custom fields, Notes in Folk CRM with bi-directional, real-time sync. Activity and record changes in Ironclad update the matching contact or account in Folk CRM, 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 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 04 Keep folk and a billing or customer success tool aligned on company records as deals close.
Common sync patterns
Where Ironclad can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Folk CRM sync into Ironclad, so people working there have the context without switching tools.
Where Ironclad handles support or shared inboxes
Tickets and conversations attach to the right contact and account in Folk CRM, so sales sees open issues before the next call.
Where Ironclad supplies contact or company data
Enriched fields land directly on records in Folk CRM, and refreshes keep them from going stale.
What you can sync between Folk CRM 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.
| Folk CRM objects | Ironclad objects | How this pairing syncs | |
|---|---|---|---|
| Companies Organization records linked to people and kept aligned with billing or CS systems. | 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. | Companies is specific to Folk CRM and Webhooks to Ironclad — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | 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. | Groups is specific to Folk CRM and Workflow Approvals to Ironclad — each maps to any object or custom field on the other side. | |
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | 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. | Custom fields is specific to Folk CRM and Signature Packets to Ironclad — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. | Notes is specific to Folk CRM and Workflow Documents to Ironclad — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | 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. | Reminders is specific to Folk CRM and Workflows to Ironclad — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Records to Ironclad — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Ironclad Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Ironclad through its API, with automatic retries and rate-limit backoff.
Ironclad Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate 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 Folk CRM ⇄ Ironclad
Connect Folk CRM and Ironclad for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Ironclad connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Ironclad record.
Observability
Monitoring
Track your Folk CRM ⇄ Ironclad sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Ironclad.
How the Folk CRM and Ironclad connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate 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 Folk CRM 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 Folk CRM 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.
Folk CRM
connected
Ironclad
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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 · Folk CRM ⇄ 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.
Folk CRM IroncladCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Ironclad integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Ironclad: authenticate both systems, choose the objects to sync (such as Folk CRM's Companies and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Ironclad: Ironclad has a native webhooks API with 40+ event types and retries a failing endpoint up to 10 times over about 13.6 hours; there is no database change-data-capture log. Folk CRM: Folk's model centers on people and companies organized into shared groups rather than pipeline-first objects, so group membership carries much of the workflow state. Stacksync's field mapping accounts for these differences between Folk CRM 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 Folk CRM and Ironclad records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Folk CRM and Ironclad connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Folk CRM–Ironclad integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Ironclad. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. 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 421 integrations available for Folk CRM and Ironclad.
Popular · 5 of 421
No integrations match .
