Do I need API keys to use Elorus automation?

No API keys are required; add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and rely on the toolkit's authenticated session.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch current schemas before executing any tool. Do not hardcode slugs or arguments.

How do I handle pagination or repeated runs?

Check for pagination tokens in responses and continue fetching until complete. Reuse session IDs within a workflow and ensure memory is included in multi-execute calls.

elorus-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Elorus Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/elorus

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Elorus operations via Composio's Elorus toolkit using the Rube MCP bridge. The workflow relies on discovering current tool schemas first, then establishing an ACTIVE connection, and finally executing tools with a memory payload. This approach keeps automation aligned with up-to-date tool schemas and safer execution.

How This Skill Works

Start by discovering available Elorus tools with RUBE_SEARCH_TOOLS to obtain current schemas. Then verify the connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, always including a memory block. Use exact field names and types from the tool schemas and reuse sessions when appropriate.

When to Use It

Automate recurring Elorus tasks (invoicing, reminders) with up-to-date tool schemas.
Integrate Elorus with other apps via Composio without hardcoding tool slugs.
Set up one-click workflows that require ACTIVE Elorus connections.
Execute bulk operations by discovering tools first and then running multiple tools in sequence.
Diagnose and fix schema changes quickly by re-discovering tools before runs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify connectivity with RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS for the elorus toolkit and complete the auth flow if needed.
Step 3: Use RUBE_SEARCH_TOOLS to select a tool_slug, then run it with RUBE_MULTI_EXECUTE_TOOL, including memory and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any run to get current tool slugs and schemas.
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use the exact field names and types from the search results; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.
Reuse session IDs within a workflow and handle pagination tokens when needed.

Example Use Cases

Create an Elorus invoice automatically when a new order is placed in an e-commerce system.
Sync new or updated client data from a CRM to Elorus.
Bulk-create invoices from a CSV feed using discovered tool schemas.
Record Elorus payments and reflect them in an ERP or accounting system.
Send automated overdue invoice reminders using Elorus tools.

Frequently Asked Questions

Add this skill to your agents