Chmeetings Automation

What This Skill Does

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

When to Use

• Schedule a new meeting in Chmeetings.
• Update an existing meeting's details.
• Retrieve meeting attendance information.
• Send meeting reminders.
• Cancel a scheduled meeting.
• Integrate Chmeetings with other calendar systems.

Key Features

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

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedChmeetings Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/chmeetings

Prerequisites

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

Step 2: Check Connection

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

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

Toolkit docs: composio.dev/toolkits/chmeetings

Prerequisites

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

Step 2: Check Connection

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