Real-time
Two-way sync
Changes in Hibob or Pigment instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Accounting and finance
Hibob to Pigment integration — real-time, two-way sync
Keep Hibob and Pigment 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 Pigment
Keep the employee, department, and cost records that Pigment and Hibob share consistent in real time, so the finance system and the people system stop drifting apart.
Pigment runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Hibob runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.
Stacksync syncs Users and permissions, Applications, Metrics, Dimension lists in Pigment with Lifecycle, Documents, Named lists, People (Employees) in Hibob bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.
Common use cases
- 01 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 03 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
- 04 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
Common sync patterns
Status changes propagate
A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
People-driven costs land in finance
Compensation, reimbursements, or other costs tied to a person on the Hibob side flow into Pigment for posting, so the books reflect what people actually cost without manual re-entry.
New person becomes a known record in finance
When someone is added in Hibob, a matching employee or payee record appears in Pigment, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
What you can sync between Hibob and Pigment
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Users and permissions Access controls governing which model areas a sync can touch | Employment is specific to Hibob and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Applications Planning models organized by domain such as finance, sales, or workforce | Work is specific to Hibob and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Salaries is specific to Hibob and Metrics to Pigment — 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. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Time off is specific to Hibob and Dimension lists to Pigment — 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. | Tables Row-based transactional data loaded into models from source systems | Lifecycle is specific to Hibob and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Documents is specific to Hibob and Scenarios to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Pigment
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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Hibob Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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.
- Pigment: Subject to the platform's API rate limits.
What ships with Hibob ⇄ Pigment
Connect Hibob and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Pigment 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 Pigment record.
Observability
Monitoring
Track your Hibob ⇄ Pigment 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 Pigment.
How the Hibob and Pigment 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.
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Hibob to Pigment — 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 Pigment 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
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Pigment 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 ⇄ PigmentCustomers 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 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Pigment: authenticate both systems, choose the objects to sync (such as Hibob's Employment and Work), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Users and permissions, Applications, Metrics, Dimension lists, plus custom fields where Pigment exposes them. On the Hibob side: Lifecycle, Documents, Named lists, People (Employees). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Hibob and Pigment: Status changes propagate; People-driven costs land in finance; New person becomes a known record in finance. A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
-
Hibob: 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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Hibob: The employee.updated webhook flags which fields changed rather than sending the full record, so Bob recommends an API call for complete data; deleting a table entry triggers no webhook because Bob has no table-entry deletion event. Stacksync's field mapping accounts for these differences between Hibob and Pigment without custom code.
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 411 integrations available for Hibob and Pigment.
Popular · 8 of 411
-
Hibob ⇄ Logisense -
Hibob ⇄ Bill -
Hibob ⇄ Braintree -
Hibob ⇄ Navan -
Pigment ⇄ Ukg Ready -
Pigment ⇄ BambooHR -
Pigment ⇄ Success Factors -
Pigment ⇄ Ceridian Dayforce
No integrations match .
