apaleo-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/apaleo-automation --openclawApaleo Automation via Rube MCP
Automate Apaleo operations through Composio's Apaleo toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/apaleo
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Apaleo connection via
RUBE_MANAGE_CONNECTIONSwith toolkitapaleo - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitapaleo - 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: "Apaleo 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 Apaleo task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["apaleo"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Apaleo-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit apaleo |
| 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 schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/apaleo-automation/SKILL.mdView on GitHub Overview
Automate Apaleo operations via Composio's Apaleo toolkit using Rube MCP. The workflow always fetches current tool schemas before execution to avoid mismatches. Prerequisites include a connected Rube MCP and an active Apaleo connection via the toolkit apaleo.
How This Skill Works
Begin by querying RUBE_SEARCH_TOOLS to retrieve current tool slugs and schemas for Apaleo tasks. Validate the connection state with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload, and reuse sessions for related steps.
When to Use It
- When you need to automate a specific Apaleo task and want the latest tool schemas first.
- When coordinating a multi-step Apaleo workflow that requires tool discovery, connection checks, and execution.
- When setting up nightly or scheduled Apaleo operations to prevent stale tool configurations.
- When performing bulk operations that may require pagination and updated tool inputs.
- When debugging tool schemas changes and avoiding hard-coded slugs.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with queries for Apaleo operations
- Step 2: RUBE_MANAGE_CONNECTIONS for toolkit apaleo and verify ACTIVE
- Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory: {}
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the search results.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and avoid creating new ones for every step.
Example Use Cases
- Automate a new booking creation by discovering the appropriate tool and executing it with the correct inputs.
- Sync room availability by discovering the latest tool and running it with updated data.
- Bulk-import reservations across properties, handling pagination tokens returned by the search.
- Validate and refresh Apaleo connections before nightly data sync tasks.
- Run a sequential tool set to complete a check-in workflow from discovery to execution.
