What is required to get started?

You must have Rube MCP connected (RUBE_SEARCH_TOOLS available) and an ACTIVE Mailsoftly connection via RUBE_MANAGE_CONNECTIONS for toolkit mailsoftly.

Should I hardcode tool slugs?

No; always fetch tool slugs with RUBE_SEARCH_TOOLS because schemas change.

Is memory required in all tool executions?

Yes, include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

mailsoftly-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Mailsoftly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailsoftly

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Mailsoftly operations through Composio's Mailsoftly toolkit via Rube MCP. It emphasizes discovering tool schemas first to adapt to changes, validating the active Mailsoftly connection, and then executing discovered tools with proper session and memory handling.

How This Skill Works

The workflow begins by using RUBE_SEARCH_TOOLS to fetch current Mailsoftly tool slugs and input schemas. It then validates the Mailsoftly connection with RUBE_MANAGE_CONNECTIONS and ensures it is ACTIVE. Finally, it executes the selected tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, an explicit memory payload, and the active session_id.

When to Use It

When automating recurring Mailsoftly tasks that rely on up-to-date tool schemas.
When you need to verify an ACTIVE Mailsoftly connection before running workflows.
When selecting and executing a specific Mailsoftly tool discovered via RUBE_SEARCH_TOOLS.
When performing batch operations across multiple Mailsoftly tools within a single session.
When troubleshooting tool executions using the provided memory and session patterns.

Quick Start

Step 1: Discover available Mailsoftly tools with RUBE_SEARCH_TOOLS; note tool_slugs and input schemas.
Step 2: Check the Mailsoftly connection status with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE.
Step 3: Execute a selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory: {} and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before a workflow to fetch current tool slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS status is ACTIVE before running tools.
Use exact field names and types from search results; avoid hardcoding.
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs for related steps; generate a new session only for new workflows.

Example Use Cases

Example 1: Automate a Mailsoftly campaign by discovering available tools, confirming the ACTIVE connection, and executing the campaign-creation tool with the required arguments.
Example 2: Retrieve the latest email templates schema from RUBE_SEARCH_TOOLS and run a tool to compose emails with personalized fields.
Example 3: Import contact data into Mailsoftly by selecting the import tool from search results and executing with memory to track progress.
Example 4: Perform a bulk update across multiple campaigns by executing several tools in one session via RUBE_MULTI_EXECUTE_TOOL and memory.
Example 5: Debug a failing workflow by listing tool schemas, verifying the connection, and re-running with updated arguments.

Frequently Asked Questions

Add this skill to your agents