turbot-pipes-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/turbot-pipes-automation --openclawTurbot Pipes Automation via Rube MCP
Automate Turbot Pipes operations through Composio's Turbot Pipes toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/turbot_pipes
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Turbot Pipes connection via
RUBE_MANAGE_CONNECTIONSwith toolkitturbot_pipes - 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 toolkitturbot_pipes - 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: "Turbot Pipes 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 Turbot Pipes task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["turbot_pipes"]
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 Turbot Pipes-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit turbot_pipes |
| 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/turbot-pipes-automation/SKILL.mdView on GitHub Overview
Automates Turbot Pipes tasks through Composio's Turbot Pipes toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running and verifying the ACTIVE connection with RUBE_MANAGE_CONNECTIONS. This minimizes schema drift and connectivity issues during automation.
How This Skill Works
You first discover available tools and their input schemas using RUBE_SEARCH_TOOLS. Then you ensure the Turbot Pipes connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, you execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and a memory object, tied to a session_id.
When to Use It
- You’re about to run a Turbot Pipes task and need current tool schemas.
- You must verify the Turbot Pipes connection is ACTIVE before execution.
- You want to select and run a specific Turbot Pipes tool discovered via RUBE_SEARCH_TOOLS.
- You need to execute multiple Turbot Pipes tools in a single workflow with a shared session.
- You’re performing bulk operations or troubleshooting tool slugs with pagination.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["turbot_pipes"] and ensure ACTIVE.
- Step 3: Use RUBE_SEARCH_TOOLS to discover a tool, then run RUBE_MULTI_EXECUTE_TOOL with the tool_slug, arguments, memory: {}, and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas.
- Verify an ACTIVE Turbot Pipes connection with RUBE_MANAGE_CONNECTIONS before executing.
- Use exact field names and types from the search results; don’t hardcode tool slugs.
- Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call.
- Reuse session IDs within a workflow and fetch new ones only for new workflows; handle pagination when fetching tool schemas.
Example Use Cases
- Schedule a nightly Turbot Pipes workflow by discovering available tools and running a selected one with its required arguments.
- Connect to Turbot Pipes with RUBE_MANAGE_CONNECTIONS and execute a tool slug obtained from RUBE_SEARCH_TOOLS.
- Chain multiple Turbot Pipes steps in a single session, reusing the session_id for continuity.
- Perform bulk Turbot Pipes operations via RUBE_REMOTE_WORKBENCH using run_composio_tool on discovered tools.
- Re-fetch tool schemas with RUBE_SEARCH_TOOLS to resolve breaking changes in a tool’s input schema before re-running.
