What is Wati automation using Rube MCP?

It automates Wati tasks by discovering current tool schemas with RUBE_SEARCH_TOOLS and executing them via RUBE_MULTI_EXECUTE_TOOL after confirming an ACTIVE Wati connection.

Do I need API keys to use Rube MCP for Wati?

No API keys are needed. Add the Rube MCP endpoint (e.g., https://rube.app/mcp) and establish the connection; ensure RUBE_SEARCH_TOOLS responds and the connection is ACTIVE.

What should I include in memory for tool execution?

Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty ({}), to satisfy the tool schema requirements.

wati-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Wati Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/wati

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Wati operations through Composio's Wati toolkit using Rube MCP. It emphasizes discovering tool schemas with RUBE_SEARCH_TOOLS before running workflows and ensuring active connections with RUBE_MANAGE_CONNECTIONS.

How This Skill Works

The workflow starts by discovering available Wati tools with RUBE_SEARCH_TOOLS. Next, it checks the connection status using RUBE_MANAGE_CONNECTIONS and ensures the toolkit is ACTIVE. Finally, it executes a discovered tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, memory, and session_id.

When to Use It

You need to automate a Wati operation that frequently changes tool schemas and slugs.
You must verify an ACTIVE Wati connection before running any workflows.
You want to avoid hardcoding tool slugs or arguments and rely on live schemas.
You are orchestrating a multi-step Wati workflow that reuses session IDs.
You need to run bulk Wati actions and manage tool execution via a centralized bench.

Quick Start

Step 1: Add Rube MCP as an MCP server and verify RUBE_SEARCH_TOOLS is available.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["wati"] and ensure the status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the live tool schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs.

Example Use Cases

Discover a Wati tool for sending a message, confirm an ACTIVE connection, and execute the message with proper arguments.
List Wati contacts via a discovered tool, then bulk update fields using the returned schema.
Run a multi-step Wati workflow that reuses a session_id to process a sequence of actions.
Handle pagination tokens when listing Wati resources through an discovered tool, continuing until complete.
Perform bulk Wati operations using RUBE_REMOTE_WORKBENCH and run_composio_tool() for efficiency.

Frequently Asked Questions

Add this skill to your agents