Integrations / Recruiting

BambooHR

Look up employees and the company directory, see time off requests and who's out, run saved reports, and trigger workflows when employees are added, changed or removed in BambooHR.

10 tools 3 trigger events

Tools

bamboohr.list_employees

List employees, optionally filtered by status, department, location, manager, name or work email, 250 per page by default. Employee IDs are numeric strings, e.g. "123". Fields the key can't read come back null and are named in _restrictedFields.

statusdepartmentlocationreports_to_idfirst_namelast_namework_emailfieldslimitafter

bamboohr.get_employee

Get one employee's fields. Employee IDs are numeric strings; 0 is the key's own employee. Fields the key can't see are left out silently.

employee_id*fields

bamboohr.get_directory

The company directory as your access level sees it, with name, job title, department, location, work contact details and manager for each employee. The fields vary with the company's directory settings.

bamboohr.list_fields

List every employee field in the account, with the names and aliases get_employee and list_employees take.

bamboohr.list_time_off_requests

List time off requests overlapping a date range, or changed since a time, with status, type, amount and notes. Request and employee IDs are numeric strings. An empty list can also mean the key isn't allowed to see them.

startendupdated_sincestatusemployee_idactiontype

bamboohr.whos_out

Who's out and which company holidays fall in a date range, today through the next 14 days by default. Entries are type timeOff, with an employee ID, or holiday.

startend

bamboohr.list_reports

List the saved custom reports the key can run. Report IDs are integers.

page_sizepage

bamboohr.run_report

Run a saved custom report and return its rows, one flat object of field values per employee, with its columns in fields.

report_id*page_sizepage

bamboohr.api_get

Send a GET request to any BambooHR API path under https://{company_domain}.bamboohr.com/api/v1 and return the response. For endpoints the named tools don't cover.

path*params

bamboohr.api_request writes

Send a POST, PUT, PATCH or DELETE request to any BambooHR API path under https://{company_domain}.bamboohr.com/api/v1.

method*path*paramsbody

Tick Allow raw writes on the connection to add api_request, which can send POST, PUT, PATCH and DELETE requests to any BambooHR API path.

Connect

  1. In BambooHR, click your name in the lower left corner and choose API Keys, then Add New Key. If API Keys isn't in the menu, your access level doesn't allow API keys and an admin has to grant it.
  2. Paste the key on the connection, and set the company domain to the first part of your BambooHR address, e.g. acme for acme.bamboohr.com. The key sees what your BambooHR access level sees.
  3. To trigger workflows, an admin opens Account Settings → Webhooks, adds a webhook with the URL shown on the connection page, picks the fields to monitor and post, sets the format to JSON, and pastes the webhook's private key on the connection.

Credentials

API key Webhook private key

BambooHR API docs

Triggers

In BambooHR, an admin opens Account Settings → Webhooks, adds a webhook with this URL, chooses the fields to monitor and to post, sets the format to JSON, and pastes the webhook's private key on this connection. Each changed employee runs the workflow once.

Events

CreatedUpdatedDeleted
 trigger
kind: bamboohr
connection: bamboohr
events: [Created]

Turn one person's AI process into the company's.

Murmurator is invite-only. Already invited? Sign in and build something real.

Sign in Talk to us