Skip to content
Business productivity ⇄ Human resources

Customer.io to Hibob integration — real-time, two-way sync

Keep Customer.io 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 Customer.io and Hibob

Keep the people, teams, and status that Customer.io 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 Customer.io 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 Broadcasts, Deliveries / Messages, Newsletters, People in Customer.io with Employment, Work, Salaries, Time off in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Customer.io within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Customer.io 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 Keep unsubscribe and subscription-preference state consistent between Customer.io and the CRM to avoid compliance gaps.
  • 02 Sync account-level objects and their person relationships for B2B messaging keyed to company attributes.
  • 03 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
  • 04 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.

Common sync patterns

Where Customer.io routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Hibob, the queues, ownership, or approvals in Customer.io update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Hibob creates the matching user in Customer.io with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

Offboarding: no standing access after a departure

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

What you can sync between Customer.io 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.

Customer.io objects Hibob objects How this pairing syncs
Campaigns Automated workflows whose membership and metrics can be read via the App API. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Campaigns is specific to Customer.io and Work to Hibob — each maps to any object or custom field on the other side.
Broadcasts One-off sends to segments or audiences, triggerable via API. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Broadcasts is specific to Customer.io and Salaries to Hibob — each maps to any object or custom field on the other side.
Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Deliveries / Messages is specific to Customer.io and Time off to Hibob — each maps to any object or custom field on the other side.
Newsletters Recurring email sends with performance metrics available for reporting syncs. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Newsletters is specific to Customer.io and Lifecycle to Hibob — each maps to any object or custom field on the other side.
People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. People is specific to Customer.io and Documents to Hibob — each maps to any object or custom field on the other side.
Objects Non-person entities such as accounts or companies, related to people for account-level messaging. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Objects is specific to Customer.io and Named lists to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Customer.io 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.

Customer.io Hibob Sub-second propagation

DetectionCustomer.io notifies Stacksync of record changes through webhook events. Reporting webhooks push message and delivery events.

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

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

Rate-limit considerations

  • Customer.io: Subject to per-API rate limits documented by Customer.io.
  • 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 Customer.io ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Customer.io ⇄ Hibob sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Customer.io and Hibob.

How the Customer.io and Hibob connectors work

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io

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 Customer.io 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 Customer.io 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
    Customer.io connected
    Hibob connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Customer.io 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 417 integrations available for Customer.io and Hibob.

Popular · 7 of 417
All Customer.io 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