What is mailbluster-automation?

A skill to automate Mailbluster tasks using Composio's Rube MCP, requiring up-to-date tool schemas and an active connection.

Do I need to hardcode tool slugs?

No. Always use RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before execution.

How should I handle credentials?

Manage connections with RUBE_MANAGE_CONNECTIONS and keep credentials out of payloads; rely on the tool's authenticated session context.

mailbluster-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Mailbluster Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailbluster

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mailbluster"]
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 Mailbluster-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mailbluster`
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/mailbluster-automation/SKILL.md

View on GitHub

Overview

Automate Mailbluster operations through Composio's Mailbluster toolkit via Rube MCP. This skill orchestrates tool discovery, connection validation, and execution to run Mailbluster tasks without manual steps.

How This Skill Works

You first call RUBE_SEARCH_TOOLS to fetch available Mailbluster tool slugs and schemas, then verify the Mailbluster connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing in the schema-compliant arguments, memory (even if empty), and a session_id to maintain workflow continuity.

When to Use It

When starting an automation workflow that relies on up-to-date Mailbluster tool schemas and slugs.
When you need to validate and activate a Mailbluster connection before running any tool.
When performing a sequence of tool executions in a single session for a campaign workflow.
When performing bulk or batch Mailbluster operations via RUBE_REMOTE_WORKBENCH or multi-tool execution.
When auditing or updating automation scripts by refreshing tool schemas with current definitions.

Quick Start

Step 1: Discover tools for Mailbluster with RUBE_SEARCH_TOOLS and review the returned tool slugs and input schemas.
Step 2: Establish and verify an ACTIVE Mailbluster connection using RUBE_MANAGE_CONNECTIONS with toolkit 'mailbluster'.
Step 3: Execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments and memory: {} using a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and slugs.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing any tool.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
Reuse session IDs within a workflow to maintain context; generate new sessions only for new workflows.

Example Use Cases

Discover available Mailbluster tools with RUBE_SEARCH_TOOLS for a given use case, then execute a tool with schema-compliant arguments returned by the search.
Connect to the Mailbluster toolkit via RUBE_MANAGE_CONNECTIONS and verify ACTIVE status before invoking a tool to export subscribers.
Run a multi-tool Mailbluster workflow in a single session by first discovering tools, then executing multiple tools with discovered slugs and arguments.
Perform bulk email tasks by using RUBE_REMOTE_WORKBENCH’s run_composio_tool() to process several tool executions in parallel.
Refresh the tool schemas by calling RUBE_GET_TOOL_SCHEMAS to ensure automation scripts use current definitions before running tools.

Frequently Asked Questions

Add this skill to your agents