PromptShop

Maintainx Automation

Automate maintenance operations and asset management in Maintainx via Rube MCP.

Install

npx promptshop add maintainx-automation

Details

What This Skill Does

  • The Maintainx Automation skill allows users to automate operations within Maintainx through Composio's Rube MCP integration.
  • It is designed for operations and maintenance teams who want to programmatically manage their Maintainx account.
  • The skill requires an active Maintainx connection via Rube MCP.

When to Use

  • Discover available Maintainx tools.
  • Check the status of the Maintainx connection.
  • Execute specific Maintainx tools.
  • Automate work order creation.
  • Manage asset maintenance schedules.
  • Retrieve maintenance data.

Key Features

  • Uses Rube MCP for Maintainx integration.
  • Requires active Maintainx connection.
  • Uses RUBE_SEARCH_TOOLS to discover available tools.
  • Uses RUBE_MANAGE_CONNECTIONS to check connection status.
  • Uses RUBE_MULTI_EXECUTE_TOOL to execute tools.
  • Tool schemas are dynamically retrieved.

Manual Installation

Maintainx Automation via Rube MCP

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Maintainx-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit maintainx
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef