What does mailersend-automation do?

It automates Mailersend operations through Composio using Rube MCP, discovering current tool schemas and executing them safely.

No. You add the Rube MCP endpoint (https://rube.app/mcp) and authenticate via the connection workflow; no individual API keys are required.

How do I keep tool schemas up to date?

Always run RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before executing any workflow; do not hardcode slugs or arguments.

mailersend-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Mailersend Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailersend

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill lets you orchestrate Mailersend operations through Composio's toolkit via Rube MCP. It emphasizes fetching current tool schemas first with RUBE_SEARCH_TOOLS and establishing an active Mailersend connection before executing workflows.

How This Skill Works

Discover available Mailersend tools with RUBE_SEARCH_TOOLS, verify the Mailersend connection via RUBE_MANAGE_CONNECTIONS, then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL. Always include a memory object and use the schema-provided field names; avoid hardcoding slugs or arguments.

When to Use It

When you need to automate a Mailersend workflow end-to-end by discovering the correct tool and executing it
When tool schemas change and you must fetch current slugs and arguments before running
When performing batch or scheduled Mailersend tasks within a larger Composio workflow
When you must confirm the Mailersend connection is ACTIVE prior to execution
When integrating Mailersend tasks into multi-step sessions and reusing session IDs

Quick Start

Step 1: Add the MCP endpoint and verify RUBE_SEARCH_TOOLS returns available tools
Step 2: Establish a Mailersend connection with RUBE_MANAGE_CONNECTIONS (toolkit 'mailersend')
Step 3: Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with memory parameter

Best Practices

Always search for current tool schemas with RUBE_SEARCH_TOOLS before any run
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Use exact field names and types from the search results; do not hardcode slugs or args
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate a new one for new workflows

Example Use Cases

Discover a Mailersend tool for sending a batch email and execute it with the required arguments
Schedule a campaign by locating the appropriate tool and supplying the scheduled time and recipients
Fetch delivery statistics for a campaign and log results in memory for later reporting
Update recipient lists or tags by running a corresponding Mailersend tool with updated fields
Retry a failed send by initiating a new session and re-running the tool with updated parameters

Frequently Asked Questions

Add this skill to your agents