Skip to content
Human resources ⇄ Business productivity

Hibob to Orderful integration — real-time, two-way sync

Keep Hibob and Orderful 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 Orderful

Keep the people, teams, and status that Orderful 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 Orderful 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 Webhook events, Transactions, Trading partners, Relationships in Orderful with Salaries, Time off, Lifecycle, Documents in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Orderful within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Orderful 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 Mirror transaction statuses and acknowledgments into a database for supply chain visibility dashboards.
  • 02 Onboard new retail partners by mapping Orderful's JSON transactions to existing order tables instead of building per-partner EDI maps.
  • 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

Offboarding: no standing access after a departure

When someone is marked as leaving in Hibob, the matching account in Orderful is deactivated or flagged, so departures do not leave open access behind.

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

Department, team, and reporting-line changes from Hibob keep the groups, queues, or projects in Orderful assigned to the right people.

What you can sync between Hibob and Orderful

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 Orderful objects How this pairing syncs
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Trading partners The retailers, carriers, and suppliers a company exchanges documents with Documents is specific to Hibob and Trading partners to Orderful — 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. Relationships Active partner connections per transaction type that govern what can be sent and received Named lists is specific to Hibob and Relationships to Orderful — 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. Validation guidelines Partner-specific rules transactions are checked against before delivery People (Employees) is specific to Hibob and Validation guidelines to Orderful — 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. Acknowledgments 997 functional acknowledgments confirming receipt of transmitted documents Employment is specific to Hibob and Acknowledgments to Orderful — 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. Webhook events Push notifications for inbound documents and transaction status changes Work is specific to Hibob and Webhook events to Orderful — 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. Transactions EDI documents such as 850 purchase orders, 810 invoices, and 856 ship notices, represented as JSON Salaries is specific to Hibob and Transactions to Orderful — each maps to any object or custom field on the other side.

How changes propagate between Hibob and Orderful

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 Orderful 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 Orderful through its API, with automatic retries and rate-limit backoff.

Orderful Hibob Sub-second propagation

DetectionOrderful notifies Stacksync of record changes through webhook events. Webhooks push inbound transactions and status events.

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.
  • Orderful: Subject to the platform's API rate limits.
What ships with Hibob ⇄ Orderful

Connect Hibob and Orderful for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Orderful connection.

Real-time

Two-way sync

Changes in Hibob or Orderful instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Hibob or Orderful 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 Orderful record.

Observability

Monitoring

Track your Hibob ⇄ Orderful 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 Orderful.

How the Hibob and Orderful 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.
Hibob setup guide

Orderful

Integration surface
REST API (JSON)
Authentication
API key
Change detection
webhooks push inbound transactions and status events; polling available as fallback
Capabilities
read · write · webhooks
Rate limits
subject to the platform's API rate limits
How it works

How to connect Hibob to Orderful — 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.

  1. 01

    Connect your apps

    Authenticate Hibob and Orderful with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Hibob connected
    Orderful connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and Orderful 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Hibob ⇄ Orderful
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Hibob Orderful
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and Orderful integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 396 integrations available for Hibob and Orderful.

Popular · 7 of 396
All Hibob integrations All Orderful integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own