Do I need API keys to use this skill?

No. You just need to add the MCP endpoint (https://rube.app/mcp) and ensure RUBE_SEARCH_TOOLS is reachable to fetch current tool schemas.

Why must I search tools first before executing?

Tool schemas change frequently. Searching first ensures you use current tool slugs and correct input fields, preventing schema mismatch errors.

How do I execute a tool correctly?

Use the slug returned from RUBE_SEARCH_TOOLS and pass exactly those fields as arguments in RUBE_MULTI_EXECUTE_TOOL, include memory even if empty, and provide a valid session_id after verifying the connection is ACTIVE.

agencyzoom-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Agencyzoom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/agencyzoom

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Agencyzoom operations using Composio's Rube MCP toolkit. The approach emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, validating an ACTIVE Agencyzoom connection with RUBE_MANAGE_CONNECTIONS, and executing tasks through RUBE_MULTI_EXECUTE_TOOL. This keeps automation resilient to schema drift and enables repeatable, error-checked workflows.

How This Skill Works

Connect to Rube MCP via the provided MCP endpoint, then fetch up-to-date Agencyzoom tool schemas with RUBE_SEARCH_TOOLS. Verify the Agencyzoom connection is ACTIVE using RUBE_MANAGE_CONNECTIONS, and finally execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including memory and a session_id. This sequence ensures you always work with current tools and valid connections during automation.

When to Use It

Starting a new Agencyzoom automation and you need up-to-date tool schemas
Verifying the Agencyzoom connection is ACTIVE before running workflows
Discovering available Agencyzoom tools to plan and design an automation
Running multi-tool workflows with proper memory and session management
Debugging or updating workflows to account for schema changes

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm connectivity
Step 3: Discover tools with RUBE_SEARCH_TOOLS, ensure the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then run a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Do not hardcode tool slugs or arguments; rely on schemas returned by search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and fetch pagination tokens if present

Example Use Cases

Discover tools for a common Agencyzoom task, then execute the returned tool slug with the required arguments derived from the schema
If RUBE_MANAGE_CONNECTIONS reports a non-ACTIVE status, follow the auth flow to activate the Agencyzoom toolkit and retry
Run a multi-tool workflow in a single session using RUBE_MULTI_EXECUTE_TOOL, ensuring memory is provided and the session_id is reused
Perform bulk Agencyzoom operations via RUBE_REMOTE_WORKBENCH with run_composio_tool() as described in the Quick Reference
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to audit integrations or debug schema drift

Frequently Asked Questions

Add this skill to your agents