Do I need API keys to use Loyverse automation?

No. The setup uses Rube MCP at https://rube.app/mcp and the Loyverse toolkit; no API keys are required.

How do I ensure tool schemas stay up to date?

Always call RUBE_SEARCH_TOOLS before executing workflows to retrieve current tool slugs and input schemas.

What if my Loyverse connection is not ACTIVE?

Follow the returned auth link to complete setup, then re-check with RUBE_MANAGE_CONNECTIONS until statusACTIVE before running workflows.

loyverse-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Loyverse Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/loyverse

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Loyverse operations using Composio's Loyverse toolkit via Rube MCP. Tools’ schemas are fetched first with RUBE_SEARCH_TOOLS to stay current, then executed through structured workflows. Requires a connected Rube MCP and an active Loyverse connection.

How This Skill Works

Discover available Loyverse tools with RUBE_SEARCH_TOOLS, then verify the Loyverse connection with RUBE_MANAGE_CONNECTIONS. Finally run tools with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool slug and memory payload; always use the exact field names from the tool schema and include memory even if empty.

When to Use It

When you need to automate Loyverse operations without manual steps and keep tool schemas current by discovering them first
When establishing or validating an active Loyverse connection before running workflows
When performing a sequence of tools in a single workflow using a session ID
When handling bulk actions via RUBE_REMOTE_WORKBENCH or executing multiple tools in one go
When validating tool inputs against current schemas to prevent hardcoding slugs or arguments

Quick Start

Step 1: Add the Rube MCP endpoint https://rube.app/mcp as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS with use_case: Loyverse operations to fetch current tool schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit loyverse and execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use the exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS
Include a memory payload in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and avoid creating new ones unnecessarily

Example Use Cases

Automate daily Loyverse inventory sync using discovered tools and a persistent session
Update Loyverse product prices automatically when inventory data changes
Generate daily sales reports by orchestrating multiple Loyverse tools in sequence
Bulk update Loyverse catalogs from an external data source via RUBE_REMOTE_WORKBENCH
End-of-day reconciliation workflow that validates connection status and executes cleanup tools

Frequently Asked Questions

Add this skill to your agents