What is mailboxlayer-automation?

It is an automation workflow that runs Mailboxlayer tasks through Rube MCP, leveraging tool schemas discovered via RUBE_SEARCH_TOOLS.

Do I need Mailboxlayer API keys?

No API keys are needed for this setup. Add the MCP endpoint and ensure an ACTIVE mailboxlayer connection through the toolkit.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch the current tool slugs and argument names; avoid hardcoding and adapt the workflow to the latest schemas.

mailboxlayer-automation

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

Files (1)

SKILL.md

2.9 KB

Mailboxlayer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailboxlayer

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Mailboxlayer operations through Composio's Mailboxlayer toolkit using Rube MCP. The workflow hinges on discovering current tool schemas with RUBE_SEARCH_TOOLS and establishing an ACTIVE mailboxlayer connection before executing tools.

How This Skill Works

Connect to the Rube MCP endpoint, use RUBE_SEARCH_TOOLS to fetch available Mailboxlayer tools and their input schemas, then verify the mailboxlayer connection with RUBE_MANAGE_CONNECTIONS. Finally, run the discovered tools via RUBE_MULTI_EXECUTE_TOOL, including a memory object and a session_id to enable session reuse.

When to Use It

Validating a batch of emails for a campaign by discovering the right tool and arguments and then executing it.
Setting up a new mailboxlayer connection and ensuring it is ACTIVE before automation workflows.
Building a multi-tool mailboxlayer workflow in a single session using RUBE_MULTI_EXECUTE_TOOL.
Fetching the latest tool schemas to adapt to changes in tool slugs or input fields.
Debugging or validating input arguments against the discovered schemas before execution.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and run RUBE_SEARCH_TOOLS to fetch current Mailboxlayer tool schemas.
Step 2: Connect to mailboxlayer with RUBE_MANAGE_CONNECTIONS and confirm the connection shows ACTIVE.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, provide exact args, and include memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas.
Check that the mailboxlayer connection shows ACTIVE in RUBE_MANAGE_CONNECTIONS before running tools.
Use exact field names and types from the search results; avoid hardcoding slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow to improve efficiency and consistency.

Example Use Cases

Campaign hygiene: discover the mailboxlayer tool, verify the connection is ACTIVE, and validate a list of 10k emails before send-time.
New user onboarding: validate a single email address during signup by selecting the appropriate tool from the current schema.
Domain deliverability check: perform MX and syntax validations for a sender domain prior to campaign deployment.
Bulk lookups: run multiple mailboxlayer operations in one session using RUBE_MULTI_EXECUTE_TOOL with a shared session_id.
Post-change debugging: after a tool schema update, re-search tools to adapt automation without hardcoding slugs.

Frequently Asked Questions

Add this skill to your agents