Bamboohr Automation

# BambooHR Automation via Rube MCP

Automate BambooHR human resources operations through Composio's BambooHR toolkit via Rube MCP.

Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)

- Active BambooHR connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`

- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds

2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`

3. If connection is not ACTIVE, follow the returned auth link to complete BambooHR authentication

4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. List and Search Employees

**When to use**: User wants to find employees or get the full employee directory

**Tool sequence**:

1. `BAMBOOHR_GET_ALL_EMPLOYEES` - Get the employee directory [Required]

2. `BAMBOOHR_GET_EMPLOYEE` - Get detailed info for a specific employee [Optional]

**Key parameters**:

- For GET_ALL_EMPLOYEES: No required parameters; returns directory

- For GET_EMPLOYEE:

- `id`: Employee ID (numeric)

- `fields`: Comma-separated list of fields to return (e.g., 'firstName,lastName,department,jobTitle')

**Pitfalls**:

- Employee IDs are numeric integers

- GET_ALL_EMPLOYEES returns basic directory info; use GET_EMPLOYEE for full details

- The `fields` parameter controls which fields are returned; omitting it may return minimal data

- Common fields: firstName, lastName, department, division, jobTitle, workEmail, status

- Inactive/terminated employees may be included; check `status` field

2. Track Employee Changes

**When to use**: User wants to detect recent employee data changes for sync or auditing

**Tool sequence**:

1. `BAMBOOHR_EMPLOYEE_GET_CHANGED` - Get employees with recent changes [Required]

**Key parameters**:

- `since`: ISO 8601 datetime string for change detection threshold

- `type`: Type of changes to check (e.g., 'inserted', 'updated', 'deleted')

**Pitfalls**:

- `since` parameter is required; use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')

- Returns IDs of changed employees, not full employee data

- Must call GET_EMPLOYEE separately for each changed employee's details

- Useful for incremental sync workflows; cache the last sync timestamp

3. Manage Time-Off

**When to use**: User wants to view time-off balances, request time off, or manage requests

**Tool sequence**:

1. `BAMBOOHR_GET_META_TIME_OFF_TYPES` - List available time-off types [Prerequisite]

2. `BAMBOOHR_GET_TIME_OFF_BALANCES` - Check current balances [Optional]

3. `BAMBOOHR_GET_TIME_OFF_REQUESTS` - List existing requests [Optional]

4. `BAMBOOHR_CREATE_TIME_OFF_REQUEST` - Submit a new request [Optional]

5. `BAMBOOHR_UPDATE_TIME_OFF_REQUEST` - Modify or approve/deny a request [Optional]

**Key parameters**:

- For balances: `employeeId`, time-off type ID

- For requests: `start`, `end` (date range), `employeeId`

- For creation:

- `employeeId`: Employee to request for

- `timeOffTypeId`: Type ID from GET_META_TIME_OFF_TYPES

- `start`: Start date (YYYY-MM-DD)

- `end`: End date (YYYY-MM-DD)

- `amount`: Number of days/hours

- `notes`: Optional notes for the request

- For update: `requestId`, `status` ('approved', 'denied', 'cancelled')

**Pitfalls**:

- Time-off type IDs are numeric; resolve via GET_META_TIME_OFF_TYPES first

- Date format is 'YYYY-MM-DD' for start and end dates

- Balances may be in hours or days depending on company configuration

- Request status updates require appropriate permissions (manager/admin)

- Creating a request does NOT auto-approve it; separate approval step needed

4. Update Employee Information

**When to use**: User wants to modify employee profile data

**Tool sequence**:

1. `BAMBOOHR_GET_EMPLOYEE` - Get current employee data [Prerequisite]

2. `BAMBOO