Extend the BambooHR connector to sync company/Public holidays
AnsweredHi team,
We use the BambooHR Fivetran connector to replicate our leave data into BigQuery. It currently syncs the per-employee time-off requests that employees submit (via the time_off_request / time_off_request_date endpoints), and that works well.
However, one category of data that matters to us for analytics is not being synced : company-wide public / national holidays.
In BambooHR itself, these are visible on each employee's Time Off page (e.g. "Maha Shivaratri" on 1 May 2026 is shown for employee "Gaurav Gupta", screenshot attached) but i think they live in BambooHR's Company Holidays feature rather than being individual user-submitted time-off requests. Because the Fivetran connector only syncs user-submitted requests, our downstream reports can't tell when an employee is off for a national holiday.
I think BambooHR exposes this data through the /v1/time_off/whos_out endpoint :
Each Time-off requests and holidays can be routed into separate tables or stored in a unified table with a type column.
Our ask: could the BambooHR connector be extended to ingest, company / public holidays in our warehouse alongside the existing time-off request data?
Ideally, either:
Public Holidays in a dedicated table (e.g. bamboohr.company_holiday with employee_id, date, holiday_name), or
A unified time_off_whos_out table with a type column distinguishing holidays from time-off requests.
This would unblock a regression we're currently working around: prior to BambooHR we used WhosOff, which auto-populated public holidays per employee.
-
Official comment
Hi Gaurav,
Thanks for the detailed writeup — this is a reasonable ask and the BambooHR API does expose what you need. The /v1/time_off/whos_out endpoint returns both time-off requests and company holidays in a single response, with a type field that distinguishes between them, so public holidays can be cleanly distinguished.
One thing I'd like to understand before we scope this: the endpoint requires a date range, and defaults to 14 days from today if none is specified. How far ahead do you need holiday data synced?
That'll help us figure out the right sync strategy.
Thanks,
Sandeep -
Want that too!
-
Hi Sandeep,Thanks for the context. For our analytics use case we only need company holidays with a rolling 6 months back and 12 months forward from sync date would cover us. Daily sync cadence is fine.Before we confirm, a few questions on how the sync would behave:
-
Deletes inside the window — if a company holiday is removed in BambooHR, will Fivetran emit a soft-delete (
_fivetran_deleted = true) on the next sync, or does the row gets removed? - MAR / costing — since this is a windowed re-sync rather than cursor-based, how is MAR counted? Content-diff (only changed rows count), or does every re-fetched row register as an update each month? Want to make sure we size the cost expectation correctly.
Thanks, Gaurav -
Deletes inside the window — if a company holiday is removed in BambooHR, will Fivetran emit a soft-delete (
-
Hi,
Can we get an update on when can the implementation be finished?
Regards
Gaurav -
Hi Gaurav,
Sorry for the delayed response here. We've added the request to our backlog and will scope it out in the next sprint. While we can't provide a timeline at this moment, we'll keep you updated on any progress.
Best,
Sandeep
Please sign in to leave a comment.
Comments
5 comments