Plex and BambooHR integration

What moves between them

Employee data flows from BambooHR into Plex. New hires, terminations, rehires, and compensation changes in BambooHR are read and synced into Plex on a configurable schedule. Employment status, job title, department, and compensation history are aligned so Plex headcount and labor-costing reports reflect the current state in BambooHR. Job codes and departments in Plex are pre-mapped to BambooHR job info so assignments land on valid Plex dimensions. Changes flow one way because BambooHR is the system of record for people data.

How ml-connector handles it

ml-connector stores the BambooHR OAuth credentials encrypted and refreshes the access token every 55 minutes before expiry, so a token refresh does not cause a stale-data read. Because BambooHR requires a per-customer subdomain in every URL and token endpoint, ml-connector accepts and validates that subdomain for each customer and constructs the correct token endpoint at runtime. Plex requires an OAuth token on the REST API side, so ml-connector stores and refreshes that as well. Because neither system offers guaranteed idempotency, ml-connector tracks the last modified timestamp of each employee record and uses that to detect changes, filtering the BambooHR employee list by modified date on each poll. BambooHR employee field queries require explicit field enumeration, so ml-connector enumerates the fields needed for Plex (employee name, job title, department, employment status, hire date, termination date, and compensation). Plex role-based permissions are validated on connection test so an unpermissioned integration user is caught before syncs begin. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized discrete manufacturer with plants across three states runs Plex ERP for production, procurement, and finance, and uses BambooHR to manage payroll and HR across all locations. Before the integration, the manufacturing operations team manually updated Plex employee records quarterly when HR sent headcount reports, which meant production capacity planning and labor costing lagged behind actual hires and terminations by weeks. When a line went down for retooling, the team had to search Plex manually to find trained operators because job assignments were stale. With Plex and BambooHR connected, each hire, termination, and job change in BambooHR flows into Plex within minutes, so capacity planning and labor cost allocation use current data, and operator skill searches return the actual workforce on the shop floor.

What you can do

• •Sync employees from BambooHR into Plex on a configurable schedule, capturing new hires, terminations, and rehires.
• •Keep employee job titles, departments, and employment status aligned across Plex and BambooHR.
• •Manage BambooHR OAuth token refresh and Plex OAuth credentials, handling token expiry before authentication fails.
• •Validate Plex role-based permissions for the integration user before syncs begin, and reject unpermissioned credentials.
• •Maintain a full audit trail of every employee record synced, with the ability to replay failed records.

Questions

Which direction does employee data move between Plex and BambooHR?

Employee data flows from BambooHR into Plex. BambooHR is the system of record for people data, so new hires, terminations, compensation changes, and job assignments in BambooHR sync into Plex on a schedule you control. Plex does not write employee changes back to BambooHR.

How does the integration handle BambooHR's per-customer subdomain requirement?

BambooHR requires a unique subdomain in every URL and OAuth token endpoint. ml-connector accepts the per-customer subdomain for each Plex instance, validates it, and constructs the correct BambooHR token and API endpoints at runtime, so no hardcoded URLs are needed.

What employee fields flow from BambooHR into Plex?

ml-connector syncs employee name, job title, department, employment status, hire date, termination date, and compensation history. BambooHR requires explicit field enumeration in each API request, so ml-connector enumerates only the fields needed for labor costing and capacity planning in Plex.