What is Rube MCP and how does it relate to Lodgify automation?

Rube MCP acts as the middleware control plane to discover Lodgify tool schemas, manage connections, and execute tools via the multi-tool API, enabling automated Lodgify workflows.

How do I ensure tool schemas are current?

Always run RUBE_SEARCH_TOOLS first to fetch current slugs and schemas; never hardcode slugs or arguments.

What should I do if the Lodgify connection is not ACTIVE?

Follow the returned auth link from RUBE_MANAGE_CONNECTIONS to complete setup, then re-check status until ACTIVE before running workflows.

lodgify-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/lodgify-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Lodgify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lodgify

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["lodgify"]
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 Lodgify-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `lodgify`
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/lodgify-automation/SKILL.mdView on GitHub

Overview

Automates Lodgify operations through Composio's Lodgify toolkit via Rube MCP. Always start by discovering the current tool schemas with RUBE_SEARCH_TOOLS, then verify an ACTIVE Lodgify connection before executing workflows.

How This Skill Works

Connect Rube MCP to Lodgify, fetch tool schemas with RUBE_SEARCH_TOOLS, and confirm the connection with RUBE_MANAGE_CONNECTIONS. Then run tool executions using RUBE_MULTI_EXECUTE_TOOL, supplying discovered tool slugs and memory payloads as per the schemas.

When to Use It

Automate recurring Lodgify listings and availability pulls by discovering tools first
Create or update Lodgify bookings from external workflows after validating the active connection
Run bulk tooling across multiple listings while keeping session state and memory intact
Validate and adapt to updated tool schemas by re-searching tools before changes
Reuse a session ID within a workflow to chain steps and later start a new workflow with a fresh session

Quick Start

Step 1: Add the Lodgify Rube MCP endpoint and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["lodgify"] and confirm ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory payload

Best Practices

Always call RUBE_SEARCH_TOOLS before any tool execution to get current slugs and schemas
Ensure the Lodgify toolkit connection is ACTIVE via RUBE_MANAGE_CONNECTIONS
Use exact field names and types from the tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls—even if empty
Reuse session IDs within a workflow and paginate responses until complete

Example Use Cases

Sync new Lodgify listings from a CRM to keep availability up to date
Create a Lodgify booking when a lead converts in your CRM
Update pricing or availability after a reservation is confirmed
Bulk fetch tool schemas and validate them before a large rollout
Audit tool results for missing fields using RUBE_GET_TOOL_SCHEMAS

Frequently Asked Questions

Add this skill to your agents