mails-so-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/mails-so-automation --openclawMails So Automation via Rube MCP
Automate Mails So operations through Composio's Mails So toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/mails_so
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Mails So connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmails_so - 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 toolkitmails_so - 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: "Mails So 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 Mails So task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["mails_so"]
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 Mails So-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit mails_so |
| 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/mails-so-automation/SKILL.mdView on GitHub Overview
Automate Mails So operations through Composio's Mails So toolkit via Rube MCP. Always search for current tool schemas before running workflows to adapt to changes. This skill covers setup, discovery, and execution patterns to streamline mail workflows.
How This Skill Works
The workflow follows a three-step pattern: discover available tools with RUBE_SEARCH_TOOLS, verify an ACTIVE Mails So connection with RUBE_MANAGE_CONNECTIONS, and execute the selected tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema. Ensure memory is included and reuse session IDs within a workflow for reliability.
When to Use It
- You need to automate a Mails So task but tool schemas may have changed.
- Setting up a new Mails So workflow and you must discover the latest tool slugs.
- Running a batch of Mails So operations that require multiple tools.
- You must validate that the Mails So connection is ACTIVE before execution.
- Handling large results with pagination tokens during tool discovery.
Quick Start
- Step 1: Discover available Mails So tools with RUBE_SEARCH_TOOLS and review input schemas.
- Step 2: Check the Mails So connection status with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
- Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory, then reuse the session_id as needed.
Best Practices
- Always search first: tool schemas change; do not hardcode slugs or arguments.
- Check connection: ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the current search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow to maintain context and enable retries.
Example Use Cases
- Discover available Mails So tools, select the appropriate slug, and execute a send_email workflow using the current schema.
- Batch process multiple mail operations by chaining tools and passing memory to preserve context across steps.
- Validate the Mails So connection is ACTIVE, then run a sequence of tools for a complex automation.
- Maintain a single session_id across steps to optimize retries during a long-running mail automation.
- Handle pagination in RUBE_SEARCH_TOOLS responses to fetch all tools and their schemas before execution.
