Real-time
Two-way sync
Changes in Hibob or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Hibob to Linnworks integration — real-time, two-way sync
Keep Hibob and Linnworks 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 Linnworks
Sync the workers, org structure, and cost centers that Linnworks and Hibob share in real time, so the people Hibob manages stay current in the system that runs finance and operations.
Hibob is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Linnworks runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Purchase Orders, Suppliers, Channel Listings, Returns & Refunds in Linnworks with Named lists, People (Employees), Employment, Work in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Linnworks keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 02 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
- 03 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
- 04 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
Common sync patterns
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure Hibob maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Hibob keep expense and purchase approval chains in Linnworks pointed at the right people.
Where Hibob runs payroll: labor cost in the books
Pay and compensation data from Hibob posts into Linnworks as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Hibob and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Suppliers Vendor records keep procurement data consistent across tools. | Lifecycle is specific to Hibob and Suppliers to Linnworks — 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. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Documents is specific to Hibob and Channel Listings to Linnworks — 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. | Returns & Refunds Post-sale records flow to finance and support systems. | Named lists is specific to Hibob and Returns & Refunds to Linnworks — each maps to any object or custom field on the other side. | |
| People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | People (Employees) is specific to Hibob and Shipping Services to Linnworks — each maps to any object or custom field on the other side. | |
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Employment is specific to Hibob and Open Orders to Linnworks — 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. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Work is specific to Hibob and Processed Orders to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Hibob Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Hibob ⇄ Linnworks
Connect Hibob and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Hibob ⇄ Linnworks 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 Linnworks.
How the Hibob and Linnworks 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.
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Hibob to Linnworks — 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 Linnworks 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
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Linnworks 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 ⇄ LinnworksCustomers 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 LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Linnworks: authenticate both systems, choose the objects to sync (such as Hibob's Lifecycle and Documents), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Hibob and Linnworks. 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 Linnworks: Polling on order and stock endpoints. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Linnworks side: Purchase Orders, Suppliers, Channel Listings, Returns & Refunds, plus custom fields where Linnworks exposes them. On the Hibob side: Named lists, People (Employees), Employment, Work. 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 Linnworks: One org structure; Reporting lines drive approvals; Where Hibob runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure Hibob maintains.
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 504 integrations available for Hibob and Linnworks.
Popular · 7 of 504
-
Hibob ⇄ Fishbowl Manufacturing -
Hibob ⇄ Infor CloudSuite - Hibob ⇄ Infor LN
-
Linnworks ⇄ Greenhouse -
Linnworks ⇄ Jobvite -
Linnworks ⇄ Lever -
Linnworks ⇄ Namely
No integrations match .
