--- name: bamboohr-automation-a4f2d40321b8 description: "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27" --- # 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. `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**: 1. `BAMBOOHR_DEPENDENTS_GET_ALL` - List all dependents [Required] 2. `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. --- ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Cache workflow configurations and automation patterns. Retrieve prior pipeline designs to avoid re-building similar flows from scratch. ```bash # Check for prior workflow/automation context before starting python3 execution/memory_manager.py auto --query "automation patterns and workflow configurations for Bamboohr Automation" ``` ### Storing Results After completing work, store workflow/automation decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "Workflow: automated data pipeline with retry logic, dead-letter queue, and Slack alerts on failure" \ --type technical --project \ --tags bamboohr-automation workflow ``` ### Multi-Agent Collaboration Share workflow state with other agents so they can trigger, monitor, or extend the automation. ```bash python3 execution/cross_agent_context.py store \ --agent "" \ --action "Workflow automation deployed — pipeline processing 1000+ events/day with 99.9% success rate" \ --project ``` ### Playbook Engine Combine this skill with others using the Playbook Engine (`execution/workflow_engine.py`) for guided multi-step automation with progress tracking. --- Source attribution: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/bamboohr-automation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024-2026 Elton Machado (TechWaveDev) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/bamboohr-automation/SKILL.md Attribution basis: Source repository record Fields of work: Human Resources, Sales Roles: Customer Success Manager, HR Generalist, People Operations Specialties: API, Backend, Design, DevOps, Frontend, Git Tools: BambooHR, Rube Mcp Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: aca139f6950759795c7149ba3f9a6076eecab2521483b0b0432e8769640e9b9b