Do I need to call RUBE_SEARCH_TOOLS before running a workflow?

Yes. The SPI requires discovering current tool schemas; never hardcode slugs.

How do I verify the GoToWebinar connection is ready?

Call RUBE_MANAGE_CONNECTIONS with the go_to_webinar toolkit and check for ACTIVE status.

What should be included in the memory parameter?

Pass an empty object {} if there is no memory, and reuse memory across steps when needed.

go-to-webinar-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/go-to-webinar-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/go-to-webinar-automation/SKILL.md

View on GitHub

Overview

Automate GoToWebinar tasks using Composio's GoToWebinar toolkit via Rube MCP. Always search for current tool schemas with RUBE_SEARCH_TOOLS before running workflows, and ensure an ACTIVE GoToWebinar connection through RUBE_MANAGE_CONNECTIONS. Workflows execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, including a session_id and memory payload.

How This Skill Works

First fetch available tools with RUBE_SEARCH_TOOLS for the GoToWebinar use case to get tool slugs and schemas. Then verify the connection with RUBE_MANAGE_CONNECTIONS and proceed to RUBE_MULTI_EXECUTE_TOOL to run the chosen tool using the schema fields, memory, and the session_id.

When to Use It

When you are setting up a new GoToWebinar automation workflow and need current tool schemas
When you want to perform a specific GoToWebinar operation defined by a discovered tool slug
When integrating GoToWebinar tasks with other systems and you must rely on up to date tool schemas
When you need to reuse a session ID across multiple steps in a workflow
When handling large tool result sets and you need to paginate through tool schemas via RUBE_SEARCH_TOOLS

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover GoToWebinar tools with RUBE_SEARCH_TOOLS using use_case for GoToWebinar operations and note the tool slug and input schema
Step 3: Connect and run: call RUBE_MANAGE_CONNECTIONS to ensure ACTIVE, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first; tool slugs and arguments can change
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovered schema and avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse a session_id within a workflow and create a new one for a new run

Example Use Cases

Schedule a new webinar using a discovered scheduling tool slug and attendee list
Update a webinar's time or title via the matched tool slug from the schema
Fetch attendee registrations and export to a CRM
Launch a live GoToWebinar session automatically via the execute tool
Apply bulk updates to multiple webinars in a single workflow

Frequently Asked Questions

Add this skill to your agents