conveyor-automation

Conveyor Automation - Automate Conveyor Tasks via Rube MCP

Skill Overview

Conveyor Automation is a skill that automates Conveyor operations through Composio’s Rube MCP server. It enables full tool discovery, connection management, and workflow execution without requiring API keys.

Use Cases

Conveyor Workflow Automation

For scenarios that require automating repetitive Conveyor operations—such as task management, project synchronization, and bulk data processing—use RUBE_MULTI_EXECUTE_TOOL to batch execute multiple tools.

MCP Integration Development

Integrate Conveyor capabilities into Claude Code or other MCP-supported environments. Use Rube MCP’s keyless connection method to quickly set up automation workflows.

Dynamic Tool Discovery and Execution

For cases where tools must be discovered and invoked dynamically based on the current architecture, use RUBE_SEARCH_TOOLS to always retrieve the latest tool architecture and execution plan.

Core Features

Intelligent Tool Discovery

Use RUBE_SEARCH_TOOLS to automatically fetch the latest Conveyor tool package architecture, available tool list, input schemas, and recommended execution plan—ensuring you always use the correct tool parameters.

Connection Status Management

Use RUBE_MANAGE_CONNECTIONS to check and manage Conveyor connection status in real time. Supports one-click activation, obtaining authorization links, and confirming connection availability.

Batch Tool Execution

Use RUBE_MULTI_EXECUTE_TOOL to run multiple Conveyor operations within a single session. Supports in-memory parameter passing, session reuse, and pagination—ideal for complex workflows.

FAQs

Does Conveyor Automation require an API key?

No. Rube MCP uses a keyless connection approach—just add https://rube.app/mcp as an MCP server to use it. During the first connection, bind your Conveyor account via the authorization link returned by RUBE_MANAGE_CONNECTIONS. After that, the connection will remain in ACTIVE status.

How do I ensure I’m using the correct tool architecture?

Before running a workflow each time, call RUBE_SEARCH_TOOLS to fetch the current architecture. Conveyor tool schemas may update, and hardcoding tool slugs or parameters can cause calls to fail. The search results will provide the complete input schema, known pitfalls, and the recommended execution plan.

What if the Conveyor connection is not showing as ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to check the connection status. If it returns a non-ACTIVE status, the system will provide an authorization link. Click the link to authorize your Conveyor account, then call the connection management interface again to confirm it has become ACTIVE, and you can execute tools normally.