Helpwise Automation

What This Skill Does

The Helpwise Automation skill allows users to automate operations within the Helpwise platform through Composio's Rube MCP. It is designed for customer support teams who use Helpwise for managing customer inquiries and want to streamline their workflows. The skill requires an active Helpwise connection and leverages Rube MCP for tool discovery and execution.

When to Use

Discover available Helpwise tools via Rube MCP.Check the connection status to the Helpwise toolkit. Execute a specific Helpwise tool with schema-compliant arguments. Automate creating new tickets in Helpwise. Update ticket information in Helpwise. Search for specific tools based on use case.

Key Features

Uses Rube MCP for tool discovery and execution. Requires active Helpwise connection via Rube MCP.Employs RUBE_SEARCH_TOOLS to find available tools. Uses RUBE_MANAGE_CONNECTIONS to check connection status. Executes tools using RUBE_MULTI_EXECUTE_TOOL.Provides a structured workflow pattern for automation.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedHelpwise 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

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