BambooHR

Manage employee data, time off requests, and HR operations via BambooHR.

Detail	Value
Category	HR
Base URL	https://api.bamboohr.com/api/gateway.php/{subdomain}/v1
Authentication	API Key
Endpoints	6
Connector key	bamboohr

Using BambooHR in a workflow

1. Go to Connections and click New Connection.
2. Pick BambooHR from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /employees/directory	Get employee directory
GET /employees/{employeeId}	Get employee data
POST /employees	Add a new employee
PUT /employees/{employeeId}	Update employee data
GET /time_off/requests	List time off requests
GET /reports/{reportId}	Get a report

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /employees/directory

Get employee directory

Detail	Value
Operation ID	hr.getDirectory
Method	GET
Path	/employees/directory

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.getDirectory.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.

GET /employees/{employeeId}

Get employee data

Detail	Value
Operation ID	hr.getEmployee
Method	GET
Path	/employees/{employeeId}

Parameters

Name	Location	Type	Required
employeeId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.getEmployee.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.

POST /employees

Add a new employee

Detail	Value
Operation ID	hr.createEmployee
Method	POST
Path	/employees

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.createEmployee.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.

PUT /employees/{employeeId}

Update employee data

Detail	Value
Operation ID	hr.updateEmployee
Method	PUT
Path	/employees/{employeeId}

Parameters

Name	Location	Type	Required
employeeId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.updateEmployee.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.

GET /time_off/requests

List time off requests

Detail	Value
Operation ID	hr.listTimeOffRequests
Method	GET
Path	/time_off/requests

Parameters

Name	Location	Type	Required
start	query	string	Yes
end	query	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.listTimeOffRequests.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.

GET /reports/{reportId}

Get a report

Detail	Value
Operation ID	hr.getReport
Method	GET
Path	/reports/{reportId}

Parameters

Name	Location	Type	Required
reportId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your BambooHR connection from the Connection dropdown.
3. In the Operation dropdown, select hr.getReport.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream BambooHR API reference.