Open Skills Logo
Open Skills

mails-so-automation

Automate Mails So tasks via Rube MCP (Composio). Always search tools first for current schemas.

Author

@ComposioHQ

Category

Office Automation

Install

Hot:3

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-mails-so-automation&locale=en&source=copy
name:mails-so-automationdescription:"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

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.

  • Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds

  • Call RUBE_MANAGE_CONNECTIONS with toolkit mails_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_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

    OperationApproach
    Find toolsRUBE_SEARCH_TOOLS with Mails So-specific use case
    ConnectRUBE_MANAGE_CONNECTIONS with toolkit mails_so
    ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
    Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
    Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef


    Powered by Composio