$ ~/registry/skill/composiohq-composio-skills-emailoctopus-automation

SKILL

emailoctopus-automation

Automate Emailoctopus workflows through Rube MCP with schema-first tool discovery.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "emailoctopus-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/emailoctopus-automation/SKILL.md
2. Save it as ~/.claude/skills/emailoctopus-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Discover tools for an Emailoctopus workflow

Developers or marketers can search for the current tools and schemas before automating tasks, avoiding outdated tool names or arguments. This fits AI workflows that need reliable execution.

Connect and verify Emailoctopus access

When using it for the first time or after a connection issue, users can check the emailoctopus connection through Rube MCP and complete authorization from the returned link. They should confirm ACTIVE status before running further actions.

Run automation with the latest schema

When a team wants an AI agent to perform Emailoctopus operations, it can search tools first and then execute against the returned schema. This reduces failures caused by changing field types or arguments.

// docs

AI summary

The README explains how to automate Emailoctopus operations through Composio’s Emailoctopus toolkit via Rube MCP. It covers prerequisites, setup and authorization, the recommended workflow of searching tools first, checking connection status, and then executing tools, plus important cautions such as strict schema compliance, session reuse, always including the memory parameter, and handling pagination.

Show full docs ▾

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

// FAQ

What does this skill do?

It uses Rube MCP to access Composio’s Emailoctopus toolkit for automating Emailoctopus operations. The docs specifically emphasize searching for tools first and executing against the latest schema.

What are the prerequisites?

You need Rube MCP connected and `RUBE_SEARCH_TOOLS` available. You also need an active `emailoctopus` toolkit connection created through `RUBE_MANAGE_CONNECTIONS`.

Why must I search tools first?

Because tool schemas can change, the docs explicitly say not to hardcode tool slugs or arguments. You should call `RUBE_SEARCH_TOOLS` first to get the current schema before execution.

Automate EspoCRM tasks and streamline customer workflows through Rube MCP.

ComposioGet→

$ loading_