clickmeeting-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/clickmeeting-automation --openclawClickmeeting Automation via Rube MCP
Automate Clickmeeting operations through Composio's Clickmeeting toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/clickmeeting
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Clickmeeting connection via
RUBE_MANAGE_CONNECTIONSwith toolkitclickmeeting - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitclickmeeting - 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: "Clickmeeting 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 Clickmeeting task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["clickmeeting"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Clickmeeting-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit clickmeeting |
| 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/clickmeeting-automation/SKILL.mdView on GitHub Overview
This skill automates Clickmeeting operations using Composio's toolkit and the Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an authenticated Clickmeeting connection via RUBE_MANAGE_CONNECTIONS, and executing actions through RUBE_MULTI_EXECUTE_TOOL. Always fetch up-to-date schemas before running workflows to avoid broken slugs or fields.
How This Skill Works
First, discover available Clickmeeting tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Next, verify and establish the Clickmeeting connection using RUBE_MANAGE_CONNECTIONS, ensuring the toolkit is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory (even if empty) and reusing a session ID to maintain workflow continuity.
When to Use It
- Automating routine Clickmeeting tasks like scheduling rooms, inviting participants, or starting sessions.
- When tool schemas change and you need the latest slugs and fields before automation.
- Batching multiple Clickmeeting actions in a single workflow using RUBE_MULTI_EXECUTE_TOOL.
- Ensuring the Clickmeeting connection is ACTIVE before proceeding with executions.
- Reusing session IDs to maintain context across steps in a workflow.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Verify RUBE_SEARCH_TOOLS responds and connect with RUBE_MANAGE_CONNECTIONS for the clickmeeting toolkit; ensure status is ACTIVE.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas.
- Check that the Clickmeeting connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
- Follow exact field names and types from the search results to ensure schema compliance.
- Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for separate workflows; monitor pagination when listing tools or results.
Example Use Cases
- Discover a 'CreateMeeting' tool via RUBE_SEARCH_TOOLS and run it to schedule a new Clickmeeting session with attendees.
- Use an 'UpdateMeetingDetails' tool discovered from RUBE_SEARCH_TOOLS to modify a scheduled room's settings.
- Validate the Clickmeeting connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then fetch upcoming meetings using a discovered tool.
- Execute multiple actions in one run by listing tools and invoking several TOOL_SLUGs with RUBE_MULTI_EXECUTE_TOOL in a single workflow, sharing memory between steps.
- If tool schemas change, refresh your workflow by re-running RUBE_SEARCH_TOOLS to obtain new slugs and input schemas.
