convolo-ai-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/convolo-ai-automation --openclawConvolo AI Automation via Rube MCP
Automate Convolo AI operations through Composio's Convolo AI toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/convolo_ai
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Convolo AI connection via
RUBE_MANAGE_CONNECTIONSwith toolkitconvolo_ai - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitconvolo_ai - 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: "Convolo AI 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 Convolo AI task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["convolo_ai"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Convolo AI-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit convolo_ai |
| 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/convolo-ai-automation/SKILL.mdView on GitHub Overview
Automate Convolo AI operations using Composio’s Convolo AI toolkit through Rube MCP. This skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing any workflows, ensuring up-to-date inputs and avoiding hard-coded tool slugs.
How This Skill Works
Connect to Rube MCP and verify the Convolo AI toolkit is active via RUBE_MANAGE_CONNECTIONS. Always discover available tools with RUBE_SEARCH_TOOLS to get current tool slugs and schemas, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including the memory field as required.
When to Use It
- Automating routine Convolo AI tasks with updated tool schemas
- When tool schemas change and hard-coded slugs could break workflows
- When you need to validate an ACTIVE connection before executing tools
- When you want to reuse a session_id across a multi-step workflow
- When performing batch or bulk operations with multiple tools
Quick Start
- Step 1: Add the Rube MCP endpoint https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Verify RUBE_SEARCH_TOOLS responds and fetch Convolo AI tool slugs and schemas
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits convolo_ai and ensure ACTIVE before executing any workflows
Best Practices
- Always search first to obtain current tool schemas using RUBE_SEARCH_TOOLS
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
- Use exact field names and types from the search results
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and create new ones for new workflows
Example Use Cases
- Discover tools with RUBE_SEARCH_TOOLS, connect via RUBE_MANAGE_CONNECTIONS, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL using the required arguments
- Automate a sequence of Convolo AI tasks across multiple tools in one session using discovered slugs and schemas
- If tool schemas update, re-run RUBE_SEARCH_TOOLS before updating arguments and re-executing
- Reuse an existing session_id for a recurring Convolo AI workflow to preserve context
- Bulk run multiple Convolo AI tools using RUBE_REMOTE_WORKBENCH run_composio_tool for batch processing
