home / skills / composiohq / awesome-claude-skills / clickmeeting-automation

clickmeeting-automation skill

safe

/clickmeeting-automation

This skill automates Clickmeeting tasks via Composio's Rube MCP, discovering tools first to ensure current schemas and reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill clickmeeting-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: clickmeeting-automation
description: "Automate Clickmeeting tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Clickmeeting Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/clickmeeting](https://composio.dev/toolkits/clickmeeting)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Clickmeeting connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clickmeeting`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clickmeeting`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

Overview

This skill automates Clickmeeting tasks using Composio's Clickmeeting toolkit via a Rube MCP connection. It provides a reliable pattern to discover tools, verify connections, and execute Clickmeeting operations programmatically. The workflow emphasizes always searching for current tool schemas before executing any actions.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, recommended execution plans, and pitfalls for the Clickmeeting toolkit. It verifies or establishes an active Clickmeeting connection via RUBE_MANAGE_CONNECTIONS, then runs selected tools through RUBE_MULTI_EXECUTE_TOOL or bulk runs via RUBE_REMOTE_WORKBENCH. All calls follow schema fields returned by the search and include memory and session management.

When to use it

Automate webinar creation, scheduling, and management in Clickmeeting
Sync Clickmeeting events with other systems or CRMs
Run bulk operations like batch attendee invites or exports
Integrate Clickmeeting flows into larger Rube MCP workflows
When building repeatable, policy-compliant Clickmeeting automations

Best practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool slugs and input schemas
Confirm connection status with RUBE_MANAGE_CONNECTIONS and ensure toolkit 'clickmeeting' is ACTIVE
Use exact field names and types returned by the search results; never hardcode schemas
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs for a single workflow and generate new sessions for separate runs
Handle pagination: check for tokens and fetch until responses are complete

Example use cases

Create and schedule a webinar using the discovered create_webinar tool with schema-compliant arguments
Fetch attendee lists and export CSVs by discovering the right export tool and iterating pages
Bulk-invite users using RUBE_REMOTE_WORKBENCH and run_composio_tool() across multiple events
Validate and update connection credentials programmatically by calling RUBE_MANAGE_CONNECTIONS and following returned auth links
Build a composite workflow that creates an event, registers attendees, and posts summaries to a CRM

FAQ

Do I need API keys to use Rube MCP?

No API keys are required to add Rube MCP; add https://rube.app/mcp as an MCP server in your client configuration.

What if tool schemas change during my workflow?

Always call RUBE_SEARCH_TOOLS before executing tools. If schemas change mid-flow, rediscover tools and adapt arguments to the new schemas.