Skip to content
Human resources ⇄ Database

Hibob to IBM AS/400 integration — real-time, two-way sync

Keep Hibob and IBM AS/400 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 IBM AS/400

Put your workforce data where your apps can reach it: IBM AS/400 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. IBM AS/400 is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: People (Employees), Employment, Work, Salaries in Hibob need to exist as queryable Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400 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 Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400 with People (Employees), Employment, Work, Salaries 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 Use journal-based change capture to replicate IBM i data into a cloud warehouse for reporting.
  • 02 Keep customer and item files aligned with an ecommerce platform or modern ERP during phased modernization.
  • 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

Org and structure stay aligned

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

Computed and operational fields flow back

Values assembled or corrected in IBM AS/400 write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Hibob land as queryable Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Hibob and IBM AS/400

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 IBM AS/400 objects How this pairing syncs
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Libraries The schema-equivalent containers that scope which files a sync reads. Documents is specific to Hibob and Libraries to IBM AS/400 — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Physical files (tables) The Db2 for i tables mapped directly to sync targets. Named lists is specific to Hibob and Physical files (tables) to IBM AS/400 — 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. Logical files (views) Indexed or filtered views over physical files, usable as read sources. People (Employees) is specific to Hibob and Logical files (views) to IBM AS/400 — 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. Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Employment is specific to Hibob and Members to IBM AS/400 — 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. Rows / records The unit of read and write, accessed via SQL or record-level access. Work is specific to Hibob and Rows / records to IBM AS/400 — 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. Journals and journal receivers The change log that enables log-based CDC on journaled files. Salaries is specific to Hibob and Journals and journal receivers to IBM AS/400 — each maps to any object or custom field on the other side.

How changes propagate between Hibob and IBM AS/400

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 IBM AS/400 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 IBM AS/400 as a row-level write, with types converted between the two schemas.

IBM AS/400 Hibob Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

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.
  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
What ships with Hibob ⇄ IBM AS/400

Connect Hibob and IBM AS/400 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–IBM AS/400 connection.

Real-time

Two-way sync

Changes in Hibob or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Hibob or IBM AS/400 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 IBM AS/400 record.

Observability

Monitoring

Track your Hibob ⇄ IBM AS/400 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 IBM AS/400.

How the Hibob and IBM AS/400 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

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.
How it works

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

    Choose tables

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

Hibob and IBM AS/400 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 433 integrations available for Hibob and IBM AS/400.

Popular · 8 of 433
All Hibob integrations All IBM AS/400 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