home / skills / composiohq / awesome-claude-skills / whautomate-automation

whautomate-automation skill

safe

/whautomate-automation

This skill automates Whautomate tasks via Rube MCP by discovering current tool schemas first and executing validated workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill whautomate-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: whautomate-automation
description: "Automate Whautomate tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Whautomate Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/whautomate](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `whautomate`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Whautomate operations through Rube MCP (Composio) to run and orchestrate Whautomate toolkit tasks programmatically. It provides a clear workflow pattern for discovering tools, validating connections, and executing multi-step operations while enforcing schema compliance. The goal is reliable, repeatable automation of Whautomate flows within Rube MCP sessions.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to discover available Whautomate tools and their current schemas, recommended execution plans, and pitfalls. It then verifies or establishes the Whautomate connection via RUBE_MANAGE_CONNECTIONS and runs tools with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always supplying schema-compliant arguments, memory, and session IDs. It also supports fetching full tool schemas with RUBE_GET_TOOL_SCHEMAS and handling pagination for large responses.

When to use it

Automating repeatable Whautomate tasks across accounts or campaigns
Running multi-step composio workflows that require current tool schemas
Bulk operations where reliable schema discovery and session reuse matter
When integrating Whautomate into larger agent-based automation pipelines
Before any tool execution to avoid broken calls due to schema changes

Best practices

Always call RUBE_SEARCH_TOOLS first—do not hardcode tool slugs or argument shapes
Verify connection status via RUBE_MANAGE_CONNECTIONS and complete auth if not ACTIVE
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session_id within the same workflow; create new ones for distinct workflows
Check responses for pagination tokens and iterate until you have all results
Use RUBE_GET_TOOL_SCHEMAS for tools that return schemaRef before constructing complex payloads

Example use cases

Discover available Whautomate actions for scheduling and dispatching tasks, then execute them in sequence
Authenticate and confirm an active Whautomate connection, then run a bulk campaign using RUBE_REMOTE_WORKBENCH
Fetch a tool's full schema with RUBE_GET_TOOL_SCHEMAS before building a complex data payload
Run a set of composio tools with RUBE_MULTI_EXECUTE_TOOL, capturing state in memory and reusing session IDs for transactional consistency

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; the MCP endpoint works without API keys for this workflow.

What if a tool schema changed since my last run?

Always call RUBE_SEARCH_TOOLS before executing. That returns current schemas and recommended plans so you can adapt arguments to match the latest fields.