go-to-webinar-automation

通过 Rube MCP 自动处理 GoToWebinar 的创建、报名与参会管理流程

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "go-to-webinar-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/go-to-webinar-automation/SKILL.md
2. 保存为 ~/.claude/skills/go-to-webinar-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

批量创建网络研讨会

输入

先搜索可用的 GoToWebinar 工具及其最新参数 schema，然后根据下面的活动表批量创建 3 场网络研讨会：主题、时间、时长、讲师、描述都已提供。创建后返回每场活动的 webinarKey、报名链接和创建状态汇总表。

预期产出

3 场研讨会创建结果汇总，包含唯一标识、报名链接及成功或失败原因。

同步报名名单

输入

先搜索 GoToWebinar 相关工具与 schema。获取指定 webinarKey 的最新报名名单，按姓名、邮箱、报名时间导出结构化列表；如果发现重复邮箱，请合并并标记冲突项。

预期产出

整理后的报名名单，包含去重结果、冲突标记和可直接使用的结构化数据。

统计参会表现

输入

先搜索可用工具和最新 schema。读取某场 GoToWebinar 的参会数据，统计报名人数、实际出席人数、出席率、平均停留时长，并按参会者输出明细表和总结。

预期产出

包含关键参会指标的统计结果，以及参会者明细与简要结论。

// 文档

GoToWebinar Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/go_to_webinar

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["go_to_webinar"]
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 GoToWebinar-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `go_to_webinar`
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`