Storeganise Automation

What This Skill Does

This skill automates Storeganise operations using the Composio Storeganise toolkit via Rube MCP. It's designed for users who need to manage self-storage facilities and customer interactions through Storeganise. The skill ensures proper setup, tool discovery, and execution while adhering to Storeganise's schema requirements.

When to Use

• Automate customer onboarding processes.
• Manage and update unit availability.
• Trigger payment reminders and notifications.
• Schedule recurring billing cycles.
• Verify Storeganise connection status.
• Discover available Storeganise tools.

Key Features

• Automates Storeganise operations via Rube MCP.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Manages connections using RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides setup instructions and prerequisites.
• Highlights common pitfalls and how to avoid them.

Manual Installation

Storeganise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/storeganise

Prerequisites

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

Step 2: Check Connection

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