What is maintainx-automation?

An automation workflow that uses Rube MCP and Composio to run Maintainx tasks, always discovering current tool schemas first.

Do I need API keys or keys to connect?

No API keys are required; add the MCP server https://rube.app/mcp and follow the setup steps to activate the Maintainx toolkit.

How do I handle changes in tool schemas?

Always run RUBE_SEARCH_TOOLS to get up-to-date tool slugs and input schemas before executing any workflow.

maintainx-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Maintainx Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/maintainx

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Maintainx operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first (RUBE_SEARCH_TOOLS) to avoid hardcoding slugs or arguments.

How This Skill Works

The skill first discovers available Maintainx tools via RUBE_SEARCH_TOOLS, then checks the connection status with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments. It always includes a memory payload and reuses session IDs for continuity.

When to Use It

When you need repeatable Maintainx workflows (e.g., creating or updating work orders) to save time
When tool schemas or slugs change and you must fetch current schemas before running
When you want to verify an ACTIVE Rube MCP connection before executing tools
When performing bulk or parallel Maintainx actions via RUBE_MULTI_EXECUTE_TOOL
When automating recurrent maintenance operations based on a defined use case

Quick Start

Step 1: Add Maintainx MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'maintainx' and ensure ACTIVE
Step 3: Discover tools and run them with RUBE_MULTI_EXECUTE_TOOL using the discovered slugs and memory parameter

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to tool execution
Use exact field names and types from search results; avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; generate new ones only for new workflows

Example Use Cases

Automatically open a maintenance work order when a sensor triggers a fault in Maintainx
Fetch current tool schemas and bulk-update asset maintenance statuses accordingly
Create or update maintenance tasks using a defined use_case slug from RUBE_SEARCH_TOOLS
Run a safety-check workflow after establishing an ACTIVE Maintainx connection
Execute multiple maintenance actions in parallel using RUBE_MULTI_EXECUTE_TOOL

Frequently Asked Questions

Add this skill to your agents