Rube MCP is Composio's management plane that lets you discover tool schemas, manage connections, and execute tools programmatically.

Why must I search tools first?

Tool schemas change over time; searching ensures you use current tool slugs and argument structures.

What if the connection is not ACTIVE?

Follow the auth flow provided to complete setup, then re-check until the status shows ACTIVE before running workflows.

emailable-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Emailable Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/emailable

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Emailable operations via Composio's Emailable toolkit through Rube MCP. It emphasizes discovering current tool schemas first and ensuring an ACTIVE connection before running workflows, making routine tasks faster and less error-prone.

How This Skill Works

The skill workflow is: discover available Emailable tools with RUBE_SEARCH_TOOLS, verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the proper arguments, memory, and session_id. This approach keeps tool usage up-to-date and resilient to schema changes.

When to Use It

When you need to automate recurring Emailable operations (e.g., campaigns, deliverability checks, or status updates).
When tool schemas may change, requiring dynamic discovery first to obtain current slugs and arguments.
When you must verify and establish an ACTIVE Emailable connection via Rube MCP before running workflows.
When performing bulk or batch Emailable tasks and wanting to maintain session continuity with memory and session_id.
When integrating Emailable tasks into larger Composio workflows and dashboards that rely on up-to-date tool schemas.

Quick Start

Step 1: Discover available Emailable tools with RUBE_SEARCH_TOOLS (use_case: 'Emailable operations').
Step 2: Ensure an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for toolkit 'emailable'.
Step 3: Execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, proper arguments, memory: {}, and session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tools to avoid stale slugs and arguments.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered tool schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it’s empty ({}).
Reuse session IDs when appropriate and handle pagination tokens in tool discovery.

Example Use Cases

Discover Emailable operation tools with RUBE_SEARCH_TOOLS, then run a selected tool against a batch of emails.
Establish an Emailable connection via RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE before any workflow.
Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the required arguments, memory, and session_id.
Perform bulk Emailable tasks and utilize RUBE_REMOTE_WORKBENCH with run_composio_tool() for orchestration.
Regularly refresh tool schemas by re-running RUBE_SEARCH_TOOLS to ensure slugs and schemas are current before automation.

Frequently Asked Questions

Add this skill to your agents