Skip to content
Human resources ⇄ Accounting and finance

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

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

Keep the employee, department, and cost records that Pigment and BambooHR share consistent in real time, so the finance system and the people system stop drifting apart.

Pigment runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. BambooHR runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Applications, Metrics, Dimension lists, Tables in Pigment with Compensation, Time Off, Employment Status, Departments and Divisions in BambooHR bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 03 Sync Employees and Employment Status to identity and IT systems so new hires are provisioned and departures deactivated automatically.
  • 04 Read Job Information and Departments into an ERP or planning tool so headcount, cost centers, and org structure stay current.

Common sync patterns

Department and cost-center alignment

The org structure maintained in BambooHR keeps the departments or cost centers in Pigment current, so spend and headcount roll up the same way.

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the BambooHR side flow into Pigment for posting, so the books reflect what people actually cost without manual re-entry.

What you can sync between BambooHR and Pigment

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 Pigment objects How this pairing syncs
Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Employment Status is specific to BambooHR and Data imports to Pigment — 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. Users and permissions Access controls governing which model areas a sync can touch Departments and Divisions is specific to BambooHR and Users and permissions to Pigment — 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. Applications Planning models organized by domain such as finance, sales, or workforce Custom Tables is specific to BambooHR and Applications to Pigment — 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. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Reports is specific to BambooHR and Metrics to Pigment — each maps to any object or custom field on the other side.
Employees The core person record with personal and work fields; read out to identity, payroll, and IT systems, and written back from recruiting or onboarding tools. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Employees is specific to BambooHR and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Job Information Effective-dated job title, department, division, location, and reporting line; synced so org charts and provisioning systems track internal moves. Tables Row-based transactional data loaded into models from source systems Job Information is specific to BambooHR and Tables to Pigment — each maps to any object or custom field on the other side.

How changes propagate between BambooHR and Pigment

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

Pigment BambooHR Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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.
  • Pigment: Subject to the platform's API rate limits.
What ships with BambooHR ⇄ Pigment

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your BambooHR ⇄ Pigment 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 Pigment.

How the BambooHR and Pigment 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.

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

BambooHR and Pigment 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 319 integrations available for BambooHR and Pigment.

Popular · 6 of 319
All BambooHR integrations All Pigment 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