Do I need API keys to use enginemailer-automation?

No. You just add the MCP server endpoint (e.g., https://rube.app/mcp) and rely on RUBE_SEARCH_TOOLS to fetch current tool schemas.

How do I ensure tool schemas are current and accurate?

Always call RUBE_SEARCH_TOOLS before selecting tool slugs or arguments; do not hardcode tool details, and handle pagination if returned.

What if the Enginemailer connection is not ACTIVE?

Follow the returned authentication link in RUBE_MANAGE_CONNECTIONS to complete setup, and re-check that the status is ACTIVE before running workflows.

enginemailer-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Enginemailer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/enginemailer

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Enginemailer operations using Composio's Rube MCP toolkit. Always search tools first to fetch current schemas and ensure an ACTIVE Enginemailer connection before running workflows.

How This Skill Works

The skill uses Rube MCP to fetch current Enginemailer tool schemas via RUBE_SEARCH_TOOLS and verifies an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. It then executes the chosen tool through RUBE_MULTI_EXECUTE_TOOL, supplying a memory payload and session_id, following the core steps: discover tools, check connection, and execute.

When to Use It

Automate sending a new Enginemailer campaign by discovering tools, establishing a connection, and executing the send tool.
Update subscriber lists or segments using Enginemailer tools discovered at runtime.
Check the status or results of a recent Enginemailer campaign or job.
Perform bulk operations on campaigns or contacts using tool slugs obtained from RUBE_SEARCH_TOOLS.
Debug or test tool schemas by re-discovering tools to validate current inputs and outputs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed).
Step 2: Verify RUBE_SEARCH_TOOLS responds and returns Enginemailer tool slugs and input schemas.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a valid session_id and memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tool slugs or arguments to use current schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool.
Reuse session IDs within a workflow; generate a new session_id for new workflows.
Avoid hardcoding tool slugs or arguments; rely on schemas returned by RUBE_SEARCH_TOOLS and handle pagination tokens.

Example Use Cases

Discover Enginemailer tools and run a campaign send using the appropriate tool_slug and inputs returned by RUBE_SEARCH_TOOLS.
Update a subscriber list by locating the correct Enginemailer tool via RUBE_SEARCH_TOOLS and executing it with the required fields.
Query the status of a dispatched campaign and retrieve results through the corresponding Enginemailer tool discovered at runtime.
Perform a bulk operation across multiple campaigns using RUBE_REMOTE_WORKBENCH to run multiple Composio tools in sequence.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and validate against discovered tool inputs before execution.

Frequently Asked Questions

Add this skill to your agents