What is required to use this skill?

You need a connected Rube MCP (RUBE_SEARCH_TOOLS available) and an ACTIVE Emailoctopus connection via RUBE_MANAGE_CONNECTIONS. Always search for current tool schemas before executing.

Do I need to hardcode tool slugs?

No. Tool slugs and input schemas are discovered at runtime using RUBE_SEARCH_TOOLS; hardcoding is discouraged.

How are memory and sessions used?

Memory is included in RUBE_MULTI_EXECUTE_TOOL calls to preserve state; session IDs should be reused within a workflow and refreshed for new workflows to manage context and pagination when applicable.

emailoctopus-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Emailoctopus Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/emailoctopus

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Emailoctopus operations through Composio's Emailoctopus toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas before execution to ensure compatibility and reduce errors.

How This Skill Works

Begin by querying available tools with RUBE_SEARCH_TOOLS to fetch up-to-date slugs and input schemas. Then verify an ACTIVE Emailoctopus connection using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact arguments, memory, and session for reliable, stateful runs.

When to Use It

You want to automatically discover current Emailoctopus tool options before building a workflow.
You need to establish and verify an ACTIVE Emailoctopus connection via RUBE_MANAGE_CONNECTIONS.
You intend to execute a discovered tool with the correct slug and schema using RUBE_MULTI_EXECUTE_TOOL.
You require session continuity within a multi-step workflow (reuse session IDs).
You must handle potential pagination or schema changes by re-fetching tool schemas first.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["emailoctopus"] and confirm ACTIVE status.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS reports an ACTIVE status before any execution.
Use the exact field names and types from the discovered schemas; do not hardcode.
Include a memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({ }).
Reuse session IDs within a workflow and fetch new ones only for new workflows; watch for pagination tokens.

Example Use Cases

Add new subscribers from a CRM to a specific Emailoctopus list using a discovered 'add_subscribers' tool slug.
Update subscriber fields in Emailoctopus from an external database by executing a 'update_subscriber' tool with matched IDs.
Create and schedule a new Emailoctopus campaign from a template via a 'create_campaign' tool.
Fetch campaign metrics (opens, clicks) for reporting by running a 'get_campaign_stats' tool.
Bulk unsubscribe or delete inactive subscribers using a 'bulk_unsubscribe' tool discovered at runtime.

Frequently Asked Questions

Add this skill to your agents