Enginemailer Automation

What This Skill Does

• This skill automates operations within the Enginemailer platform using Composio's Enginemailer toolkit via Rube MCP.
• It's designed for users who need to manage email campaigns and marketing automation programmatically. It requires an active Enginemailer connection and Rube MCP setup.

When to Use

Automate sending email campaignsManage subscriber lists in EnginemailerRetrieve and analyze campaign performance dataManage Enginemailer connectionsSync Enginemailer data with other systemsCreate workflows for email marketing automation

Key Features

• Automates Enginemailer tasks via Rube MCP.
• Uses RUBE_SEARCH_TOOLS to discover available tools. Requires active Enginemailer connection via RUBE_MANAGE_CONNECTIONS. Provides a core workflow pattern for tool execution. Highlights the importance of schema compliance. Offers setup instructions and known pitfalls.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedEnginemailer 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