Moosend Automation

What This Skill Does

• This skill automates Moosend operations through the Composio Moosend toolkit via Rube MCP.
• It's designed for users looking to streamline their email marketing workflows.
• The skill focuses on setup, tool discovery, and execution, while highlighting common pitfalls to avoid.

When to Use

• Discover available Moosend tools.
• Check the status of the Moosend connection.
• Execute specific Moosend tools.
• Automate email campaign creation.
• Manage subscriber lists automatically.
• Trigger automated email sequences.

Key Features

• Uses Rube MCP to automate Moosend tasks.
• Requires an active Moosend connection.
• Employs RUBE_SEARCH_TOOLS for tool discovery.
• Checks connection status via RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides guidance on avoiding common pitfalls.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed 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

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: {}

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