Skip to content
Human resources ⇄ Accounting and finance

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

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

Keep the employee, department, and cost records that Workday and Hibob share consistent in real time, so the finance system and the people system stop drifting apart.

Workday 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 Organizations, Positions, Compensation, Time Off and Absence in Workday with Work, Salaries, Time off, Lifecycle 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 Sync worker records from Workday into IT and identity systems so hires, transfers, and terminations provision access automatically.
  • 02 Replicate worker, organization, and compensation data into a secured database for people analytics without giving analysts tenant access.
  • 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

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the Hibob side flow into Workday 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 Workday, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

What you can sync between Hibob and Workday

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 Workday objects How this pairing syncs
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. Positions Job seats synced with recruiting and planning tools. People (Employees) is specific to Hibob and Positions to Workday — 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. Compensation Pay components read into payroll, planning, and equity systems under strict access control. Employment is specific to Hibob and Compensation to Workday — 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. Time Off and Absence Balances and requests synced with scheduling and workforce tools. Work is specific to Hibob and Time Off and Absence to Workday — 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. Payroll Results Completed pay data exported to finance and benefits systems. Salaries is specific to Hibob and Payroll Results to Workday — 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. Suppliers Workday Financials vendor records aligned with procurement tools. Time off is specific to Hibob and Suppliers to Workday — 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. Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. Lifecycle is specific to Hibob and Customers and Invoices to Workday — each maps to any object or custom field on the other side.

How changes propagate between Hibob and Workday

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

Workday Hibob Interval-based propagation

DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.

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.
What ships with Hibob ⇄ Workday

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Hibob and Workday 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

Workday

Integration surface
SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
Authentication
OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
Change detection
Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
Capabilities
read · write
How it works

How to connect Hibob to Workday — 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 Workday 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
    Workday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and Workday 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 ⇄ Workday
    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 Workday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and Workday 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 495 integrations available for Hibob and Workday.

Popular · 8 of 495
All Hibob integrations All Workday 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