Skip to content
Data warehouse ⇄ Human resources

Azure Synapse Analytics to Hibob integration — real-time, two-way sync

Keep Azure Synapse Analytics and Hibob 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 Azure Synapse Analytics and Hibob

Land the people and organization records from Hibob in Azure Synapse Analytics as live tables for workforce reporting, without extract jobs, and write computed results back where Hibob can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Hibob is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Azure Synapse Analytics next to everything else the company measures.

Stacksync syncs People (Employees), Employment, Work, Salaries from Hibob into tables in Azure Synapse Analytics continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Azure Synapse Analytics, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Hibob where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Publish warehouse aggregates (account health scores, LTV) from Synapse back into operational tools like a CRM.
  • 02 Sync curated Synapse views into an operational Postgres or Azure SQL database that applications can query cheaply.
  • 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

Write-back of computed values

Segments, rollups, or risk flags computed in Azure Synapse Analytics sync back onto the matching records in Hibob, where the HR team sees them in the system they already use.

HR data in the warehouse, minus the pipeline

People and organization records from Hibob arrive in Azure Synapse Analytics as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

Analysts combine Hibob's workforce records with finance, product, or operational data already in Azure Synapse Analytics for reporting the HR system cannot produce on its own.

What you can sync between Azure Synapse Analytics and Hibob

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.

Azure Synapse Analytics objects Hibob objects How this pairing syncs
Views Curated projections used when downstream tools should not read base tables directly. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Views is specific to Azure Synapse Analytics and Documents to Hibob — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Schemas is specific to Azure Synapse Analytics and Named lists to Hibob — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. 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. Materialized views is specific to Azure Synapse Analytics and People (Employees) to Hibob — each maps to any object or custom field on the other side.
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. SQL pools is specific to Azure Synapse Analytics and Employment to Hibob — each maps to any object or custom field on the other side.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Work to Hibob — each maps to any object or custom field on the other side.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. External tables is specific to Azure Synapse Analytics and Salaries to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics and Hibob

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.

Azure Synapse Analytics Hibob Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.

Hibob Azure Synapse Analytics 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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

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 Azure Synapse Analytics ⇄ Hibob

Connect Azure Synapse Analytics and Hibob for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ Hibob sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Hibob.

How the Azure Synapse Analytics and Hibob connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

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
How it works

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

    Choose tables

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

Azure Synapse Analytics and Hibob 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 541 integrations available for Azure Synapse Analytics and Hibob.

Popular · 8 of 541
All Azure Synapse Analytics integrations All Hibob 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