Benchmark Email Automation

What This Skill Does

• This skill automates Benchmark Email operations using Composio's Benchmark Email toolkit via Rube MCP.
• It allows users to manage email campaigns, contacts, and lists programmatically. This is useful for automating marketing workflows and integrating email marketing with other systems.

When to Use

• Create and send email campaigns.
• Manage contact lists in Benchmark Email. Automate email marketing tasks. Get campaign performance data. Trigger emails based on events. Segment contacts automatically.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Benchmark Email connection. Dynamically fetches tool schemas to ensure compatibility. Provides a structured workflow for tool execution. Includes error handling and connection verification. Integrates with the Composio Benchmark Email toolkit.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedBenchmark Email Automation via Rube MCP

Automate Benchmark Email operations through Composio's Benchmark Email toolkit via Rube MCP.

• Toolkit docs: composio.
• dev/toolkits/benchmark_email.

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["benchmark_email"] 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