Real-time
Two-way sync
Changes in Hibob or Ironclad instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Hibob to Ironclad integration — real-time, two-way sync
Keep Hibob 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 Hibob and Ironclad
Keep the people, teams, and status that Ironclad and Hibob share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Ironclad keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Hibob is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Entities, Obligations, Webhooks, Workflow Approvals in Ironclad with People (Employees), Employment, Work, Salaries in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Ironclad within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Ironclad captures details of its own, such as a corrected contact or a login identity, those can flow back to Hibob in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
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 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
- 04 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
Common sync patterns
Org and team structure kept current
Department, team, and reporting-line changes from Hibob keep the groups, queues, or projects in Ironclad assigned to the right people.
Where Ironclad routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Hibob, the queues, ownership, or approvals in Ironclad update to match, so work reaches whoever holds the role now.
Onboarding: access ready on day one
A new hire recorded in Hibob creates the matching user in Ironclad with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
What you can sync between Hibob 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.
| Hibob objects | Ironclad objects | How this pairing syncs | |
|---|---|---|---|
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | 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. | Work is specific to Hibob and Workflow Approvals to Ironclad — each maps to any object or custom field on the other side. | |
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | 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. | Salaries is specific to Hibob and Signature Packets to Ironclad — each maps to any object or custom field on the other side. | |
| Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. | Time off is specific to Hibob and Workflow Documents to Ironclad — each maps to any object or custom field on the other side. | |
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | 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. | Lifecycle is specific to Hibob and Workflows to Ironclad — each maps to any object or custom field on the other side. | |
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | 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. | Documents is specific to Hibob and Records to Ironclad — each maps to any object or custom field on the other side. | |
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | 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. | Named lists is specific to Hibob and Entities to Ironclad — each maps to any object or custom field on the other side. |
How changes propagate between Hibob 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.
Hibob Ironclad Sub-second propagation
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
DeliveryEach detected change is written to Ironclad through its API, with automatic retries and rate-limit backoff.
Ironclad Hibob 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 Hibob through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
- 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 Hibob ⇄ Ironclad
Connect Hibob and Ironclad for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Ironclad connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob 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 Hibob or Ironclad record.
Observability
Monitoring
Track your Hibob ⇄ Ironclad sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Hibob and Ironclad.
How the Hibob and Ironclad connectors work
Hibob
- Integration surface
- REST API (the Bob API)
- Authentication
- Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
- Change detection
- Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
- Capabilities
- read · write · webhooks
- Rate limits
- Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
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 Hibob 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 Hibob 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.
Hibob
connected
Ironclad
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob 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 · Hibob ⇄ 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.
Hibob IroncladCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Ironclad integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Ironclad: authenticate both systems, choose the objects to sync (such as Hibob's Work and Salaries), 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 Hibob and Ironclad records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and Ironclad connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–Ironclad integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Hibob and Ironclad. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Hibob: Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event). 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.
-
On the Ironclad side: Entities, Obligations, Webhooks, Workflow Approvals, plus custom fields where Ironclad exposes them. On the Hibob side: People (Employees), Employment, Work, Salaries. 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
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 511 integrations available for Hibob and Ironclad.
Popular · 7 of 511
-
Hibob ⇄ Customer.io -
Hibob ⇄ eClinicalWorks -
Hibob ⇄ Full Enrich -
Ironclad ⇄ Lever -
Ironclad ⇄ Namely -
Ironclad ⇄ Paylocity -
Ironclad ⇄ Ukg Ready
No integrations match .
