$ loading_
Discover and run Whautomate automations through Rube MCP.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "whautomate-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/whautomate-automation/SKILL.md 2. Save it as ~/.claude/skills/whautomate-automation/SKILL.md 3. Reload skills and tell me it's ready
First call RUBE_SEARCH_TOOLS to find currently available tools for "Whautomate operations", including input schemas, recommended execution plans, and pitfalls, and generate a session for this workflow.
A list of available Whautomate tools, their parameter schemas, and guidance for the next execution steps.
Using the current session, call RUBE_MANAGE_CONNECTIONS to check the connection status for the whautomate toolkit; if it is not ACTIVE, tell me how to complete authorization.
The Whautomate connection status, and if inactive, an auth link or activation guidance.
First search for tools related to "my specific Whautomate task", then select the correct tool slug based on the latest returned schema and execute it with RUBE_MULTI_EXECUTE_TOOL; make sure to include memory: {}.A Whautomate action executed using the latest tool definition, returning results or pagination continuation details.
Developers or automation maintainers can search for current tools and schemas before running a Whautomate workflow to avoid failures caused by changed fields. This is useful for reliable, repeatable automation.
When a Whautomate action cannot run, users can first check the whautomate connection status in Rube MCP and complete activation through the returned auth link. This helps rule out connection readiness issues.
Users can complete tool discovery, connection checking, and execution within the same session to form a full Whautomate automation flow. Reusing the session also helps keep context consistent across multiple steps.
The documentation explains how to automate Whautomate operations through Composio's toolkit via Rube MCP. It covers prerequisites, connection setup, tool discovery, and the recommended execution pattern. A key requirement is to always call `RUBE_SEARCH_TOOLS` first to get current schemas, then verify the `whautomate` connection is ACTIVE, and finally execute with `RUBE_MULTI_EXECUTE_TOOL`, while handling session reuse, the required `memory` field, and pagination.
Automate Whautomate operations through Composio's Whautomate toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/whautomate
RUBE_MANAGE_CONNECTIONS with toolkit whautomateRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit whautomateAlways 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.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Whautomate task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["whautomate"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| 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
It uses Rube MCP to access Composio's Whautomate toolkit for discovering and executing Whautomate-related operations. The docs emphasize searching tools first and then executing with the latest schema.
You need Rube MCP connected first and `RUBE_SEARCH_TOOLS` available. You also need an active connection for the `whautomate` toolkit through `RUBE_MANAGE_CONNECTIONS`.
The docs say you can add `https://rube.app/mcp` as an MCP server and no API key is needed. For Whautomate-side authorization details, follow the information returned during the connection flow.
Automate Stormglass IO weather data queries and integrations through Rube MCP.
Automate OCRSpace text extraction tasks through Rube MCP workflows.
Automate GoToWebinar creation, registration, and attendee management through Rube MCP.
Automate Logo development tasks via Rube MCP using current tool schemas.
Automate Globalping network probes and collect results through Rube MCP.
Automate Mailcoach email marketing and subscriber workflows through Rube MCP.
Automate Autom workflows via Rube MCP while checking current tool schemas first.
Automate Wit AI workflows via Rube MCP using current tool schemas first.
Automate V0 workflows via Rube MCP using current tool schemas first.
Automate Wati messaging and customer communication tasks through Rube MCP.
Automate Botpress tasks and workflow actions through Rube MCP.
Automate AI/ML API workflows via Rube MCP, checking latest tool schemas first.