What is Rube MCP and how does it relate to Sendloop automation?

Rube MCP is Composio's managed cloud platform for connecting and orchestrating tools. This skill uses it to run Sendloop tasks by dynamically discovering tool schemas and executing them via discovered slugs.

Why must I always search tools first?

Tool schemas change over time. RUBE_SEARCH_TOOLS provides current slugs, input fields, and execution plans, preventing hardcoded errors and enabling safe, up-to-date automation.

What if the connection is not ACTIVE?

Do not run workflows. Complete the auth flow via the returned link, recheck with RUBE_MANAGE_CONNECTIONS, and ensure ACTIVE before executing any tools.

sendloop-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sendloop Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sendloop

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Sendloop operations through Composio's Sendloop toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas before execution to adapt to changes. This keeps Sendloop automations reliable and up-to-date.

How This Skill Works

Connect to Rube MCP and verify Sendloop availability with RUBE_SEARCH_TOOLS, then manage the Sendloop toolkit connection using RUBE_MANAGE_CONNECTIONS. When ready, execute discovered tool slugs with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id, ensuring the connection is ACTIVE before running workflows.

When to Use It

When you need to automate Sendloop tasks and want current tool schemas
When adding a new Sendloop workspace via Rube MCP and need a fresh setup
When you must run a discovered Sendloop tool slug with proper arguments
When performing bulk or chained Sendloop operations via RUBE_MULTI_EXECUTE_TOOL
When validating that the Sendloop connection is ACTIVE before running workflows

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and confirm RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["sendloop"] and verify ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL, passing memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs where possible and watch for pagination tokens

Example Use Cases

Discover Sendloop tools, then run a campaign-send tool slug with the required arguments
Connect a Sendloop toolkit to an existing Rube MCP and confirm ACTIVE
Execute a tool discovered from RUBE_SEARCH_TOOLS to update a subscriber list
Use RUBE_GET_TOOL_SCHEMAS to review a tool's input schema before running
Chain steps: discover -> connect -> execute in a single workflow using a shared session

Frequently Asked Questions

Add this skill to your agents