Automate BambooHR Employee Management

This skill automates BambooHR human resources operations through Composio's BambooHR toolkit, reached via Rube MCP. It gives an assistant a tool-by-tool playbook for five workflows: listing and searching employees, tracking employee changes, managing time off, updating employee information, and managing dependents and benefits. Each workflow names the tool sequence, the key parameters, and the pitfalls to avoid. The skill's own rule is to always call RUBE_SEARCH_TOOLS first to get current tool schemas, since parameters can change.

The workflows in more detail:

• Employees: BAMBOOHR_GET_ALL_EMPLOYEES returns the directory with basic info, and BAMBOOHR_GET_EMPLOYEE returns details for one numeric employee ID. A comma-separated fields parameter, such as firstName, lastName, department, and jobTitle, controls what comes back. Inactive or terminated employees may appear, so check the status field.
• Changes: BAMBOOHR_EMPLOYEE_GET_CHANGED takes a required since value in ISO 8601 format and a change type such as inserted, updated, or deleted. It returns only IDs, so you call GET_EMPLOYEE for each one. This suits incremental sync, where you cache the last sync timestamp.
• Time off: list types first, then check balances, list requests, create a request, and update a request. Creating a request does not auto-approve it; approval is a separate step needing manager or admin permission.
• Updates: fetch the current employee, then call BAMBOOHR_UPDATE_EMPLOYEE with only the fields to change. Some fields are read-only, and updates appear in the employee's change history.
• Dependents and benefits: BAMBOOHR_DEPENDENTS_GET_ALL and BAMBOOHR_BENEFIT_GET_COVERAGES.

Use it when a user wants to find employees, sync HR data to another system, check or request time off, approve or deny a request, edit a profile field, or look at dependents and benefit coverage in BambooHR.

Do not use it when the task does not clearly match this scope. The output is not a substitute for environment-specific validation, testing, or expert review, and the assistant should stop and ask when required inputs, permissions, safety boundaries, or success criteria are missing. Not all BambooHR plans include benefits administration, so check account features before promising benefit data. The skill is marked critical risk in its metadata.

Inputs are numeric employee IDs, date ranges in YYYY-MM-DD format, time-off type IDs resolved by name from the types list, and field-value pairs for updates. Date formats differ between endpoints: time-off uses YYYY-MM-DD while change detection uses ISO 8601 with a timezone.

Outputs are BambooHR records and status results. Responses may be nested under a data key, fields vary with the fields parameter, and empty fields may be omitted or null, so the skill advises parsing defensively with fallbacks. Balances may be in hours or days depending on company configuration.

• Rube MCP by Composio, added by pointing your client at the Rube MCP endpoint, with no API keys needed for that step.
• An active BambooHR connection created through RUBE_MANAGE_CONNECTIONS with the bamboohr toolkit. If the connection is not ACTIVE, follow the returned auth link and confirm ACTIVE before running workflows.

Operational cautions: employee data includes personal information such as names, addresses, and SSN, and dependent data is especially sensitive. Data access depends on API key permissions. The BambooHR API is rate limited per key, so throttle bulk operations and prefer GET_ALL_EMPLOYEES over many single GET_EMPLOYEE calls.

It is for HR operations staff, people-ops engineers, and anyone building HR automations who wants an assistant to drive BambooHR safely, with correct ID resolution, approval steps, and sensitive-data handling.