home / skills / composiohq / awesome-claude-skills / mails-so-automation

mails-so-automation skill

/mails-so-automation

This skill automates Mails So operations through Rube MCP, discovering tools first and ensuring active connections for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill mails-so-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: mails-so-automation
description: "Automate Mails So tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Mails 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](https://composio.dev/toolkits/mails_so)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Mails So connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mails_so`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mails_so`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

Overview

This skill automates Mails So tasks using Composio’s Mails So toolkit via a Rube MCP server. It guides discovery of current tool schemas, connection checks, and safe execution patterns so workflows run reliably. The skill emphasizes searching tools first and strict schema compliance to avoid runtime errors.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, and recommended execution plans. It then ensures an ACTIVE Mails So connection via RUBE_MANAGE_CONNECTIONS. Finally it runs operations through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk tasks) using schema-compliant arguments and a session-aware workflow.

When to use it

  • Automate sending, routing, or management tasks in Mails So programmatically
  • Run multi-step Mails So workflows that require composing several toolkit calls
  • Perform bulk or remote operations using Composio tools through Rube MCP
  • When schema drift is likely and you need a discovery-first execution strategy
  • Integrate Mails So into larger agent workflows that require session state and memory

Best practices

  • Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes
  • Verify connection status with RUBE_MANAGE_CONNECTIONS and complete auth links until status is ACTIVE
  • Use exact field names and types returned by the search results to ensure schema compliance
  • Include a memory object (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session_id for related workflow steps; generate new sessions for distinct workflows
  • Handle pagination tokens from search responses to ensure full results

Example use cases

  • Discover and invoke a Mails So 'send_message' tool by fetching its latest schema at runtime
  • Batch-update mailing lists using RUBE_REMOTE_WORKBENCH with run_composio_tool() for high-volume ops
  • Build an agent that checks connection status, discovers an appropriate tool, and executes a campaign step-by-step
  • Automate message routing and tagging using multiple Composio toolkit calls within a single session
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before constructing complex payloads

FAQ

What is the first call I should make when using this skill?

Always call RUBE_SEARCH_TOOLS with a Mails So-specific use case to retrieve current tool slugs and schemas.

What if my connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to get the auth link, complete the authentication flow, then confirm the status is ACTIVE before executing tools.