What is autobound-automation?

A workflow pattern to automate Autobound tasks via Rube MCP and the Autobound toolkit.

Do I need API keys or credentials?

No API keys are required; you only need to configure the MCP endpoint and establish an Autobound connection.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current schemas; do not hardcode tool slugs or arguments and include memory in multi-execute calls.

autobound-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Autobound Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/autobound

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Autobound operations using Composio's Autobound toolkit through the Rube MCP. This skill orchestrates tool discovery, connection setup, and tool execution to automate Autobound tasks reliably. Always search for current tool schemas before running any workflow.

How This Skill Works

You first verify available Autobound tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then you establish or validate an Autobound connection with RUBE_MANAGE_CONNECTIONS and ensure its status is ACTIVE. Finally, you execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL, passing the required arguments and a memory object, while aligning with the exact field names from the tool's schema.

When to Use It

After discovering Autobound tools with RUBE_SEARCH_TOOLS, automate selecting and running a task.
Before executing any workflow, verify the RUBE_MANAGE_CONNECTIONS status is ACTIVE.
When building multi-step Autobound workflows, reuse the same session_id across steps.
When performing bulk actions, orchestrate multiple tool runs via RUBE_REMOTE_WORKBENCH.
When starting a new Autobound workflow, fetch the latest tool schemas with RUBE_GET_TOOL_SCHEMAS to avoid hardcoding.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client.
Step 2: Run RUBE_SEARCH_TOOLS to discover Autobound tools and their input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS for autobound and, once ACTIVE, execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and the discovered slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results when building arguments.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and fetch pagination tokens if results are paginated.

Example Use Cases

Discover Autobound tools, connect, and run a specific tool slug with correct arguments.
Execute multiple Autobound tools in sequence using RUBE_MULTI_EXECUTE_TOOL and a shared memory object.
Fetch all available tools by handling pagination tokens with RUBE_SEARCH_TOOLS.
Reuse a single session_id across a multi-step Autobound workflow.
Validate tool schemas with RUBE_GET_TOOL_SCHEMAS before executing to prevent errors.

Frequently Asked Questions

Add this skill to your agents