Two-way sync
Changes in Hibob or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Keep Hibob and Sysaid in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Sysaid 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 Changes, Users, Assets, Configuration Items (CIs) in Sysaid with Time off, Lifecycle, Documents, Named lists in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Sysaid within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Sysaid 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.
A new hire recorded in Hibob creates the matching user in Sysaid with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in Hibob, the matching account in Sysaid is deactivated or flagged, so departures do not leave open access behind.
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.
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 | Sysaid objects | How this pairing syncs | |
|---|---|---|---|
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. | Named lists is specific to Hibob and Users to Sysaid — 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. | Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. | People (Employees) is specific to Hibob and Assets to Sysaid — 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. | Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. | Employment is specific to Hibob and Configuration Items (CIs) to Sysaid — 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. | Companies Customer and department organizations that scope tickets and users; mapped to Accounts in a CRM or org tables in a database. | Work is specific to Hibob and Companies to Sysaid — 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. | Custom Fields Org-specific fields on service records, discoverable through the API so mappings can be generated without hardcoding names. | Salaries is specific to Hibob and Custom Fields to Sysaid — 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. | Incidents Break/fix tickets under /api/v1/sr with type=incident; created and updated two-way with status, priority, assignee, category, and SLA fields. | Time off is specific to Hibob and Incidents to Sysaid — each maps to any object or custom field on the other side. |
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.
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 Sysaid through its API, with automatic retries and rate-limit backoff.
DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Sysaid connection.
Changes in Hibob or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Hibob or Sysaid data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Hibob or Sysaid record.
Track your Hibob ⇄ Sysaid sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Hibob and Sysaid.
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.
Authenticate Hibob and Sysaid with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Hibob and Sysaid 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Sysaid: authenticate both systems, choose the objects to sync (such as Hibob's Named lists and People (Employees)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Sysaid side: Changes, Users, Assets, Configuration Items (CIs), plus custom fields where Sysaid exposes them. On the Hibob side: Time off, Lifecycle, Documents, Named lists. 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 Sysaid: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Hibob creates the matching user in Sysaid with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
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. Sysaid: REST API (JSON). Authentication: Client-credentials app keys: an application key (clientId/clientSecret) is created via /v1/application-keys, then exchanged at /v1/access-tokens for a bearer token (default 24h, up to 30 days); an x-sysaid-accountid header scopes the account. Legacy V0 uses session-cookie login. Stacksync manages authentication, retries, and rate limits on both sides.
Sysaid: SysAid ships cloud and on-premise editions; on-prem instances must be network-reachable from Stacksync, and the legacy V0 API uses session-cookie login instead of tokens. 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 Sysaid without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 511 integrations available for Hibob and Sysaid.