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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit bamboohr
- If connection is not ACTIVE, follow the returned auth link to complete BambooHR authentication
- 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:
BAMBOOHR_GET_ALL_EMPLOYEES - Get the employee directory [Required]
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:
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:
BAMBOOHR_GET_META_TIME_OFF_TYPES - List available time-off types [Prerequisite]
BAMBOOHR_GET_TIME_OFF_BALANCES - Check current balances [Optional]
BAMBOOHR_GET_TIME_OFF_REQUESTS - List existing requests [Optional]
BAMBOOHR_CREATE_TIME_OFF_REQUEST - Submit a new request [Optional]
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:
BAMBOOHR_GET_EMPLOYEE - Get current employee data [Prerequisite]
BAMBOOHR_UPDATE_EMPLOYEE - Update employee fields [Required]
Key parameters:
id: Employee ID (numeric, required)
- Field-value pairs for the fields to update (e.g.,
department, jobTitle, workPhone)
Pitfalls:
- Only fields included in the request are updated; others remain unchanged
- Some fields are read-only and cannot be updated via API
- Field names must match BambooHR's expected field names exactly
- Updates are audited; changes appear in the employee's change history
- Verify current values with GET_EMPLOYEE before updating to avoid overwriting
5. Manage Dependents and Benefits
When to use: User wants to view employee dependents or benefit coverage
Tool sequence:
BAMBOOHR_DEPENDENTS_GET_ALL - List all dependents [Required]
BAMBOOHR_BENEFIT_GET_COVERAGES - Get benefit coverage details [Optional]
Key parameters:
- For dependents: Optional
employeeId filter
- For benefits: Depends on schema; check RUBE_SEARCH_TOOLS for current parameters
Pitfalls:
- Dependent data includes sensitive PII; handle with appropriate care
- Benefit coverages may include multiple plan types per employee
- Not all BambooHR plans include benefits administration; check account features
- Data access depends on API key permissions
Common Patterns
ID Resolution
Employee name -> Employee ID:
1. Call BAMBOOHR_GET_ALL_EMPLOYEES
2. Find employee by name in directory results
3. Extract id (numeric) for detailed operations
Time-off type name -> Type ID:
1. Call BAMBOOHR_GET_META_TIME_OFF_TYPES
2. Find type by name (e.g., 'Vacation', 'Sick Leave')
3. Extract id for time-off requests
Incremental Sync Pattern
For keeping external systems in sync with BambooHR:
1. Store last_sync_timestamp
2. Call BAMBOOHR_EMPLOYEE_GET_CHANGED with since=last_sync_timestamp
3. For each changed employee ID, call BAMBOOHR_GET_EMPLOYEE
4. Process updates in external system
5. Update last_sync_timestamp
Time-Off Workflow
1. GET_META_TIME_OFF_TYPES -> find type ID
2. GET_TIME_OFF_BALANCES -> verify available balance
3. CREATE_TIME_OFF_REQUEST -> submit request
4. UPDATE_TIME_OFF_REQUEST -> approve/deny (manager action)
Known Pitfalls
Employee IDs:
- Always numeric integers
- Resolve names to IDs via GET_ALL_EMPLOYEES
- Terminated employees retain their IDs
Date Formats:
- Time-off dates: 'YYYY-MM-DD'
- Change detection: ISO 8601 with timezone
- Inconsistent formats between endpoints; check each endpoint's schema
Permissions:
- API key permissions determine accessible fields and operations
- Some operations require admin or manager-level access
- Time-off approvals require appropriate role permissions
Sensitive Data:
- Employee data includes PII (names, addresses, SSN, etc.)
- Handle all responses with appropriate security measures
- Dependent data is especially sensitive
Rate Limits:
- BambooHR API has rate limits per API key
- Bulk operations should be throttled
- GET_ALL_EMPLOYEES is more efficient than individual GET_EMPLOYEE calls
Response Parsing:
- Response data may be nested under
data key
- Employee fields vary based on
fields parameter
- Empty fields may be omitted or returned as null
- Parse defensively with fallbacks
Quick Reference
| Task |
Tool Slug |
Key Params |
| List all employees |
BAMBOOHR_GET_ALL_EMPLOYEES |
(none) |
| Get employee details |
BAMBOOHR_GET_EMPLOYEE |
id, fields |
| Track changes |
BAMBOOHR_EMPLOYEE_GET_CHANGED |
since, type |
| Time-off types |
BAMBOOHR_GET_META_TIME_OFF_TYPES |
(none) |
| Time-off balances |
BAMBOOHR_GET_TIME_OFF_BALANCES |
employeeId |
| List time-off requests |
BAMBOOHR_GET_TIME_OFF_REQUESTS |
start, end, employeeId |
| Create time-off request |
BAMBOOHR_CREATE_TIME_OFF_REQUEST |
employeeId, timeOffTypeId, start, end |
| Update time-off request |
BAMBOOHR_UPDATE_TIME_OFF_REQUEST |
requestId, status |
| Update employee |
BAMBOOHR_UPDATE_EMPLOYEE |
id, (field updates) |
| List dependents |
BAMBOOHR_DEPENDENTS_GET_ALL |
employeeId |
| Benefit coverages |
BAMBOOHR_BENEFIT_GET_COVERAGES |
(check schema) |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: bamboohr-automation3description: "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/bamboohr-automation10---1112# BambooHR Automation via Rube MCP1314Automate BambooHR human resources operations through Composio's BambooHR toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active BambooHR connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**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.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`293. If connection is not ACTIVE, follow the returned auth link to complete BambooHR authentication304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. List and Search Employees3536**When to use**: User wants to find employees or get the full employee directory3738**Tool sequence**:391. `BAMBOOHR_GET_ALL_EMPLOYEES` - Get the employee directory [Required]402. `BAMBOOHR_GET_EMPLOYEE` - Get detailed info for a specific employee [Optional]4142**Key parameters**:43- For GET_ALL_EMPLOYEES: No required parameters; returns directory44- For GET_EMPLOYEE:45 - `id`: Employee ID (numeric)46 - `fields`: Comma-separated list of fields to return (e.g., 'firstName,lastName,department,jobTitle')4748**Pitfalls**:49- Employee IDs are numeric integers50- GET_ALL_EMPLOYEES returns basic directory info; use GET_EMPLOYEE for full details51- The `fields` parameter controls which fields are returned; omitting it may return minimal data52- Common fields: firstName, lastName, department, division, jobTitle, workEmail, status53- Inactive/terminated employees may be included; check `status` field5455### 2. Track Employee Changes5657**When to use**: User wants to detect recent employee data changes for sync or auditing5859**Tool sequence**:601. `BAMBOOHR_EMPLOYEE_GET_CHANGED` - Get employees with recent changes [Required]6162**Key parameters**:63- `since`: ISO 8601 datetime string for change detection threshold64- `type`: Type of changes to check (e.g., 'inserted', 'updated', 'deleted')6566**Pitfalls**:67- `since` parameter is required; use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')68- Returns IDs of changed employees, not full employee data69- Must call GET_EMPLOYEE separately for each changed employee's details70- Useful for incremental sync workflows; cache the last sync timestamp7172### 3. Manage Time-Off7374**When to use**: User wants to view time-off balances, request time off, or manage requests7576**Tool sequence**:771. `BAMBOOHR_GET_META_TIME_OFF_TYPES` - List available time-off types [Prerequisite]782. `BAMBOOHR_GET_TIME_OFF_BALANCES` - Check current balances [Optional]793. `BAMBOOHR_GET_TIME_OFF_REQUESTS` - List existing requests [Optional]804. `BAMBOOHR_CREATE_TIME_OFF_REQUEST` - Submit a new request [Optional]815. `BAMBOOHR_UPDATE_TIME_OFF_REQUEST` - Modify or approve/deny a request [Optional]8283**Key parameters**:84- For balances: `employeeId`, time-off type ID85- For requests: `start`, `end` (date range), `employeeId`86- For creation:87 - `employeeId`: Employee to request for88 - `timeOffTypeId`: Type ID from GET_META_TIME_OFF_TYPES89 - `start`: Start date (YYYY-MM-DD)90 - `end`: End date (YYYY-MM-DD)91 - `amount`: Number of days/hours92 - `notes`: Optional notes for the request93- For update: `requestId`, `status` ('approved', 'denied', 'cancelled')9495**Pitfalls**:96- Time-off type IDs are numeric; resolve via GET_META_TIME_OFF_TYPES first97- Date format is 'YYYY-MM-DD' for start and end dates98- Balances may be in hours or days depending on company configuration99- Request status updates require appropriate permissions (manager/admin)100- Creating a request does NOT auto-approve it; separate approval step needed101102### 4. Update Employee Information103104**When to use**: User wants to modify employee profile data105106**Tool sequence**:1071. `BAMBOOHR_GET_EMPLOYEE` - Get current employee data [Prerequisite]1082. `BAMBOOHR_UPDATE_EMPLOYEE` - Update employee fields [Required]109110**Key parameters**:111- `id`: Employee ID (numeric, required)112- Field-value pairs for the fields to update (e.g., `department`, `jobTitle`, `workPhone`)113114**Pitfalls**:115- Only fields included in the request are updated; others remain unchanged116- Some fields are read-only and cannot be updated via API117- Field names must match BambooHR's expected field names exactly118- Updates are audited; changes appear in the employee's change history119- Verify current values with GET_EMPLOYEE before updating to avoid overwriting120121### 5. Manage Dependents and Benefits122123**When to use**: User wants to view employee dependents or benefit coverage124125**Tool sequence**:1261. `BAMBOOHR_DEPENDENTS_GET_ALL` - List all dependents [Required]1272. `BAMBOOHR_BENEFIT_GET_COVERAGES` - Get benefit coverage details [Optional]128129**Key parameters**:130- For dependents: Optional `employeeId` filter131- For benefits: Depends on schema; check RUBE_SEARCH_TOOLS for current parameters132133**Pitfalls**:134- Dependent data includes sensitive PII; handle with appropriate care135- Benefit coverages may include multiple plan types per employee136- Not all BambooHR plans include benefits administration; check account features137- Data access depends on API key permissions138139## Common Patterns140141### ID Resolution142143**Employee name -> Employee ID**:144```1451. Call BAMBOOHR_GET_ALL_EMPLOYEES1462. Find employee by name in directory results1473. Extract id (numeric) for detailed operations148```149150**Time-off type name -> Type ID**:151```1521. Call BAMBOOHR_GET_META_TIME_OFF_TYPES1532. Find type by name (e.g., 'Vacation', 'Sick Leave')1543. Extract id for time-off requests155```156157### Incremental Sync Pattern158159For keeping external systems in sync with BambooHR:160```1611. Store last_sync_timestamp1622. Call BAMBOOHR_EMPLOYEE_GET_CHANGED with since=last_sync_timestamp1633. For each changed employee ID, call BAMBOOHR_GET_EMPLOYEE1644. Process updates in external system1655. Update last_sync_timestamp166```167168### Time-Off Workflow169170```1711. GET_META_TIME_OFF_TYPES -> find type ID1722. GET_TIME_OFF_BALANCES -> verify available balance1733. CREATE_TIME_OFF_REQUEST -> submit request1744. UPDATE_TIME_OFF_REQUEST -> approve/deny (manager action)175```176177## Known Pitfalls178179**Employee IDs**:180- Always numeric integers181- Resolve names to IDs via GET_ALL_EMPLOYEES182- Terminated employees retain their IDs183184**Date Formats**:185- Time-off dates: 'YYYY-MM-DD'186- Change detection: ISO 8601 with timezone187- Inconsistent formats between endpoints; check each endpoint's schema188189**Permissions**:190- API key permissions determine accessible fields and operations191- Some operations require admin or manager-level access192- Time-off approvals require appropriate role permissions193194**Sensitive Data**:195- Employee data includes PII (names, addresses, SSN, etc.)196- Handle all responses with appropriate security measures197- Dependent data is especially sensitive198199**Rate Limits**:200- BambooHR API has rate limits per API key201- Bulk operations should be throttled202- GET_ALL_EMPLOYEES is more efficient than individual GET_EMPLOYEE calls203204**Response Parsing**:205- Response data may be nested under `data` key206- Employee fields vary based on `fields` parameter207- Empty fields may be omitted or returned as null208- Parse defensively with fallbacks209210## Quick Reference211212| Task | Tool Slug | Key Params |213|------|-----------|------------|214| List all employees | BAMBOOHR_GET_ALL_EMPLOYEES | (none) |215| Get employee details | BAMBOOHR_GET_EMPLOYEE | id, fields |216| Track changes | BAMBOOHR_EMPLOYEE_GET_CHANGED | since, type |217| Time-off types | BAMBOOHR_GET_META_TIME_OFF_TYPES | (none) |218| Time-off balances | BAMBOOHR_GET_TIME_OFF_BALANCES | employeeId |219| List time-off requests | BAMBOOHR_GET_TIME_OFF_REQUESTS | start, end, employeeId |220| Create time-off request | BAMBOOHR_CREATE_TIME_OFF_REQUEST | employeeId, timeOffTypeId, start, end |221| Update time-off request | BAMBOOHR_UPDATE_TIME_OFF_REQUEST | requestId, status |222| Update employee | BAMBOOHR_UPDATE_EMPLOYEE | id, (field updates) |223| List dependents | BAMBOOHR_DEPENDENTS_GET_ALL | employeeId |224| Benefit coverages | BAMBOOHR_BENEFIT_GET_COVERAGES | (check schema) |225226## When to Use227This skill is applicable to execute the workflow or actions described in the overview.