Talenthr Automation
automates operations within the Talenthr human resources platform using Composio's Talenthr toolkit via Rube MCP.
Install
npx promptshop add talenthr-automationDetails
What This Skill Does
This skill automates operations within the Talenthr human resources platform using Composio's Talenthr toolkit via Rube MCP. It's designed for users who need to streamline HR-related tasks such as managing employee data, processing payroll, and tracking time off. The skill ensures that all operations are performed with the most up-to-date tool schemas.
When to Use
Manage employee profiles Process payroll calculations Track employee time off Generate HR reports Automate employee onboarding Sync HR data with other systems
Key Features
- Automates Talenthr tasks via Rube MCP.
- Uses Composio's Talenthr toolkit.
- Requires active Talenthr connection.
- Discovers tools using RUBE_SEARCH_TOOLS.
- Checks connection status via RUBE_MANAGE_CONNECTIONS.
- Executes tools using RUBE_MULTI_EXECUTE_TOOL.
Automate Talenthr operations through Composio's Talenthr toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/talenthr
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Talenthr connection via RUBE_MANAGE_CONNECTIONS with toolkit talenthr 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 talenthr If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows: RUBE_SEARCH_TOOLS queries: [{use_case: "Talenthr operations", known_fields: ""}] session: {generate_id: true} This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Talenthr task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["talenthr"] session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"
Known Pitfalls
Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Talenthr-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit talenthr |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schema Ref |