Limit to time off that you have a particular level of access to.

Limit to a particular employee (ID).

Limit to time off that occurs on/after the specified start date.

Limit to time off that occurs on/before the specified end date.

Limit to one or more status values

The ID of the time off request, which you would usually get from a "New Time Off Request" trigger step using a "Custom Value".

If left blank, we'll use the original file name.

Choose an employee to store the file under (non-employee users aren't available options).

Create a new report under the "Reports" tab and grab the id from the URL as shown here. This trigger only works for reports under "Reports".

Pick which field to watch to detect changes. By default, any field changes in the report will trigger the Zap.

Defaults to the current date if left blank and no end date is provided. Defaults to the end date if left blank and the end date is provided.

Defaults to the current date if left blank and no start date is provided. Defaults to the start date if left blank and the start date is provided.

Choose which employees to include in summary. Defaults to "All" if left blank.

API docs for BambooHR are located here https://www.bamboohr.com/api/documentation/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.