What prerequisites are required?

Rube MCP must be connected and RUBE_SEARCH_TOOLS available; an active Helpwise connection via RUBE_MANAGE_CONNECTIONS with toolkit 'helpwise' is required; always search tools first.

How do I discover available Helpwise tools?

Run RUBE_SEARCH_TOOLS with queries for the Helpwise use_case and review the returned tool slugs, input schemas, and execution plans.

What should I do before executing a tool?

Ensure the Helpwise connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, confirm tool schemas from RUBE_SEARCH_TOOLS, and include a memory payload in RUBE_MULTI_EXECUTE_TOOL.

helpwise-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Helpwise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/helpwise

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Helpwise operations through Composio's Rube MCP toolkit. This approach emphasizes discovering current tool schemas before execution to adapt to updates and avoid hard-coded slugs.

How This Skill Works

Discover available Helpwise tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Then verify an active connection with RUBE_MANAGE_CONNECTIONS for the helpwise toolkit, and finally run tools using RUBE_MULTI_EXECUTE_TOOL with compliant arguments and a memory payload. Always reuse a session_id when appropriate and include memory in every tool call.

When to Use It

When you need to automate a Helpwise workflow and want the latest tool schemas
When setting up a new Helpwise integration and confirming the connection is ACTIVE
When performing a sequence of Helpwise tasks that requires discovery before execution
When debugging automation failures caused by schema changes or inactive connections
When automating repeated Helpwise tasks and reusing session IDs for continuity

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) to your client
Step 2: Verify RUBE_SEARCH_TOOLS and connect with RUBE_MANAGE_CONNECTIONS using toolkits: ["helpwise"]
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and compliant arguments

Best Practices

Always call RUBE_SEARCH_TOOLS before execution to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use the exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow or generate new ones for independent runs

Example Use Cases

Discover a Helpwise tool to create a new ticket and execute with required fields
Query tickets due this week, then update statuses via the matched tool
Perform a bulk close operation using a tool that supports batch processing
Sync ticket notes to a separate memory store after tool execution
Test a new Helpwise workflow by running a dry-run with an existing session

Frequently Asked Questions

Add this skill to your agents