Do I need API keys to use sympla-automation?

No API keys are needed; just configure the MCP endpoint and ensure the Sympla toolkit connection is ACTIVE.

Why must I call RUBE_SEARCH_TOOLS before running a tool?

Tool schemas and slugs can change; searching first prevents hardcoding invalid inputs.

How can I confirm the Sympla connection is ready?

Run RUBE_MANAGE_CONNECTIONS for the sympla toolkit and verify that the status is ACTIVE before execution.

sympla-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Sympla Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sympla

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Sympla operations through Composio's Sympla toolkit using Rube MCP. It discovers current tool schemas first and then executes tasks against an active Sympla connection, enabling scalable event and attendee workflows.

How This Skill Works

Technically, you first call RUBE_SEARCH_TOOLS to fetch tool slugs and schemas, then verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and finally run RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and arguments. Always include memory in the call.

When to Use It

When you need to perform a Sympla operation by using discovered tool schemas (for example attendee management or event updates)
When tool slugs or input schemas may have changed and you must fetch fresh definitions with RUBE_SEARCH_TOOLS
When you must verify that the Sympla connection is ACTIVE before running workflows
When batching multiple Sympla tasks in a single run using RUBE_MULTI_EXECUTE_TOOL
When debugging or auditing workflow behavior by fetching current tool schemas with RUBE_GET_TOOL_SCHEMAS

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and ensure RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit set to sympla and confirm ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and memory, passing a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to retrieve current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to execution
Use exact field names and types from the tool search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for separate runs

Example Use Cases

Export attendees for a Sympla event using a discovered tool slug
Create a new Sympla event and publish tickets via a guided workflow
Batch process attendee confirmations and status updates in one run
Validate current tool schemas before integrating with external systems
Resume failed runs by reusing a session_id and re-discovering tools

Frequently Asked Questions

Add this skill to your agents