Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: Airtable and Hibob share the same people, positions, and org structure in real time.

Hibob is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Airtable is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Salaries, Time off, Lifecycle, Documents in Hibob need to exist as queryable Records, Fields, Views, Linked records in Airtable before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Records, Fields, Views, Linked records in Airtable with Salaries, Time off, Lifecycle, Documents in Hibob field by field, in real time. You decide which system owns which fields — Hibob typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Consolidate several Airtable bases into one analytical database for reporting without manual CSV exports.
  • 02 Sync form-submitted records from Airtable into downstream systems like a helpdesk or marketing platform.
  • 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

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Salaries, Time off, Lifecycle, Documents replicate into Airtable where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Hibob stay consistent in Airtable, so hierarchy-driven logic and permissions don't drift.

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

Airtable objects Hibob objects How this pairing syncs
Bases Top-level containers; each base has its own API endpoint and schema. 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. Bases is specific to Airtable and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Tables Map to sync tables; schema is readable through the base metadata endpoints. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Tables is specific to Airtable and Employment to Hibob — each maps to any object or custom field on the other side.
Records The row-level unit created, updated, and deleted during syncs, identified by rec-prefixed IDs. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Records is specific to Airtable and Work to Hibob — each maps to any object or custom field on the other side.
Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Fields is specific to Airtable and Salaries to Hibob — each maps to any object or custom field on the other side.
Views Filtered subsets of a table that can scope which records a sync reads. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Views is specific to Airtable and Time off to Hibob — each maps to any object or custom field on the other side.
Linked records Cross-table references that carry relationships between synced tables. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Linked records is specific to Airtable and Lifecycle to Hibob — each maps to any object or custom field on the other side.

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

Airtable Hibob Sub-second propagation

DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).

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

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

Rate-limit considerations

  • Airtable: The Web API enforces a per-base limit of 5 requests per second.
  • 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 Airtable ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Airtable and Hibob connectors work

Airtable

Integration surface
REST API (per-base Web API plus metadata and webhooks endpoints)
Authentication
OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a `creator` role, since only creator roles can create webhooks
Change detection
Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour
Capabilities
read · write · CDC · webhooks
Rate limits
The Web API enforces a per-base limit of 5 requests per second.
Airtable setup guide

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

    Choose tables

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

Airtable 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 Airtable and Hibob.

Popular · 8 of 541
All Airtable 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