Skip to content
Human resources ⇄ Database

BambooHR to Citus integration — real-time, two-way sync

Keep BambooHR and Citus 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 BambooHR and Citus

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

BambooHR is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Citus is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employees, Job Information, Compensation, Time Off in BambooHR need to exist as queryable Distributed tables, Reference tables, Local tables, Schemas in Citus 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 Distributed tables, Reference tables, Local tables, Schemas in Citus with Employees, Job Information, Compensation, Time Off in BambooHR field by field, in real time. You decide which system owns which fields — BambooHR 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 a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 02 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • 03 Read Job Information and Departments into an ERP or planning tool so headcount, cost centers, and org structure stay current.
  • 04 Push approved Time Off into capacity and scheduling systems so project plans reflect real availability.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in Citus write onto the matching record in BambooHR where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in BambooHR land as queryable Distributed tables, Reference tables, Local tables, Schemas in Citus, so internal apps and dashboards read live data instead of a periodic export.

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.

What you can sync between BambooHR and Citus

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.

BambooHR objects Citus objects How this pairing syncs
Compensation Effective-dated pay rate, schedule, and change reason; read into planning and payroll systems with access restricted to authorized fields. Sequences Key generators that matter when external writes must not collide with application inserts. Compensation is specific to BambooHR and Sequences to Citus — each maps to any object or custom field on the other side.
Time Off Requests, balances, and policies; read for absence calendars and capacity planning, with approved requests written from an external scheduling tool. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Time Off is specific to BambooHR and Distributed tables to Citus — each maps to any object or custom field on the other side.
Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Employment Status is specific to BambooHR and Reference tables to Citus — each maps to any object or custom field on the other side.
Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Departments and Divisions is specific to BambooHR and Local tables to Citus — each maps to any object or custom field on the other side.
Custom Tables Company-specific effective-dated tables (assets, training, certifications); rows read and written so custom HR data isn't trapped in the HRIS. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Custom Tables is specific to BambooHR and Schemas to Citus — each maps to any object or custom field on the other side.
Reports Saved company reports retrievable via API; read out on a schedule to feed a warehouse without rebuilding field-by-field queries. Views Curated projections over distributed data, often used as read-only sync sources. Reports is specific to BambooHR and Views to Citus — each maps to any object or custom field on the other side.

How changes propagate between BambooHR and Citus

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.

BambooHR Citus Sub-second propagation

DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Citus BambooHR Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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

Rate-limit considerations

  • BambooHR: Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.
What ships with BambooHR ⇄ Citus

Connect BambooHR and Citus for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in BambooHR or Citus instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BambooHR or Citus 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 BambooHR or Citus record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BambooHR and Citus.

How the BambooHR and Citus connectors work

BambooHR

Integration surface
BambooHR API (REST, per-company subdomain)
Authentication
API key per user over HTTP Basic auth (key as username), scoped to that user's permission level in BambooHR; OAuth/OpenID available for SSO-enabled apps
Change detection
The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling; webhooks can fire on monitored field changes
Capabilities
read · write · webhooks
Rate limits
Requests are rate-limited per API key with standard REST throttling (429 on excess); bulk reads are best done through saved Reports or the updated-IDs delta endpoint rather than per-employee calls.

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

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

    Choose tables

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

BambooHR and Citus 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 340 integrations available for BambooHR and Citus.

Popular · 8 of 340
All BambooHR integrations All Citus 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