Elorus Automation

What This Skill Does

This skill automates operations within Elorus using the Composio's Elorus toolkit via Rube MCP. It's designed for users who want to streamline their project management or invoicing tasks programmatically. The skill requires an active Elorus connection and familiarity with Rube MCP.

When to Use

Automate invoice creation. Programmatically manage clients. Create custom project workflows. Schedule and execute billing tasks. Monitor project expenses. Integrate Elorus with other systems.

Key Features

Uses Rube MCP for tool discovery and execution. Requires an active Elorus connection. Provides access to the Elorus toolkit. Employs RUBE_SEARCH_TOOLS for dynamic schema retrieval. Supports session management for workflow continuity.

Manual Installation

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

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: {}

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

Powered by Composio