cloudconvert-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/cloudconvert-automation --openclawCloudconvert Automation via Rube MCP
Automate Cloudconvert operations through Composio's Cloudconvert toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cloudconvert
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cloudconvert connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcloudconvert - 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 toolkitcloudconvert - 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: "Cloudconvert 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 Cloudconvert task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudconvert"]
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 Cloudconvert-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit cloudconvert |
| 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/cloudconvert-automation/SKILL.mdView on GitHub Overview
Automate Cloudconvert operations through Composio's Cloudconvert toolkit using Rube MCP. It emphasizes discovering current tool schemas first and requires an active Cloudconvert connection managed through RUBE_MANAGE_CONNECTIONS. By orchestrating tools with RUBE_MULTI_EXECUTE_TOOL, you can build repeatable, scalable conversion workflows.
How This Skill Works
Begin with RUBE_SEARCH_TOOLS to fetch available Cloudconvert tools and their input schemas. Next, verify the Cloudconvert connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, a memory payload, and a session_id to preserve state.
When to Use It
- Batch or chained Cloudconvert conversions discovered via RUBE_SEARCH_TOOLS.
- Automate recurring tasks in a workflow by reusing a session_id.
- Validate and refresh the Cloudconvert connection before execution.
- Run multiple tools in a single batch with RUBE_MULTI_EXECUTE_TOOL.
- Handle changing tool schemas by re-discovering tools before each run.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and run RUBE_SEARCH_TOOLS to verify availability.
- Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkits: ["cloudconvert"] and ensure the status is ACTIVE.
- Step 3: Choose a discovered tool_slug from the search results and run RUBE_MULTI_EXECUTE_TOOL with memory: {} and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS to fetch current tool schemas prior to execution.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
- Use exact field names and types from the search results (schema compliance).
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even when empty.
- Reuse session IDs within a workflow and generate new IDs for new workflows.
Example Use Cases
- Batch-convert a folder of documents by discovering a conversion tool and running it in a single session.
- Orchestrate upload → convert → notify steps by chaining RUBE_MULTI_EXECUTE_TOOL calls.
- Onboard a new Cloudconvert account and perform a test conversion automatically.
- Fetch all available Cloudconvert tools and their schemas for a project catalog.
- Execute multiple tools in parallel using a single session and memory state.
