Chatwork Automation

What This Skill Does

• This skill automates Chatwork operations via the Composio Chatwork toolkit through Rube MCP.
• It allows users to discover available tools, check connections, and execute tools within the Chatwork environment.
• This is useful for developers and automation engineers looking to streamline Chatwork workflows.

When to Use

• Send a message to a Chatwork room.
• Create a new Chatwork room.
• Add a user to a Chatwork room.
• Retrieve Chatwork message history.
• Search for messages in Chatwork.
• Automate Chatwork notifications.

Key Features

• Discovers available Chatwork tools via Rube MCP.
• Checks Chatwork connection status.
• Executes Chatwork tools with schema validation.
• Provides setup instructions for Rube MCP and Chatwork.
• Offers a core workflow pattern for tool execution.
• Highlights common pitfalls and how to avoid them.

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• Chatwork Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/chatwork

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["chatwork"] 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

• Powered by Composio
• Chatwork Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/chatwork

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Chatwork connection via RUBE_MANAGE_CONNECTIONS with toolkit chatwork Always call RUBE_SEARCH_TOOLS first to get current tool schemas

• 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 chatwork If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Chatwork 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 Chatwork task"}] session: {id: "existing_session_id"}

RUBE_MANAGE_CONNECTIONS toolkits: ["chatwork"] 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"

• 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

Powered by Composio