No API keys are required; configure Rube MCP at https://rube.app/mcp.

What must be true before running a workflow?

RUBE_SEARCH_TOOLS must respond; the Eventzilla connection must be ACTIVE; memory must be included; do not hardcode tool slugs.

What happens if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS to fetch current schemas and avoid breaking changes.

eventzilla-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/eventzilla-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Eventzilla Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/eventzilla

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["eventzilla"]
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 Eventzilla-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `eventzilla`
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/eventzilla-automation/SKILL.mdView on GitHub

Overview

Automate Eventzilla tasks using Composio's toolkit via Rube MCP. This skill keeps tool schemas current by always searching tools first and requires an active Eventzilla connection and a connected MCP.

How This Skill Works

You start by discovering available Eventzilla tools with RUBE_SEARCH_TOOLS, which returns slugs, input schemas, and execution plans. Then you verify or establish the Eventzilla connection with RUBE_MANAGE_CONNECTIONS, ensuring ACTIVE status before any workflow. Finally, you execute tools via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments, reusing sessions and including a memory object.

When to Use It

When you need to automate recurring Eventzilla operations and keep tool schemas up to date
When setting up a new Eventzilla workflow and you must discover the latest tool slugs
Before executing any Eventzilla tools, ensure the connection is ACTIVE
When performing bulk or multi-step actions using RUBE_MULTI_EXECUTE_TOOL
When reusing session IDs across a series of Eventzilla tasks

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit 'eventzilla' and ensure ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related workflows and handle pagination if present

Example Use Cases

Discover tools for Eventzilla operations and run a 'CreateEvent' slug with required arguments
Establish an Eventzilla connection and create a new event in a single workflow
List events using a discovered tool and handle pagination tokens
Bulk update attendee registrations via a discovered tool slug
Validate ACTIVE connection before performing a multi-tool workflow and reuse session IDs

Frequently Asked Questions

Add this skill to your agents