Do I need API keys to use this skill?

No API keys are required; you add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and authenticate through the provided flow.

How do I know which tool slug to call?

Run RUBE_SEARCH_TOOLS with a Servicem8 use case to retrieve tool slugs, input schemas, and execution plans; never hardcode slugs.

What must I include when executing a tool?

Pass exact field names and types from the search results, include memory (even if empty), and reuse a valid session_id within the workflow.

servicem8-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Servicem8 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/servicem8

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Servicem8 operations through Composio's toolkit via Rube MCP. Always search tools first to fetch current tool schemas and ensure you’re running up-to-date workflows. This skill orchestrates discovery, connection validation, and execution with strict schema adherence.

How This Skill Works

It starts by querying current tool schemas using RUBE_SEARCH_TOOLS with a Servicem8 use_case. It then validates the Servicem8 connection with RUBE_MANAGE_CONNECTIONS and ensures ACTIVE status. Finally, it executes the selected tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, memory, and session_id.

When to Use It

When you need to automate a standard Servicem8 task by discovering and running a tool slug from the current schemas.
When tool schemas may have changed and you must fetch the latest definitions before execution.
When integrating Servicem8 tasks into larger Composio workflows that require session management.
When verifying a Servicem8 connection is ACTIVE before running any workflow steps.
When reusing a session ID within a multi-step Servicem8 automation workflow.

Quick Start

Step 1: Ensure Rube MCP is connected and run RUBE_SEARCH_TOOLS to fetch current Servicem8 tool schemas.
Step 2: Find a tool for your task (use_case: Servicem8 operations) and start a session.
Step 3: Check the connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify the Servicem8 connection via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE before executing tools.
Use exact field names and types from search results; do not hardcode slugs or arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens if present.

Example Use Cases

Example 1: Discover a 'create_job' tool slug from the Servicem8 use_case and execute it with customer_id and job_description derived from a CRM input.
Example 2: Update a Servicem8 Job status by calling 'update_job_status' with job_id and new status.
Example 3: Retrieve details for a specific job via 'get_job_details' and store the results in memory for display or further steps.
Example 4: List open Servicem8 jobs using 'list_open_jobs' and feed the results into a dashboard widget.
Example 5: Bulk create multiple Servicem8 jobs by discovering 'bulk_create_jobs' and supplying an array of records, capturing results in memory.

Frequently Asked Questions

Add this skill to your agents