How do I ensure schemas are up to date?

Always call RUBE_SEARCH_TOOLS before executing and use the returned input schemas to populate tool arguments exactly as provided.

What if the Interzoid connection is not ACTIVE?

Run RUBE_MANAGE_CONNECTIONS for the interzoid toolkit and follow the auth flow; re-check the status until it shows ACTIVE before continuing.

Can I reuse a session across multiple tools?

Yes, reuse session IDs within a workflow to maintain context, but generate new session IDs for separate workflows and handle pagination as needed.

interzoid-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Interzoid Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/interzoid

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Interzoid operations using Composio's Interzoid toolkit through Rube MCP. It emphasizes discovering current tool schemas before running workflows to adapt to changes and requires an active RUBE_SEARCH_TOOLS and Interzoid connection.

How This Skill Works

Begin by discovering available tools with RUBE_SEARCH_TOOLS to fetch slugs and input schemas. Then verify an active Interzoid connection with RUBE_MANAGE_CONNECTIONS and execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and required arguments, always including memory.

When to Use It

When tool schemas may change and you need fresh slugs before running a workflow
When you must ensure an active Interzoid connection prior to execution
When performing a sequence of Interzoid tasks in a single session
When you want to avoid hardcoding tool slugs or arguments
When you need to handle multi-step tool discovery with pagination

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Interzoid tool slugs and input schemas
Step 3: Use RUBE_MANAGE_CONNECTIONS to ensure the Interzoid toolkit is ACTIVE, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, memory, and a session_id

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Ensure schema compliance by using exact field names and types from search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows; watch for pagination tokens

Example Use Cases

Enrich contact data by discovering an Interzoid tool and executing a lookup with proper arguments
Batch-verify addresses for a dataset using a discovered Interzoid tool
Process multiple Interzoid tasks in one session and log results
Reset and re-establish connection if ACTIVE status is lost before a run
Explore all relevant Interzoid operations by paginating tool schemas and executing them as needed

Frequently Asked Questions

Add this skill to your agents