What do I need to start using moosend-automation?

Add the Rube MCP server, confirm a Moosend connection via RUBE_MANAGE_CONNECTIONS, and always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.

Do I need API keys for Moosend?

No API keys are required; the MCP endpoint and toolkit handle authentication.

How do I run a Moosend tool?

Discover tools with RUBE_SEARCH_TOOLS, verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper memory+args.

moosend-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Moosend Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moosend

Prerequisites

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

Step 2: Check Connection

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

Overview

Moosend Automation via Rube MCP lets you orchestrate Moosend operations using Composio's Moosend toolkit. It centralizes discovery of available Moosend tools, ensures an active Moosend connection, and executes tool actions through RUBE_MULTI_EXECUTE_TOOL. This approach keeps workflows repeatable, schema-compliant, and auditable.

How This Skill Works

Begin by invoking RUBE_SEARCH_TOOLS to fetch current Moosend tool schemas. Ensure an active Moosend connection with RUBE_MANAGE_CONNECTIONS for the moosend toolkit. When ready, run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and schema-compliant arguments, always including memory and a session_id to support multi-step workflows.

When to Use It

You need to discover available Moosend tools before building a workflow
You must verify the Moosend connection is ACTIVE before execution
You want to run a discovered tool with correct, schema-compliant arguments
Your workflow requires reusing a session_id across steps
You need to handle pagination or multi-step tool outputs during discovery or execution

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Moosend tool schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["moosend"] and then RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and proper arguments (include memory and session_id)

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from search results; avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related workflows and handle pagination tokens

Example Use Cases

Discover a Moosend tool for sending a campaign and execute it with proper arguments
Sync a list of subscribers by discovering the add-subscribers tool and running it with the subscriber data
Query Moosend analytics tool and store results in memory for reporting
Update multiple subscriber fields in bulk using a discovered tool and memory
Choreograph a multi-tool workflow that creates a campaign, adds recipients, and sends it

Frequently Asked Questions

Add this skill to your agents