Recruitee Automation

What This Skill Does

• This skill automates operations within Recruitee using Composio's Recruitee toolkit through Rube MCP.
• It is designed for users who want to streamline their recruiting processes by programmatically interacting with Recruitee.
• The skill handles setup, tool discovery, and execution, ensuring schema compliance.

When to Use

• Automate candidate profile creation.
• Manage job postings programmatically.
• Trigger interview scheduling.
• Update candidate statuses automatically.
• Extract recruiting data for analysis.
• Integrate Recruitee with other HR systems.

Key Features

• Uses Rube MCP for Recruitee automation.
• Requires active Recruitee connection.
• Discovers tools using RUBE_SEARCH_TOOLS.
• Checks connection status via RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Ensures schema compliance for arguments.

Manual Installation

Recruitee Automation via Rube MCP

Automate Recruitee operations through Composio's Recruitee toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/recruitee

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Recruitee connection via RUBE_MANAGE_CONNECTIONS with toolkit recruitee 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 recruitee 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: "Recruitee 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 Recruitee task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["recruitee"] 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