Do I need API keys to use this skill?

No API keys are required. Add the Rube MCP endpoint (https://rube.app/mcp) as your MCP server; then the toolkit handles authentication.

What is the first step in a Route4me automation workflow?

Always call RUBE_SEARCH_TOOLS to obtain the current tool schemas before selecting and executing any tool.

How do I ensure safe execution of Route4me tools?

Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools and include memory in RUBE_MULTI_EXECUTE_TOOL calls; use exact schema fields from search results.

route4me-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Route4me Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/route4me

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill lets you automate Route4me operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first and ensuring an ACTIVE connection before executing any workflow. By following the toolbox steps, you can reliably run Route4me tasks with schema-compliant inputs.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch current Route4me tool slugs and input schemas. Next, RUBE_MANAGE_CONNECTIONS ensures the toolkit connection is ACTIVE for route4me. Finally, RUBE_MULTI_EXECUTE_TOOL runs the selected tool with memory and session context, using the exact schema fields returned by the search.

When to Use It

When you need to automate a Route4me operation from a CRM or other data source using up-to-date tool schemas.
When tool schemas change and hardcoding slugs or parameters would break automation.
When establishing or verifying a Route4me connection before running routes or optimizations.
When performing multiple Route4me actions in a single workflow requiring session reuse.
When performing bulk Route4me tasks via tools discovered from RUBE_SEARCH_TOOLS and validated against the latest schemas.

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS is available and fetch Route4me tool slugs.
Step 2: Establish and verify an ACTIVE Route4me connection with RUBE_MANAGE_CONNECTIONS.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the schema-compliant arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and fetch new ones only for new workflows.

Example Use Cases

Create Route4me routes from a CRM lead list by discovering the create-route tool and executing with mapped fields.
Update the status of a Route4me route after a completion trigger by reusing a session in a single workflow.
Run a Route4me optimization by discovering the appropriate tool slug and supplying required inputs from a data source.
Establish a Route4me connection via RUBE_MANAGE_CONNECTIONS and verify ACTIVE before operations.
Fetch tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before running a workflow.

Frequently Asked Questions

Add this skill to your agents