What is required to use whautomate-automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and a Whautomate connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS. Always search tools first to get current schemas.

How do I run a Whautomate task safely?

Discover the tool with RUBE_SEARCH_TOOLS, verify the ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute with RUBE_MULTI_EXECUTE_TOOL, including memory and a valid session_id.

Why do I need to search tools first?

Tool schemas change frequently. Searching first ensures you use current slugs and argument names, preventing execution errors from stale or hardcoded values.

whautomate-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Whautomate Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/whautomate

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Whautomate operations through Composio's Whautomate toolkit via Rube MCP. The process hinges on discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to avoid hardcoding slugs or arguments.

How This Skill Works

The workflow starts by discovering available Whautomate tools with RUBE_SEARCH_TOOLS, then establishes or validates a connection using RUBE_MANAGE_CONNECTIONS. Tools are executed through RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, with a memory payload and an active session_id as described in the core workflow pattern.

When to Use It

When you need to automate a Whautomate task and tool schemas may change.
When you must verify that Rube MCP is connected and the toolkit is ACTIVE before running workflows.
When you want to discover available tools for a specific Whautomate use case.
When executing a specific tool requires arguments derived from the latest tool schemas.
When reusing a session across related workflows to maintain context.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Discover tools for your Whautomate use case with RUBE_SEARCH_TOOLS and note tool_slugs and schemas.
Step 3: Establish/verify the connection with RUBE_MANAGE_CONNECTIONS, then execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL using memory and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before attempting any execution to fetch current slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before tool execution.
Use exact field names and types from the search results to ensure schema compliance.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for separate runs to avoid context leakage.

Example Use Cases

Automate a weekly Whautomate data pull by discovering the appropriate tool slug, verifying the connection, and executing with the required arguments and memory.
Perform a bulk run of multiple Whautomate steps in a single session using RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs.
Debug a failing automation by re-discovering tool schemas, updating the tool slug, and re-running with the correct arguments.
Switch to a new Whautomate task by discovering its schema, then executing the tool with the exact field names from the search results.
Maintain context across related tasks by reusing an existing session_id while performing consecutive tool executions.

Frequently Asked Questions

Add this skill to your agents